Back online

  • May. 16th, 2013 at 6:02 PM
markf
lj_maintenance
We've just brought User Cluster #9 back online, and the errors being caused by the maintenance should stop occurring. Notifications are sending again, but may be delayed as there is a backlog of notifications waiting to be sent. If you are still encountering any errors, please open a Support request so we can investigate the issue.

Maintenance still in progress

  • May. 16th, 2013 at 1:42 PM
mferrell
lj_maintenance
We are still in the process of bringing User Cluster #9 back online, and it is unfortunately taking longer than we anticipated. We are making progress, but are still several hours away from this being fixed. To address a few common questions we are seeing:

How many user clusters are there?

There are 13 user clusters in total.

How can I find out what user cluster my account is on?

You can see which user cluster you are on at http://www.livejournal.com/misc/whereami.bml if you are logged-in. If you cannot login, your account is located on user cluster #9.

I am not on cluster 9, but still can't post or edit entries. What's happening?

Trying to update or edit posts may still fail even if you are not on user cluster #9. An Error 500 will appear when loading the update/edit journal page if you have posting access to a community which is located on this cluster. The update module at http://www.livejournal.com/portal/ may still allow you to post while maintenance is ongoing.

I'm not getting notifications. Is this related?

Subscription notifications are not currently being sent as a result of this maintenance. You may still receive other types of emails, such as pingbacks and password notification emails, but will not receive notifications of new entries or comments being posted.

What other things aren't working right now?

Twitter digest posts are not currently being imported as a result of this maintenance. Some other pages & features may display errors if they need to access information located on user cluster #9. The inbox and community management pages are both known to be showing errors for people affected by this.

We will post again either when user cluster #9 is back online, or if we have any additional information to post. Thanks again for your patience while we work to fully restore service to the site.

Maintenance update

  • May. 16th, 2013 at 3:35 PM
livejournal
lj_maintenance
We successfully finished maintenance on cluster #7. All accounts’ owners from this cluster can now log into their journals.

We are working on restoring the user cluster #9, it will take approximately an hour. We will keep you informed. Please accept our apologies for the inconvenience.

Maintenance update

  • May. 15th, 2013 at 9:44 PM
mferrell
lj_maintenance
To followup on the previous post, the same symptoms for user cluster #7 are also present for users on cluster #9, so we're in the process of fixing it as well. Having 2 clusters to work on rather than 1 unfortunately means that we expect it to take approximately 6-8 hours for everything to be resolved. We do, however, know how the problems with each cluster started and it is not something which will cause any additional clusters to have these issues. We'll post here again either when the issue has been resolved, or if we have any significant developments to update you on.

Emergency maintenance on user cluster #7

  • May. 15th, 2013 at 6:46 PM
mferrell
lj_maintenance
We're doing some emergency maintenance on one of our databases (user cluster #7, there are 13 user clusters in total. You can see which user cluster your account is on here). The estimated duration of this maintenance is 4-5 hours.

If your account is located on user cluster #7, you will not be able to login to your account until this maintenance has been completed. If you are already logged-in, you will be unable to post, edit, or delete any material on LiveJournal until the maintenance is completed.

If your account is not on this cluster, LiveJournal will still be up, you will be able to login. You may be able to post, edit, and delete content, but if any communities you have posting access to are on cluster #7, you will see an Error 500 when attempting to load the update/edit journal page, or viewing your inbox if any messages have been received from a user on cluster #7. Other pages may also be similarly affected if they attempt to load usernames or data from this cluster. You may also encounter problems viewing journals, entries, comments, or private messages from accounts which are on this cluster.

We're working as quickly as possible to get everything back up & running, and appreciate your patience during this maintenance.