Just got back from a long weekend up in Portland, OR (attending a friend's wedding, then visiting other friends/family while up in that rather charming part of the country). It was a busy weekend while I was away.

We had a lab-wide scheduled outage which Jeff managed in my absence. It went flawlessly except for two things. First, rebooting all the routers in the lab exposed some sort of mysterious configuration problem. Since a lot of parties were involved with troubleshooting and trying this and trying that it is still unclear what actually eventually fixed the problem. Second, beta uploads were failing in a weird way: files were being created on our servers but they were all zero length. Jeff, Eric, and I hammered on this all morning but Eric only figured out just now that it was nfsd running on the upload file server, which was otherwise working just fine. It needed to be kicked (i.e. restarted).

Meanwhile we had the usual Tuesday outage with the kicker that we didn't actually have to stop the httpd servers. Clients could still connect to our schedulers
and upload/download work as much as possible without any of the back end connecting to our database. Hopefully this was much more of a user friendly experience than usual. Of course, due to the outage recovery over the weekend we ran out of excess work to send out, so demand is artificially high right now. Ugh.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Matt--can someone else do these updates on Friday when you're out please?

Thx

---

Just to confirm, are the servers down or not, i havent been able to download any new info or upload either, in the past few days. Maybe its just me.

---

I seem to be having the same problem. The server status page shows 2K plus units ready to send, but I keep getting the message that there is no work from the project.
Glad you had some R&R time. Portland is really nice this time of year.

---

I too have not been able to download any any work. The only files that have been downloaded are a bunch of png files

---

I've been having the same problems since the weekend. my communications gets constantly deferred and repeated messages stating the server isn't sending any work and "reached daily quota of 2 results" (whatever that means)

Any Ideas on what the problem is? My average work done went from 500+ down to 16.86 within the past week.

---

I seem to be having the same problem. The server status page shows 2K plus units ready to send, but I keep getting the message that there is no work from the project.
Glad you had some R&R time. Portland is really nice this time of year.

2000 is a very small number.

Odds are good that the splitters aren't keeping up with the demand, especially after the weekend outage.

---

any problems you may be having - see this: Server status page

> my time in North Carolina is 12:19 AM EST

any problems you may be having - see this: Server status page

That's probably where the "2k" figure came from... ;-,)

> my time in North Carolina is 12:19 AM EST

Currently (at 10.26 PDT [5.26 GMT]) there's nothing in the "Results ready to send" queue... this is another reason to run more than one BOINC project... [edit][snip][/edit] (got some as I was originally posting this!)


Matt,

After a big weekend outage like we had this weekend, wouldn't it make sense to postpone the "weekly" outage to Thursday, so the "results ready to send" queue could be full before the "weekly" outage?

---

.

Hello, from Albany, CA!...

All that incidences, are the reasons for what many users (like me) increases the 'additional days of cache' before an outage...

Best regards.


Logan.
(sorry for my english)

I've been having the same problems since the weekend. my communications gets constantly deferred and repeated messages stating the server isn't sending any work and "reached daily quota of 2 results" (whatever that means)

Due to various issues/reasons, the server decided- for now- that you should be getting at most two WU's per day (your 'quota'). I think.

Any Ideas on what the problem is? My average work done went from 500+ down to 16.86 within the past week.

Have you had any WU's abort or disconnected/discarded. I've heard that if the server's think that's happening, it'll tell itself "Slow this guy down; Give him time to figure out what's wrong."
My second idea is: How many projects are you working on at the same time? (This affects ME the most.)

---

Is it me or does the overall amount of work seem way down from say a year or so ago? Forgive me if the question is silly but I've not been following all the threads in granular enough detail if this question seems to obvious to some. Thanks.

I've been having the same problems since the weekend. my communications gets constantly deferred and repeated messages stating the server isn't sending any work and "reached daily quota of 2 results" (whatever that means)

Any Ideas on what the problem is? My average work done went from 500+ down to 16.86 within the past week.

Your computer is erroring out with the following ....

exit code 1

For every bad result your quota is reduced by 1. That is why you are only getting 2 workunits a day.

Please post in Q&A and someone will be able to help you.

---

Is it me or does the overall amount of work seem way down from say a year or so ago? Forgive me if the question is silly but I've not been following all the threads in granular enough detail if this question seems to obvious to some. Thanks.

There was a recent reduction of the ready-to-send queue from 500k to 200k (I think those numbers are right)... Normally that shouldn't be a problem, but it does tend to bottom out during outages.

In response to everyone who compulsively twiddles their queue when they know an outage is coming: don't. The more you do the manually screw with the system the harder time it has keeping up. If you run a reasonable queue (I think mine is set to 3 days) and run multiple projects from different sources (ie, count SETI and SETIbeta as one because they're likely to go down at the same times) you should have no trouble at all keeping your computer busy. Need I remind you while going for the most credits possible is fun, it's still the science we're going for here.

---

Today I've been getting these kinds of messages all day, when trying to report finished work and when requesting new work;
25.07.2007 22:13:54|SETI@home|Reporting 2 tasks
25.07.2007 22:13:59|SETI@home|Scheduler request failed: HTTP file not found
25.07.2007 22:13:59|SETI@home|Deferring communication for 1 min 0 sec
25.07.2007 22:13:59|SETI@home|Reason: scheduler request failed

Something wrong on serverside? Tested and checked everything possible at my end.

---

