Denise (
denise) wrote in
dw_maintenance2011-07-27 11:43 am
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Crossposting to LJ throttled; LJ imports slow/failing
As LJ has now officially confirmed that they're experiencing a DDoS attack, and a pretty nasty one at that, we've throttled the rate at which we attempt to crosspost entries, and reduced the number of times the process will try before it fails. (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 1 minute, 5 minutes, and 15 minutes.)
You don't need to do anything differently when posting your entries, but if you receive a failure notice after the third try (which should happen around 20 minutes after you try to crosspost your entry), wait a while and then try to crosspost again, by editing the entry, making sure the crosspost box is checked, and saving the entry.
If the crossposting continues to fail after that, just hang tight and wait a day or so before you try again. LJ's operations and engineering teams are doing everything they can to restore access to the site, including restoring the ability to post from elsewhere using the LJ protocol (which is what the Dreamwidth crossposter uses).
Importing from LJ is also affected by this, obviously, which is driving up the import queue. If you can, please consider waiting a few days to import your journal from LJ -- the process is likely to fail right now anyway. If you get a failure in your inbox when trying to import, just hang tight and try again in a few days.
If the traffic situation at LJ continues to worsen, or if the backup gets too large, we may temporarily disable LJ as an import source, in order to let the queue clear out a bit. If that happens, I'll post here about it again!
We wish LJ and the LJ team the absolute best of luck in dealing with this situation, and we hope that they can recover quickly!
EDIT: And the slowness on our end that some people were noting turned out to be another stuck process and Apache in general sucking up too much memory.
alierak is monitoring and fixing.
EDIT #2: (1) The problems on our end involve some bug that's causing the webservers to work too hard that we're trying really hard to chase down the source of. If DW is slow or sluggish for you, that's the cause. We've put some measures in place to deal with it temporarily, and we're working on tracing down the root source of the problem. It's not traffic-related!
(2) If you comment, please try to keep it on the topic of Dreamwidth, not LJ -- we'd like to avoid the comments turning into a LJ-bashing session. Thanks, all.
You don't need to do anything differently when posting your entries, but if you receive a failure notice after the third try (which should happen around 20 minutes after you try to crosspost your entry), wait a while and then try to crosspost again, by editing the entry, making sure the crosspost box is checked, and saving the entry.
If the crossposting continues to fail after that, just hang tight and wait a day or so before you try again. LJ's operations and engineering teams are doing everything they can to restore access to the site, including restoring the ability to post from elsewhere using the LJ protocol (which is what the Dreamwidth crossposter uses).
Importing from LJ is also affected by this, obviously, which is driving up the import queue. If you can, please consider waiting a few days to import your journal from LJ -- the process is likely to fail right now anyway. If you get a failure in your inbox when trying to import, just hang tight and try again in a few days.
If the traffic situation at LJ continues to worsen, or if the backup gets too large, we may temporarily disable LJ as an import source, in order to let the queue clear out a bit. If that happens, I'll post here about it again!
We wish LJ and the LJ team the absolute best of luck in dealing with this situation, and we hope that they can recover quickly!
EDIT: And the slowness on our end that some people were noting turned out to be another stuck process and Apache in general sucking up too much memory.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
EDIT #2: (1) The problems on our end involve some bug that's causing the webservers to work too hard that we're trying really hard to chase down the source of. If DW is slow or sluggish for you, that's the cause. We've put some measures in place to deal with it temporarily, and we're working on tracing down the root source of the problem. It's not traffic-related!
(2) If you comment, please try to keep it on the topic of Dreamwidth, not LJ -- we'd like to avoid the comments turning into a LJ-bashing session. Thanks, all.
no subject
But I honestly don't know when, right now, I would have time. By way of illustration, currently I am studying Russian, German, and Japanese on my own (which is not as ludicrous as it sounds, honestly, there are circumstances!), holding down a day job, prepping two novels for self-pub, practicing two instruments, planning on voice lessons in the winter, prepping costumes for Dragon*Con, um. Squirrels. TUtoring Spanish. And cooking and cleaning and... no, wait, I think that's it. So, um. Spare time, what is that?
Also my sense of design with regard to end-user work is crap. I can throw up a crappy model and take feedback but I am pretty well useless for design.
Um. That said, though, actually, the various factors that make me good at languages also make me pretty quick to pick up coding, so, yeah, if I ever stop running the Red Queen's race, I will totally take you up on that. Also, if you do need help with either writing copy or translating copy into Spanish, French, or possibly Russian or German, I can also help with that! It'd fall neatly under currently allotted practice time, I'm always looking for more things to write or read in languages. (I'm planning on picking up either Arabic Standard or Hindi after Dragon*Con, while I try to maintain/reinforce my Russian, shoot me now.)
no subject
We don't currently have plans to do translations (the reasons why are long and complex but basically boil down to, the system to do so is unworkable and the maintenance of the translation once it's done is a nightmare) but we always need people who are willing to write or improve our FAQs and Guides.
(But, yeah. Don't ever feel like you have to -- your life sounds hectic enough!)
no subject
Ugh. But, yeah, I think I can do that. At least, on the surface it looks like I can. *peers at comm* Oh yeah, I can totes do that. I know a couple other people who could do that easy, too, but they're doing the same trying-twenty-things-at-once that I am. The short version is about three years ago we decided we were sick of talking about how awesome we could be and decided to actually work on being that awesome. But! Yes. My talents lie in fiction, but in order to actually sell fiction you have to write clear, concise, and often short non fiction, so, sadly... Also my day job sometimes involves writing instruction sheets.
And, um, I'll stop trying to impress you now. >.> Tonight is slammed but I will poke the comm in more detail tomorrow and see what things I can pick up!
no subject
Anyway, if you get stuck or have any questions or just need guidance, just PM me; I'm happy to assist. :)
no subject
no subject
And in the event you do IRC and want to hang out, it's #dreamwidth on Freenode.
no subject
Oh man, I haven't done IRC in the longest time. If I start back up again, I'll remember that. :)