dw_maintenance | (no subject)

(no subject)

We're getting multiple reports of crossposting to LiveJournal not working, with an error message of "Failed to crosspost entry to [username]@LiveJournal: Failed to connect to http://www.livejournal.com/interface/xmlrpc." We're looking into whether this is a problem on LJ's end or our end (and if it's our end, we'll do our best to fix it!)

EDIT: This problem has been fixed now!

Flat | Top-Level Comments Only

Dreamwidth and everyone who works on it Rock. So. HARD.

Thank you for always doing everything you can and then communicating it to us :D

Yep, it's been happening to me. Thank you for your attention to it.

Should be fixed now. One of our IPs got banned again.

Awesome, thank you for fixing that!

Thank you.

It's not fixed for everyone, or there's been a new instance. I've just had 2 crosspost attempts fail in the last hour. (Same post -- I tried an edit-and-crosspost first before reporting the problem.)

The problem was only fixed about 15 minutes ago, so give it another try now.

Just crossposted a fresh post few minutes ago,(I haven't done an edit and crosspost since I gave up on the original post that was failing to crosspost and just posted that one directly on LiveJournal) and crossposting seems to be working again, so thanks

mark and

denise

I've not seen this latest problem, but a few days ago I crossposted an entry to both LJ and IJ, then later edited it. The edit worked fine with the IJ entry, but LJ just reposted it (ie I ended up with two entries on LJ). Is this a known problem?

I've had one other report about something similar recently. If you could open a Support request with the link to the entry, and, if possible, the links to the entries on LiveJournal, I'll look into it. Thanks!

Done. Unfortunately I can't link you to the original LJ entry as I deleted it as soon as I realised what had happened.

FWIW I've had this happen to me on multiple occasions, too, but with nothing to show for it since I always delete the duplicated post once I spot it.

If it happens again, can you open a Support req? More reports = more data = easier to triangulate where the issue is.

Thanks!

Will do!

I had this happen with some imported entries from ~2004. I was tagging, actually edited a typo or something, and instead of editing the post on LJ, it posted the edited entry as a second entry (but with the right month/day in 2004). iirc, it happened on multiple entries but when I realized what was happening, I stopped and deleted the doubles.

Since I still have about eight years to tag, I'm sure I'll have a chance to test it again. If I get the same weirdness, I'll open a ticket.

See, this is why I love you guys... unlike LJ where the RSS feeds can sit broken for a week or more until someone goes "Oh hey, weren't we supposed to fix that or something?!"

I got that identical error message less than 2 minutes ago. I'm not sure that it actually didn't post, because I immediately edited the DW entry without checking the LJ (because sometimes that makes it post on LJ), and when I looked just now, the LJ entry was there.

The error above also shows when the crossposter's first attempt to reach LiveJournal doesn't go through. The error is thrown automatically, but then it retries. Often, the second try will go through without any issues.

If it happens again, or if the entry doesn't actually make it over, please let us know!

Thank you, Denise. You are made of awesome ♥

Thanks for fixing that! I had assumed it was due to the database outage LJ had a while back. It kept happening, but I still assumed it was LJ somehow ;). Again, thanks!

I've been getting cross-post fails this past week - 1 out of 4 seems to go through, the rest fail. edits to DW posts are also not cross-posting. I've waited for up to a day to see if the cross-post makes it through after it retries and the problem persists.

edited to add: problem began 7/17 and since then and I received roughly 14 crosspost failure notifications

Edited 2013-07-25 18:47 (UTC)

That problem usually means LJ's down or unreachable at the time. We'll look into it!

I assumed it was an issue at LJs end. Although here is another odd data point: on 2 of those failed cross-posts, it created double entries on LJ (one locked which is my default when I post to DW) and then when I unlocked the DW post it created a second unlocked duplicate. Both LJ posts link back to the same (now unlocked) DW post and have the same date stamp.

ex: http://morgandawn.livejournal.com/1284828.html (unlocked)
the locked version is here (I unlocked it just now so you can see it)): http://morgandawn.livejournal.com/1284425.html

This has been happening to me today since about 2:30pm PST - none of my posts have crossposted, and the failure notification is the one you quote.

I'm having this problem still. Just happened again...

The problem is back again. I had it happen to posts made Sunday morning, and I just had it happen on a post I just made.

95% of the time, that error means that LJ's down or unreachable (the other 5% of the time means they're up, but they've blocked us, but that doesn't appear to be the case this time). LJ has been really intermittent this week -- your best option is to wait a day or two, then edit the post and check the crosspost box again, which will make it retry the crosspost.

Sigh. This gets tiring. Got the two non-crossposted entries to finally post yesterday... and now I'm getting the error for today's post. Not how a seamless system is supposed to work -- I'll just keep trying.

I wish there were something we could do, but sadly, whether LJ is reachable or not is out of our hands!

And now it works. Must'a been that dead chicken I waved in front of my monitor.

Flat | Top-Level Comments Only