You are viewing melsykes

20 May 2013 @ 09:04 pm
40(30)[?v? {recording clash}]
 
 
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.
 
 
16 May 2013 @ 01:42 pm

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.
 
 
16 May 2013 @ 03:35 pm

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.
 
 
15 May 2013 @ 09:44 pm

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.
 
 
15 May 2013 @ 06:46 pm

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.
 
 
15 May 2013 @ 10:34 pm
Served dinner at 18:20
At 21:40 L noticed I left a gas ring on on the hob
With a pan on it

Which has miraculously survived
 
 
15 May 2013 @ 07:03 pm
Well it works very nicely over HDMI to the main house telly, not a soss via composite to the ickle telly.

Have seen something suggesting composite is suppressed if HDMI is detected, but just whipping the HDMI plug out doesn't get it to switch if that was the prob.
The config.txt has an "uncomment this for composite" but it wouldn't let me edit it - I assumed the SD card had the write protect on but maybe I just need to sudo.
Or it might be something else!
 
 
14 May 2013 @ 01:49 pm
Raspberry Pi arrived, wasn't expecting it quite so soon

Examined power socket, noted that although on the webpage they mention running it off phone chargers, it's not a size we have

Run into Tod, get USB keyboard, mouse, memory stick.
No externally powered USB hubs, if only we hadn't lost the supply for the one we inherited from L's dad.
No suitable power supplies.

Get home, start ransacking house.
Eventually find cable that converts socket on Pi to standard USB. We have supplies for that.
After a really deep search, in the furthest back darkest corner of the "office", find a couple of supplies that'll fit the hub.

Good to go!

Now to package it all back up so YB can open it when he gets in from school...
 
 
13 May 2013 @ 11:40 pm
33(28 {or 26 if ultra strict}) [was it 18v17 ? I forget]