Back up!

[mark]

Looks like we're back online. Please let me know if anything is not working like you expect!

Update: DNS was broken. This affected imports, crossposts, and emails. It's back up and running now and the email backlog will slowly be cleared. Nothing was lost, just delayed.

Comments

[simont]

Well, my network page contains no entries at all, which seems odd. (But perhaps things are still starting up and it'll be fine in a few minutes?)

[mark]

I believe this is because memcache is not warm enough yet. If it's still broken in a few hours, then maybe I can do something to kickstart it.

[simont]

It's back to normal now :-)

[kayliemalinza]

Wow, that was fast! Good job!

Crossposting to LJ is giving me a new error, though: Failed to connect to http://www.livejournal.com/interface/xmlrpc.

[dil]

It's not new, I had been receiving these last week. LJ is fucked up.

[kayliemalinza]

Ah, well, I crossposted yesterday no problem so I didn't know if it was related to the maintenance or not.

[mark]

Actually, this is. DNS problem. I'm on it.

[kayliemalinza]

Hey, it went through! You're awesome.

[ilyena_sylph]

That looks like it might be the same problem one of my buddies is having trying to start crossposting.

She put in a Support request sometime last week, but last I knew (yesterday) she hadn't heard back from anyone.

Should it be fixed across the board now?

[mark]

It's certainly worth a shot.

This morning's issue shouldn't have been affecting anything earlier than this morning, though. Any problems last week are likely to be from a different source.

[denise]

Basically, there are three possible causes of "having crosspost problems" (if you're talking about from this morning):

* the DNS problem related to the maintenance that Mark fixed (should be fixed now)
* LJ's DDoS problems making it impossible to contact the remote site at the time crosspost is requested (is kind of on and off and on and off based on whether LJ is reachable)
* some bizarre third problem that needs investigation

Right now, the most common problem is #2: LJ's DDoS problems. We are looking into problems that people ask us about in case it's #3, some bizarre new problem, but generally, assume that any crosspost problems involving not being able to contact LJ is because LJ's DDoS is preventing it.

[ilyena_sylph]

*nods*

Yeah, I know, so does she. I think she's tried six different times to get things to crosspost, at wildly different times, and... can't.

*shrugs*

It'll fix itself, somebody will get to her request, or when I get over to her place this weekend I'll try poking at it some more.

[denise]

It is possible it is something weird! But right now it's hard to troubleshoot, because, well, LJ DDoS. :/

[florahart]

The fun thing about the site being completely totally utterly down is that there are like two posts on my reading list between "going to be down for a couple hours" and "back up!" It's like time didn't even pass in there or something.

Yay for success!

[baggyeyes]

I seem to be having trouble accessing pages like Settings, or Customize. Am I the only one?

EDIT: Never mind. Just loaded for me.

[miera_c]

I don't say this enough, but I love all the DW staffers because you clearly care about keeping this thing up and going. And you tell us when something's not working instead of leaving us in the dark.

[onlysmallwings]

+1!

[illariy]

+1

I really like the almost-real time info on when the site is down, whether for planned maintenance or unplanned. Much appreciated, rock on. <3

[geminianeyes]

This.

It's one of the reasons why I love DW. :D

[dil]

+100. Unlike LJ maintainers breaking it themselves and lying about permanent DDoS.

[wytchcroft]

all seems shiny and good - you kids is crazy mit der quickness! :)

[jumpuphigh]

Is search down? I haven't had any success searching.

Error: Sorry, we were unable to find a result in the time allotted. This may mean that the server is busy or down. Please try your query again later.

I've tried a few different searches and I get this message every time.

[mark]

Try now?

[jumpuphigh]

All better. Thanks!

Three cheers!

[marashar]

Three cheers for all of you to get the side online that fast again.

[blackwillow]

You are awesome.

[intermezzo]

You guys are awesome. Will renew my account next week for sure!

[lone_lilly]

You guys rock as usual!

Having a weird problem with html code in posts this evening, could this be related? img src tags aren't working and neither is < i >. I can see the code in the post instead of the desired effect. I can provide screencaps if you'd like, although they are from locked journals/communities so I don't want to do that here. :)

[denise]

In that case usually what happened is that whoever was making the post accidentally flipped over into the rich text mode instead of the HTML mode. Try double-checking that you're in HTML mode!

[lone_lilly]

Gosh, I feel dumb! You think I would have noticed that on two different journals. Sheesh. Thanks for the superquick reply! :)

