I had the same problem around the time you posted your message.
Things seem to be working again. I just received 40 (!) new workunits and they downloaded really fast (less than 1.5 minutes for all 40 of them). No big surprise as the cricket graph isn't maxed out, but still nice to see ...

Now i'm not getting any response from the Scheduler.

---

Now i'm not getting any response from the Scheduler.

Now it's back again.
But for a while there it wasn't.

1/10/2011 19:14:59 SETI@home Sending scheduler request: To fetch work.
1/10/2011 19:14:59 SETI@home Reporting 4 completed tasks, requesting new tasks for CPU and GPU
1/10/2011 19:15:22 Project communication failed: attempting access to reference site
1/10/2011 19:15:22 SETI@home Scheduler request failed: Couldn't connect to server
1/10/2011 19:15:25 Internet access OK - project servers may be temporarily down.
1/10/2011 19:16:22 SETI@home Sending scheduler request: To fetch work.
1/10/2011 19:16:22 SETI@home Reporting 4 completed tasks, requesting new tasks for CPU and GPU
1/10/2011 19:16:44 Project communication failed: attempting access to reference site
1/10/2011 19:16:44 SETI@home Scheduler request failed: Couldn't connect to server
1/10/2011 19:16:46 Internet access OK - project servers may be temporarily down.
1/10/2011 19:17:44 SETI@home Sending scheduler request: To fetch work.
1/10/2011 19:17:44 SETI@home Reporting 6 completed tasks, requesting new tasks for CPU and GPU
1/10/2011 19:18:40 SETI@home Scheduler request failed: HTTP internal server error
1/10/2011 19:19:40 SETI@home Sending scheduler request: To fetch work.
1/10/2011 19:19:40 SETI@home Reporting 6 completed tasks, requesting new tasks for CPU and GPU
1/10/2011 19:20:00 SETI@home Computation for task 17ap11ah.22009.16427.6.10.174_0 finished
1/10/2011 19:20:16 Project communication failed: attempting access to reference site
1/10/2011 19:20:16 SETI@home Scheduler request failed: Failure when receiving data from the peer
1/10/2011 19:20:18 Internet access OK - project servers may be temporarily down.

Now it's mostly "Project has no tasks available"

---

Grant
Darwin NT

The main message for my 3 PC's for the last 4-6 hours has been, "This computer has reached a limit on tasks in progress", with the occasional 1-10 tasks being received every 4th or 5th request.

Cheers.

---

S@H has been running with a cap on tasks in progress (in other words a limit on the number of tasks you can have on each cruncher) for some time.
Each cruncher is allowed 50 per CPU core, and 400 per GPU.

(My figures might be wrong, I deduced them from the number of tasks on my crunchers.)

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Well after a fair period of no uploads or downloads it seems that the system has settled and all the gripes can be forgotten until the next time, no expectations no regrets lets all do it for the one in a bazillion chance to say we have proven that there is life out there beyond our little blue planet.

Keep on crunching and greetings to all on our little planet called Earth.

---

Someone must have kicked the routers at HE very hard - yiiihhha
Just got 40 WUs and downloaded them in under 2 minutes, in spite of cricket nearly maxed out - and pinging the servers is as fast as never before (from my point of the world) :-) .

__W__

---

_______________________________________________________________________________

The main message for my 3 PC's for the last 4-6 hours has been, "This computer has reached a limit on tasks in progress", with the occasional 1-10 tasks being received every 4th or 5th request.

Cheers.

Each one of your three hosts shows either 449 or 450 tasks in progress. That's the current limit for CPU and GPU tasks combined. Subject to the usual caveats about hitting the feeder when it has suitable tasks available, you'll get a fresh task in exchange for each completed task you return.

The main message for my 3 PC's for the last 4-6 hours has been, "This computer has reached a limit on tasks in progress", with the occasional 1-10 tasks being received every 4th or 5th request.

Cheers.

Each one of your three hosts shows either 449 or 450 tasks in progress. That's the current limit for CPU and GPU tasks combined. Subject to the usual caveats about hitting the feeder when it has suitable tasks available, you'll get a fresh task in exchange for each completed task you return.

Yes it's certainly nowhere near my usual cache capacity but then again I also have quite a bit of CPU work from backup projects for a safety buffer (so far it only seems to be CPU work that I run out of, the GPU work has remained SETI only).

Cheers.

---

Somebody must be in the lab, the scheduling server is now showing as disabled.

---

PROUD MEMBER OF Team Starfire World BOINC

Somebody must be in the lab, the scheduling server is now showing as disabled.

Well, it isn't disabled, because I just reported 20 tasks. Did you check the status page for the server status page? ;-)

