Friends

16 May 2013 @ 06:02 pm

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.

105 comments | Leave a comment

mferrell
[lj_maintenance]

16 May 2013 @ 01:42 pm

Maintenance still in progress

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.

330 comments | Leave a comment

livejournal
[lj_maintenance]

16 May 2013 @ 03:35 pm

Maintenance update

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.

1251 comments | Leave a comment

mferrell
[lj_maintenance]

15 May 2013 @ 09:44 pm

Maintenance update

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.

963 comments | Leave a comment

mferrell
[lj_maintenance]

15 May 2013 @ 06:46 pm

Emergency maintenance on user cluster #7

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.

162 comments | Leave a comment

spot

07 May 2013 @ 05:40 pm

Tuesday Notes

Today was the day of "stuff I can't talk publicly about". Sorry.

* Talked with Ruth about Flock hotels, good progress there! She is kicking butt. :D
* Updated matreshka to 0.4.0 in rawhide, now that gcc has a fix for the ada bug that was blocking it. Tagged gcc override into F19, but the buildroot never regenerated... so I will have to keep waiting to rebuild it there.
* Updated perl-Config-IniFiles to 2.79 in f19 and rawhide (Fix test failures with Pod-Simple-3.28)
* Walked 2.5 miles on the treadmill (I need to lose weight!)
* Updated fedora-logos to 19.0.2 in f19 and rawhide, added new Fedora logo specifically for use with GDM login screen in Fedora 19
* Went to last ultrasound appointment with Pam, baby is coming soon. :)
* Updated perl-Gtk2 to 1.247 in F18, added explicit list of provides to resolve bz 960358

2 comments | Leave a comment

spot

06 May 2013 @ 05:05 pm

Flock Call For Papers (and Registration) is Open!

For eight years, Fedora users and developers have gathered at an event named for them, the Fedora Users and Developers conference (FUDCon). But we’ve grown, and it’s time for a new approach: Flock.

Flock will bring together the Global Fedora communities for three days of scheduled content with one optional day at the end for open hacking. Unlike the barcamp style we've used in the past for FUDCon, Flock will accept submissions in advance for talks, hackfests, sprints, and workshops. The schedule will be built based on the community's votes on those submissions.

This is a Fedora focused event, but we welcome participation from the entire Free Software community. If you have an idea on how we can improve Fedora, we'd love to hear it!

Dates: August 9-12, 2013
Location: College of Charleston (Charleston, SC, USA)
Website: flocktofedora.org

Both pre-registration and talk submissions are now open! Submissions should be for one of the following:

* Talk (45 minutes)
* Hackfest (2 hours)
* Workshop (2 hours)
* Sprint (2 hours)

You may submit as many topics as you feel qualified to deliver.Suggested topics include but are in no way limited to:

* ARM
* Cloud
* Community
* Design
* Desktop
* Fedora Ambassadors
* Fonts
* Games
* Infrastructure
* Marketing
* Open hardware
* QA
* Security
* Special Interest Groups

Ready to submit a talk or register? Go to http://flock-lmacken.rhcloud.com/.
All submissions must be received by May 31, 2013 at 11:59 p.m. ET.