Perhaps the router problem they had last week has resurfaced today. I've seen the same thing here.

Today I've been getting these kinds of messages all day, when trying to report finished work and when requesting new work;
25.07.2007 22:13:54|SETI@home|Reporting 2 tasks
25.07.2007 22:13:59|SETI@home|Scheduler request failed: HTTP file not found
25.07.2007 22:13:59|SETI@home|Deferring communication for 1 min 0 sec
25.07.2007 22:13:59|SETI@home|Reason: scheduler request failed

Something wrong on serverside? Tested and checked everything possible at my end.

---

I have the same problem on four systems here :-(

7/25/2007 4:27:51 PM|SETI@home|Sending scheduler request: Requested by user
7/25/2007 4:27:51 PM|SETI@home|Requesting 582 seconds of new work, and reporting 1 completed tasks
7/25/2007 4:28:56 PM|SETI@home|Scheduler request failed: HTTP service unavailable
7/25/2007 4:28:56 PM|SETI@home|Sending scheduler request: Requested by user
7/25/2007 4:28:56 PM|SETI@home|Requesting 703 seconds of new work, and reporting 1 completed tasks
7/25/2007 4:29:01 PM|SETI@home|Scheduler request failed: HTTP file not found
7/25/2007 4:29:01 PM|SETI@home|Deferring communication for 52 min 36 sec
7/25/2007 4:29:01 PM|SETI@home|Reason: scheduler request failed

---

Same here. Worked o.k. for about 2 days, then zilch. I'm getting way behind on my ranking. Isn't that what this is all about?
:>))

Steve Gaber

25/07/2007 22:30:43|SETI@home|Sending scheduler request: To fetch work
25/07/2007 22:30:43|SETI@home|Requesting 8 seconds of new work
25/07/2007 22:32:19|SETI@home|Scheduler request failed: HTTP service unavailable
25/07/2007 22:32:19|SETI@home|Deferring communication for 1 min 0 sec
25/07/2007 22:32:19|SETI@home|Reason: scheduler request failed
25/07/2007 22:33:19|SETI@home|Sending scheduler request: To fetch work
25/07/2007 22:33:19|SETI@home|Requesting 209 seconds of new work
25/07/2007 22:34:29|SETI@home|Scheduler request failed: HTTP service unavailable
25/07/2007 22:34:29|SETI@home|Deferring communication for 1 min 0 sec
25/07/2007 22:34:29|SETI@home|Reason: scheduler request failed
25/07/2007 22:35:29|SETI@home|Sending scheduler request: To fetch work
25/07/2007 22:35:29|SETI@home|Requesting 361 seconds of new work
25/07/2007 22:36:39|SETI@home|Scheduler request failed: HTTP service unavailable
25/07/2007 22:36:39|SETI@home|Deferring communication for 1 min 0 sec
25/07/2007 22:36:39|SETI@home|Reason: scheduler request failed
25/07/2007 22:37:39|SETI@home|Sending scheduler request: To fetch work
25/07/2007 22:37:39|SETI@home|Requesting 395 seconds of new work
25/07/2007 22:38:49|SETI@home|Scheduler request failed: HTTP service unavailable
25/07/2007 22:38:49|SETI@home|Deferring communication for 1 min 0 sec
25/07/2007 22:38:49|SETI@home|Reason: scheduler request failed
25/07/2007 22:39:49|SETI@home|Sending scheduler request: To fetch work
25/07/2007 22:39:49|SETI@home|Requesting 558 seconds of new work
25/07/2007 22:40:59|SETI@home|Scheduler request failed: HTTP service unavailable
25/07/2007 22:40:59|SETI@home|Deferring communication for 1 min 10 sec
25/07/2007 22:40:59|SETI@home|Reason: scheduler request failed
25/07/2007 22:42:14|SETI@home|Sending scheduler request: To fetch work
25/07/2007 22:42:14|SETI@home|Requesting 723 seconds of new work
25/07/2007 22:43:24|SETI@home|Scheduler request failed: HTTP service unavailable
25/07/2007 22:43:24|SETI@home|Deferring communication for 5 min 22 sec
25/07/2007 22:43:24|SETI@home|Reason: scheduler request failed
25/07/2007 22:48:50|SETI@home|Sending scheduler request: To fetch work
25/07/2007 22:48:50|SETI@home|Requesting 1045 seconds of new work
25/07/2007 22:50:00|SETI@home|Scheduler request failed: HTTP service unavailable
25/07/2007 22:50:00|SETI@home|Deferring communication for 16 min 52 sec
25/07/2007 22:50:00|SETI@home|Reason: scheduler request failed


Here too, but I have enough WU's in the cache to process...

Same problem here.

7/25/2007 5:30:20 PM|SETI@home|Requesting 10486 seconds of new work, and reporting 2 completed tasks
7/25/2007 5:30:45 PM|SETI@home|Scheduler request failed: HTTP file not found
7/25/2007 5:30:45 PM|SETI@home|Sending scheduler request: Requested by user
7/25/2007 5:30:45 PM|SETI@home|Requesting 10486 seconds of new work, and reporting 2 completed tasks
7/25/2007 5:32:05 PM|SETI@home|Scheduler request failed: HTTP service unavailable
7/25/2007 5:32:05 PM|SETI@home|Deferring communication for 2 min 13 sec
7/25/2007 5:32:05 PM|SETI@home|Reason: scheduler request failed

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)