Panic Mode On (79) Server Problems?

Yes, it could be ghosts being resent - some of my machines had developed a new crop of hauntings overnight. But it looks like it's beginning to decay now - this might be a good time to try manual updates, and help flush the remaining gremlins out of the system.

On a side-note, Since switching from 6.2.19 to 6.10.58, I have noticed that my cache is not being processed in FIFO. It is all APs..about 17 days worth, and APs with a deadline four days sooner than the ones that keep getting picked to run next are still sitting there not getting started.

I know there are cache/queue changes along the way through the build history, but each WU has a 25-day deadline, so wouldn't it still make sense to run the soonest deadlines first (which also happen to be the ones that were acquired first)? I mean, it works out in the end I'm sure, but it's just weird.

Welp... Looks like the cricket graph just bottomed out. :(

On a side-note, Since switching from 6.2.19 to 6.10.58, I have noticed that my cache is not being processed in FIFO. It is all APs..about 17 days worth, and APs with a deadline four days sooner than the ones that keep getting picked to run next are still sitting there not getting started.

I know there are cache/queue changes along the way through the build history, but each WU has a 25-day deadline, so wouldn't it still make sense to run the soonest deadlines first (which also happen to be the ones that were acquired first)? I mean, it works out in the end I'm sure, but it's just weird.

Not true. FIFO does not necessarliy equate to EDF (earliest deadline first). A task's deadline is determined by how long it is estimated to take to run. So it is possible to download a bunch of tasks yesterday estimated to take 20 hours to run and have deadlines in late January, and then a bunch today estimated to take 1 hour and have deadlines in mid-December. And don't forget, if you're running more than one project, Boinc has to balance all of them, and different projects do their time estimates and deadlines differently.

However, if all of the tasks you're looking at have the same time estimate, then I agree, it is weird for them not to run FIFO, which presumably is also EDF.

If tasks from the same download batch don't appear to run in FIFO (and be very careful to observe that you haven't applied a sort order to one of the columns in BOINC Manager, before you jump to that conclusion), then it's a long-standing bug which applies some slight randomisation to the display order when data is transferred from the server to the BOINC Client to the BOINC Manager. In short, it's cosmetic only.

BOINC v6.10.58 is still a very old version. We applied a lot of pressure to get that bug (and many others) fixed - I forget just when. The latest ones - I'm running v7.0.38 - have had display order and running order in perfect step for a long time - possibly even since sometime in the v6.12.xx range - but I wouldn't advise upgrading just for this. Like I said, it's cosmetic only.

Well I'm back to NNT if I want to get an acknowledge from the server of the tasks being reported. Allowing tasks greets me with

11/20/2012 11:21:44 PM | SETI@home | work fetch resumed by user
11/20/2012 11:25:39 PM | SETI@home | Sending scheduler request: To fetch work.
11/20/2012 11:25:39 PM | SETI@home | Requesting new tasks for CPU and ATI
11/20/2012 11:25:47 PM | | Project communication failed: attempting access to reference site
11/20/2012 11:25:47 PM | SETI@home | Scheduler request failed: Failure when receiving data from the peer
11/20/2012 11:25:49 PM | | Internet access OK - project servers may be temporarily down.
11/20/2012 11:27:13 PM | SETI@home | Sending scheduler request: To fetch work.
11/20/2012 11:27:13 PM | SETI@home | Requesting new tasks for CPU and ATI
11/20/2012 11:32:26 PM | | Project communication failed: attempting access to reference site
11/20/2012 11:32:26 PM | SETI@home | Scheduler request failed: Timeout was reached
11/20/2012 11:32:28 PM | | Internet access OK - project servers may be temporarily down.

I currently have 15 ghosts, all GPU units, and I'm now down to 104 units "In Progress" counting those ghosts. I'm probably down to under 2 days worth of units for either the CPU or GPU and the only reason I haven't run out of GPU units, other that it's a weak GPU, is I routinely suspend GPU crunching to play games or watch movies.

Well Turkey day is coming up, I guess even a computer could use the break.
____________
"Life is just nature's way of keeping meat fresh." - The Doctor

Well, since the outage i've picked up some work. I'm also getting new errors when trying to contact the Scheduler.
Still getting the timeouts, but to add to that i'm now getting "Server returned nothing (no headers, no data)" & "Failure when receiving data from the peer".
As before, even with NNT set, it appears to depend on the wind direction & how you hold your tongue while clicking repatedly on the retry button as to whether or not you will get a response from the Scheduler.
____________
Grant
Darwin NT.

As expected, with the AP splitters not running this morning I am able to connect and and the tasks are flowing quite well.

Frank

My i7 is finally up to its full 200 WU limit. I suppose this means it finished enough Einstein GPU work to ask Seti for some, and the Seti servers were actually able to deliver it.

I also see that the five APs I got yesterday are done already, four valid and one pending.

____________
David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Still getting the timeouts, but to add to that i'm now getting "Server returned nothing (no headers, no data)" & "Failure when receiving data from the peer".

After the change(s) this afternoon, I had several nodes that had empty caches but could not get a successful scheduler update. I was able to get them to start downloading some tasks by decreasing the minimum work buffer to 0.25 days. Now they are slowly getting some resent tasks.
____________

After I flushed the DNS caches on all my nodes I was able to go back to multi-day work buffers and got scheduler updates to complete.
____________