Denise (![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
denise) wrote in ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_maintenance2011-12-06 02:20 pm
denise) wrote in dw_maintenance2011-12-06 02:20 pm
LJ DDoS causing import (and possibly crosspost) problems
The DDoS mitigation steps that LiveJournal is taking to make sure their users can continue to access the site have, unfortunately, meant that third-party applications (such as DW's importer!) temporarily can't access the site. This means that importing from LJ is temporarily disabled again, because all imports would fail due to being blocked. We'll let you know when they're re-enabled!
Many people are also experiencing problems with crossposts. If you try to crosspost an entry and it doesn't immediately crosspost, your crosspost attempt has not mysteriously wandered off into the deepest darkest depths of the internet: until you receive a failure message in your inbox or the crosspost attempt succeeds, the worker is still trying to contact LJ in order to make your crosspost, even if you then edit the entry and the crosspost box is unchecked. (The crosspost box will not be checked on the entry edit page until the crosspost is successful.) So, just hang tight until you get the final failure message in your inbox, then wait a day or two and try to crosspost again by editing the entry, checking the crosspost box, and hitting 'save'.
Because of the problems with accessing LJ, and in order to help reduce the traffic on LJ's servers, we've lowered the number of times a crosspost attempt will try to contact LJ before failing and we've extended the delays between attempts (it was five tries at an interval of 10 seconds, 30 seconds, 60 seconds, 5 minutes, and 10 minutes; now it's three tries at 5 minutes, 15 minutes, and 30 minutes.) This may help more crossposts to succeed because of the reduced load, or it might have no effect at all, but we're hoping it will also help reduce the traffic to LJ and help them recover from their DDoS more quickly.
Best of luck to LJ with their DDoS mitigation efforts!
Many people are also experiencing problems with crossposts. If you try to crosspost an entry and it doesn't immediately crosspost, your crosspost attempt has not mysteriously wandered off into the deepest darkest depths of the internet: until you receive a failure message in your inbox or the crosspost attempt succeeds, the worker is still trying to contact LJ in order to make your crosspost, even if you then edit the entry and the crosspost box is unchecked. (The crosspost box will not be checked on the entry edit page until the crosspost is successful.) So, just hang tight until you get the final failure message in your inbox, then wait a day or two and try to crosspost again by editing the entry, checking the crosspost box, and hitting 'save'.
Because of the problems with accessing LJ, and in order to help reduce the traffic on LJ's servers, we've lowered the number of times a crosspost attempt will try to contact LJ before failing and we've extended the delays between attempts (it was five tries at an interval of 10 seconds, 30 seconds, 60 seconds, 5 minutes, and 10 minutes; now it's three tries at 5 minutes, 15 minutes, and 30 minutes.) This may help more crossposts to succeed because of the reduced load, or it might have no effect at all, but we're hoping it will also help reduce the traffic to LJ and help them recover from their DDoS more quickly.
Best of luck to LJ with their DDoS mitigation efforts!
no subject