Yesterday both CE.com and the connection to the projects worked on was lost. Everything seems to be back online and working fine - it would be nice, though, to maybe hint at what happened? :)
Hi Marcel, there were some technical challenges being addressed yesterday. Connectivity was intermittent, so some people may have been able to connect fine while others experienced an inability to connect. Sorry to hear you were on the unfavorable end of that!
Things are back in shape and working fine, now, it was just one of those cases where finding the problem is 99% of the battle! Thanks much for your support!
It's normal that it's waiting an hour to try to reconnect after a failure. The failure itself is not typical, though -- is that still happening? We did fix a DNS issue on that server which may have been the cause.
But in any case, yes, the Rosetta project server works independently from the CE server; all project servers do, really. So one can fail without any of the others being affected as far as your tasks go. Good thing, too... project servers go up and down often enough... we'd never get anything done!
Yesterday both CE.com and the connection to the projects worked on was lost. Everything seems to be back online and working fine - it would be nice, though, to maybe hint at what happened? :)
Much appreciated,
a happy CE helper,
best wishes,
Marcel Aubron-Bülles
Hi Marcel, there were some technical challenges being addressed yesterday. Connectivity was intermittent, so some people may have been able to connect fine while others experienced an inability to connect. Sorry to hear you were on the unfavorable end of that!
Things are back in shape and working fine, now, it was just one of those cases where finding the problem is 99% of the battle! Thanks much for your support!
Great to hear it, Tristan, thanks for getting back to me :)
Hmmm...From My "log":
It looks like that an hour goes by between attempts to contact the Mother Ship!!
12/17/2014 2:36:20 PM | Charity Engine | Sending scheduler request: Requested by project.
12/17/2014 2:36:20 PM | Charity Engine | Sending trickle-up message
12/17/2014 2:36:20 PM | Charity Engine | Reporting 8 completed tasks
12/17/2014 2:36:20 PM | Charity Engine | Requesting new tasks for CPU and ATI
12/17/2014 2:36:28 PM | Charity Engine | Scheduler request completed: got 0 new tasks
12/17/2014 2:36:28 PM | Charity Engine | Server can't open database
12/17/2014 2:37:44 PM | Charity Engine | Fetching scheduler list
12/17/2014 2:37:45 PM | Charity Engine | Master file download succeeded
12/17/2014 2:37:50 PM | Charity Engine | Sending scheduler request: Requested by project.
12/17/2014 2:37:50 PM | Charity Engine | Sending trickle-up message
12/17/2014 2:37:50 PM | Charity Engine | Reporting 8 completed tasks
12/17/2014 2:37:50 PM | Charity Engine | Requesting new tasks for CPU and ATI
12/17/2014 2:37:51 PM | Charity Engine | Scheduler request completed: got 0 new tasks
12/17/2014 2:37:51 PM | Charity Engine | Server can't open database
Scheduler request completed
12/17/2014 3:37:52 PM | Charity Engine | Sending scheduler request: Requested by project.
12/17/2014 3:37:52 PM | Charity Engine | Sending trickle-up message
12/17/2014 3:37:52 PM | Charity Engine | Reporting 8 completed tasks
12/17/2014 3:37:52 PM | Charity Engine | Requesting new tasks for CPU and ATI
12/17/2014 3:37:55 PM | Charity Engine | Scheduler request completed: got 0 new tasks
12/17/2014 3:37:55 PM | Charity Engine | Server can't open database
12/17/2014 4:37:58 PM | Charity Engine | Sending scheduler request: Requested by project.
12/17/2014 4:37:58 PM | Charity Engine | Sending trickle-up message
12/17/2014 4:37:58 PM | Charity Engine | Reporting 8 completed tasks
12/17/2014 4:37:58 PM | Charity Engine | Requesting new tasks for CPU and ATI
12/17/2014 4:38:00 PM | Charity Engine | Scheduler request completed: got 0 new tasks
12/17/2014 4:38:00 PM | Charity Engine | Server can't open database
12/17/2014 5:38:01 PM | Charity Engine | Sending scheduler request: Requested by project.
12/17/2014 5:38:01 PM | Charity Engine | Sending trickle-up message
12/17/2014 5:38:01 PM | Charity Engine | Reporting 8 completed tasks
12/17/2014 5:38:01 PM | Charity Engine | Requesting new tasks for CPU and ATI
12/17/2014 5:38:03 PM | Charity Engine | Scheduler request completed: got 0 new tasks
12/17/2014 5:38:03 PM | Charity Engine | Server can't open database
12/17/2014 6:38:04 PM | Charity Engine | Sending scheduler request: Requested by project.
12/17/2014 6:38:04 PM | Charity Engine | Sending trickle-up message
12/17/2014 6:38:04 PM | Charity Engine | Reporting 8 completed tasks
12/17/2014 6:38:04 PM | Charity Engine | Requesting new tasks for CPU and ATI
12/17/2014 6:38:06 PM | Charity Engine | Scheduler request completed: got 0 new tasks
12/17/2014 6:38:06 PM | Charity Engine | Server can't open database
So then I requested a "Do Network Communication" and received this:
12/17/2014 6:41:59 PM | | Resuming computation
12/17/2014 6:42:25 PM | Charity Engine | update requested by user
12/17/2014 6:42:27 PM | Charity Engine | Sending scheduler request: Requested by user.
12/17/2014 6:42:27 PM | Charity Engine | Sending trickle-up message
12/17/2014 6:42:27 PM | Charity Engine | Reporting 8 completed tasks
12/17/2014 6:42:27 PM | Charity Engine | Requesting new tasks for CPU and ATI
12/17/2014 6:42:29 PM | Charity Engine | Scheduler request completed: got 0 new tasks
12/17/2014 6:42:29 PM | Charity Engine | Server can't open database
Ideas anyone?
It seems that Rosetta @ home IS working correctly...
Curious!
Ed
It's normal that it's waiting an hour to try to reconnect after a failure. The failure itself is not typical, though -- is that still happening? We did fix a DNS issue on that server which may have been the cause.
But in any case, yes, the Rosetta project server works independently from the CE server; all project servers do, really. So one can fail without any of the others being affected as far as your tasks go. Good thing, too... project servers go up and down often enough... we'd never get anything done!