[denise]

*g* It happens! Especially since the default setting is "show you whichever editor you used last", so if you accidentally flip over to RTE, you'll keep getting the RTE given to you. :)

[dil]

I can see this post http://dil.dreamwidth.org/1034603.html in my journal http://dil.dreamwidth.org/ but not on http://dil.dreamwidth.org/read
The next post http://dil.dreamwidth.org/1034858.html can be seen on both pages. Why is this?

[denise]

You checked the "dated out of order" option (when posting the entry or when editing it later) -- entries that are dated out of order don't show on reading pages.

[dil]

Thank you very much! I unchecked it and the post appeared on the reading page.

But I don't really understand how it happened, all my posts are being cross-posted from a standalone wordpress blog which does not have this "out of order" functionality..

[denise]

Hm. Maybe the crosspost script automatically sets the backdate option if the post is dated differently? The DW software does try to prevent you from posting "in the past", so sometimes if you post in the future without the date out of order option, you won't be able to post "normally" again until you reach that 'future' date. (If that makes any sense.) So, some crossposting scripts will know that, and will set the "date out of order" flag on the crosspost whenever the current time and the time of the entry don't match.

[dil]

Maybe, but I didn't change the dates for both yesterday posts, and one of them got this flag somehow..

[denise]

Could you have edited the post after the fact somehow and accidentally checked the box?

(It's hard to troubleshoot "this got set and I don't know how" type issues, since there are so many ways that it could happen accidentally. If you keep having the problem regularly, open a support request and we can look into it more, but if it's just the once, I'm inclined to chalk it up as just something being weird.)

[dil]

No, I didn't edit them. It's rather difficult to change the time accidentally, it's hidden by default. I would have to click the "Publish immediately/Edit" link, then the date/time form would appear, and I would click the OK button on it. Too complicated for an accident.

Don't worry, anyhow it's my problem rather than yours.

[denise]

if it keeps happening, try posting directly to your account (through the DW posting interface) and see if you get any messages about needing to date out of order? That might give some clues.

[dil]

Thanks, I'll let you know if I find anything unusual

[triadruid]

Crossposts are working fine for me, but they no longer spam my inbox when they succeed (haven't had one fail since the downtime). Not a big deal if this is by design (I really only care if they fail), but I hadn't seen any announcement of a change to this.

[denise]

This was by design -- it was announced in a code tour, but I'm so very behind and we haven't had a major news post since the code push in which it went live. I'm sorry for the confusion!

If you want to get the success messages too, go to your manage notifications page and check "when a crosspost succeeeds" :)

[triadruid]

No problem, thanks for letting me know.

[tameiki]

I don't have the words to express how much I appreciate everyone at Dreamwidth. You continually, and consistently give us updates, real news, and actually *gasp!* reply and give us answers when we ask questions/concerns in a timely manner.

The more I see of the exact opposite of what you do on Dreamwidth happening at Live Journal, the more I love it here :)

Thanks again for all you do!

[awry]

Is importing still down? I've tried several times over the last few months to import from LJ and it never does. :/

[denise]

Importing should work, assuming LJ is not unreachable at the time you try (due to DDoS attacks). You should receive an error message in your inbox when the job fails -- if it fails due to LJ being unreachable it'll say something like "XML-RPC error, can't contact www.livejournal.com". If it's a different problem, it'll be explained in the failure message. If you can't figure it out, open a support request with the text of the error and somebody will help you try to figure it out!

(Today the import queue is very backed up; there are a lot of people importing.)

[awry]

I've tried when LJ's not having problems and it goes into a queue but then never imports. :/ I'll wait and see what this one does for now.

Also every time I see your user name in my inbox I'm like 'what? When did I reply to myself on DW?' lol

[denise]

*giggle* Fellow Denise, I assume?

It sounds like something is failing, yeah. Check your inbox and the error message -- it's possible that something's causing the import to fail.

[awry]

Yup! And it's a great name. :D
All it says right now is 'Waiting for verification to finish'. Which is probably because you said it's backed up right now. In the past I'm not even sure it did all that. :/ Ah well I'll give it some time to hopefully clear out and hopefully it will import. :D