Yes, some sort of problem communicating with the servers just now. What is the weather like in Denver, CO? (OUr BOINC servers are there, or in nearby Boulder, CO. I forget just which.)

Lawrence

There used to be a Wednesday morning maintenance run, but about 3-4 month ago that was discontinued due to the very hi reliability achieved and also, the ability to do daily backups without interrupting production. It must thus be you had an intermittent from where you are, across all the hops do Boulder Co. and back. Anyway, there are 2 parallel systems, so sometimes 50 percent have a disturbance and the other 50% has not. The system is designed to fail over, but how quick i do not know.

At least, when uploading a FA@H job at 12:34 CET the data files (part 1) went up fine and the "Ready To Report" task was acknowledged at 13:10:13 (part 2). A typical result reporting cycle looks like this:

BOINC uses for efficiency sake (discussed elsewhere extensively), a 2 part completed task reporting. The result data files are most important and go first. The entry that confirmed the confirmation that the result files were uploaded goes later talking to the scheduler. Here a link to the Schematics which can be found in the Start Here forum's "Information about BOINC" thread:

Added: The Maintenance Schedule can be found following the link below in my signature!

Sek, you may be right about the 50% availability. One of my systems just managed to pull some new work. Others are still failing.

Jonathan.

Ok - you can get work now - I'm trying to figure out what happened. It appears that the problem started around 15:06UTC

Yea - it isn't quite resolved. I'm continuing to investigate. The key issue is that the db load is extremely high