stephenbrooks.orgForumMuon1GeneralBOINC server issue
Username: Password:
Search site:
Subscribe to thread via RSS

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings.  You are *required* to use the date.timezone setting or the date_default_timezone_set() function.  In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier.  We selected 'Europe/London' for 'BST/1.0/DST' instead in /home/stephe1/public_html/forum/main.php on line 269

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings.  You are *required* to use the date.timezone setting or the date_default_timezone_set() function.  In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier.  We selected 'Europe/London' for 'BST/1.0/DST' instead in /home/stephe1/public_html/forum/main.php on line 269
Stephen Brooks
2012-04-04 18:37:50
Right now I noticed that the BOINC wrapper/yoyo@home server is displaying "500 - Internal Server Error". I also notice that the Muon1 project hasn't received any results from these BOINC-wrapped users since April 1st.  Have e-mailed yoyo to see if he knows what's wrong.  Non-BOINC users are unaffected.
K`Tetch
2012-04-04 19:44:32
I did think the weekly stats on @muon1 were down a bit.

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings.  You are *required* to use the date.timezone setting or the date_default_timezone_set() function.  In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier.  We selected 'Europe/London' for 'BST/1.0/DST' instead in /home/stephe1/public_html/forum/main.php on line 269
K`Tetch
2012-04-04 19:47:37
As I posted about this to twitter, I noticed a tweet from the boinc wrapper account (@yoyo_rkn)




Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings.  You are *required* to use the date.timezone setting or the date_default_timezone_set() function.  In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier.  We selected 'Europe/London' for 'BST/1.0/DST' instead in /home/stephe1/public_html/forum/main.php on line 269

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings.  You are *required* to use the date.timezone setting or the date_default_timezone_set() function.  In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier.  We selected 'Europe/London' for 'BST/1.0/DST' instead in /home/stephe1/public_html/forum/main.php on line 269
Stephen Brooks
2012-04-04 19:53:59
Ah, that explains it.  (FYI Muon1's database is backed up daily, though it's only to a NAS box about 6 feet away from the stats server, so I'm not sure how much redundancy that really gives.)

Depending on how long yoyo@home takes to come back online, BOINC users might consider running the native Muon1 client for a while.

[edit] A response:
From: "yoyo" 
To: "Stephen Brooks"
Subject: Re: Yoyo server error?
Date: 2012 April 04; Wednesday 20:01

There was a power outage last weekend in the data center.
Afterwards the data base could not start anymore.
The disc has read faults.  Therefore the service will deploy a new disc.
Afterwards we will copy everything to the new disc and try to recover as
much as we can from the data base.
The data base backup was done round 15h before the crash.

This error 500 means, that the server is now in rescue mode and no more
reachable.
Stephen Brooks
2012-04-05 13:40:41
Looks like this issue is resolved, from our point of view at least: (BOINC wrapper) results started coming in to Muon1 again last night.
: contact : - - -
E-mail: sbstrudel characterstephenbrooks.org
Yahoo: scrutney_mallard
Jabber: stephenbrooksstrudel characterjabber.org
Twitter: stephenjbrooks

Site has had 12243009 accesses.