Seriously, all of those 'status' flags are indicative only. A script tests each server/daemon periodically to see if it's in some sense 'responsive'. The result of the test goes into a disk file somewhere, and that's what we see as being the status for the next 10 or 20 minutes, until the next page update. The daemons also have watchdog scripts which restart them if they stop running.

All of which means that the scheduling server might have glitched for a second and been restarted. That's the most we can deduce from the SSP - a single server down for a single observing cycle isn't enough to conclude that maintenance is underway (and if the staff do shut a server down manually, they usually shut down a whole block of them).

Somebody must be in the lab, the scheduling server is now showing as disabled.

Well, it isn't disabled, because I just reported 20 tasks. Did you check the status page for the server status page? ;-)

Seriously, all of those 'status' flags are indicative only. A script tests each server/daemon periodically to see if it's in some sense 'responsive'. The result of the test goes into a disk file somewhere, and that's what we see as being the status for the next 10 or 20 minutes, until the next page update. The daemons also have watchdog scripts which restart them if they stop running.

All of which means that the scheduling server might have glitched for a second and been restarted. That's the most we can deduce from the SSP - a single server down for a single observing cycle isn't enough to conclude that maintenance is underway (and if the staff do shut a server down manually, they usually shut down a whole block of them).

Plus, today is Saturday, not a normal work day for the S@H gang.

---

Donald
Infernal Optimist / Submariner, retired

I had success at 15:56:19, but not at 16:01:50, 16:07:27 or 16:13:19.

Think I also detect a nose dive starting on cricket.

edit]uploads are ok.

I had success at 15:56:19, but not at 16:01:50, 16:07:27 or 16:13:19.

Think I also detect a nose dive starting on cricket.

edit]uploads are ok.

All my fault, I had most of my rigs shut down and had just restarted 2 of them. Downloads failed as soon as the 2nd one booted up and asked for work.

(Just wondering. Is there any way we can blame Misfit for this ? He hasn't been around for a long time but......)

T.A.

Well, I checked the server status page just before I posted that and it had refreshed just one minute before I did. That's why I posted it as showing disabled.


TA, we can always blame Misfit. Actually, I kinda miss him. Wonder how he's doing?

---

PROUD MEMBER OF Team Starfire World BOINC

Something's definitely wrong. I just uploaded a pile of units and then sent all the results in to s&h. This morning I even got some new WUs.
I am worried that this may not be what is supposed to happen ;)

---

For some reason my Linux pc's can still report (and get new work) while my Windows pc's all get the "unable to connect to server" or "HTTP error" message. Same thing happened yesterday when the Linux pc's were still able to get through.

The Cricket graphs clearly show that something happened about an hour ago.

---

Seti@Netherlands website

TA, we can always blame Misfit. Actually, I kinda miss him. Wonder how he's doing?

Same here, I still occasionally go look at his profile when I want a grin.

More worryingly, I just got

01/10/2011 18:03:21 | SETI@home | Sending scheduler request: Requested by user.
01/10/2011 18:03:21 | SETI@home | Reporting 14 completed tasks, requesting new tasks for CPU and NVIDIA GPU
01/10/2011 18:03:21 | SETI@home | [sched_op] CPU work request: 673473.12 seconds; 0.00 CPUs
01/10/2011 18:03:21 | SETI@home | [sched_op] NVIDIA GPU work request: 154670.17 seconds; 0.00 GPUs
01/10/2011 18:04:22 | SETI@home | Scheduler request failed: HTTP internal server error
01/10/2011 18:04:22 | SETI@home | [sched_op] Deferring communication for 1 min 30 sec

The 14 tasks got reported OK, because the 'in progress' count for that host on the website is now 14 fewer than the number of tasks BoincView is counting - I never got the 'ack' for successful reporting of those tasks, so BOINC locally still thinks they're 'ready to report'.

Edit - whatever it was, was only temporary. The tasks reported properly and were acknowledged a couple of attempts later, and I got some new work.

Just tried to to report work from the old P4 and its a no go. Says servers may be down. the Mac has two work units that I got sometime today. This I7 still has 4 Einstiens I want to finish befor I request new work. Think I will get some?

And downloads from Einstien havent been very fast the past few days either. Ive had one trying since this morning.

Ill join Chris at the pub.

---

[/quote]

Old James

Daren't go to pub. The only way i can get uploads and reports through is to sit here constantly hitting the retry button. Just to add insult to injury, I jave got a whole load of 12s megashorties that take 12s to abort and then 12 minutes to upload and another 12 minutes to report. Have to go now still got WU to report again and again and again....

EDIT guess what while I was typing this the report went through. Now I have 14 minutes free till the next shortie finishes. How many pints can I drink in 14 minutes?