I have been unable to send back completed work units or get new one for approximately 1 1/2 weeks now, is there still a problem with wanadoo.fr? I am using a proxie 57.67.8.114 on port 80.
This new BOINC system is frustrating and I'm thinking of scrapping the lot; with the old system I was in the top 6% now there is no communication and BOINC slows my machine down badly.
Whats happening out there?

---

I have been unable to send back completed work units or get new one for approximately 1 1/2 weeks now, is there still a problem with wanadoo.fr? I am using a proxie 57.67.8.114 on port 80.
This new BOINC system is frustrating and I'm thinking of scrapping the lot; with the old system I was in the top 6% now there is no communication and BOINC slows my machine down badly.
Whats happening out there?

Not much people can do to help because your computers are hidden! Means we can't see what is going wrong. Did you try changing proxies? I have had problems, I do not use a proxy, but Berkeley seems to be and running just fine right now.
This link: http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html
will show how Berkeley is connecting with the outside world. The first top left box is the in/out.

---

Thank you Mikey, I took out the proxy that I had to use when they had the problem with cogent, it sort of works now. I also upgraded to BOINC 4.45 having read some of the other posts. However while I have now been able to send back the completed work units, I appear to be unable to unload anymore work and in looking at my account I cannot see any of the past work, even though I have been a seti@home member since 1999.

---

...I cannot see any of the past work, even though I have been a seti@home member since 1999.

Here, http://setiathome.berkeley.edu/show_user.php?userid=375814, you show SETI BOINC credit of 5,859.25. 5,200.85 credits on computer ID 453566 and 658.40 credits on computer ID 486058. You also show, as of March 15, 2005, 800 SETI@home classic workunits and 8,948 hours SETI@home classic CPU time.

What past work isn't showing?

---

Help and BOINC documentation is available here.

Thank you Mikey, I took out the proxy that I had to use when they had the problem with cogent, it sort of works now. I also upgraded to BOINC 4.45 having read some of the other posts. However while I have now been able to send back the completed work units, I appear to be unable to unload anymore work and in looking at my account I cannot see any of the past work, even though I have been a seti@home member since 1999.

You missed the dealine on those last work units.

check this one.

<P>

---

Red Bull Air Racing

Gas price by zip at Seti

...I cannot see any of the past work, even though I have been a seti@home member since 1999.

Here, http://setiathome.berkeley.edu/show_user.php?userid=375814, you show SETI BOINC credit of 5,859.25. 5,200.85 credits on computer ID 453566 and 658.40 credits on computer ID 486058. You also show, as of March 15, 2005, 800 SETI@home classic workunits and 8,948 hours SETI@home classic CPU time.

What past work isn't showing?

I used to be able to see all of the past work units on the BOINC system now when I go to my account I see only the last 5 uploaded since I changed versions of BOINC. Moreover, having had a problem and changed the version of BOINC I managed to upload the work units now I don't seem to be able to download anything. I know I missed the deadline thats because I had the problem in the first place.

So all of you clever people out there let me, the poor old man know what it is that I have done wrong.

I suffered the Wanadoo argument through France telecom, I changed versions of BOINC, I have tried proxies as recommended elsewhere and I agree I am a bit dim in the detailed computer knowledge required to fix the problem immediately. I learned computing when operating systems were tape resident and you buttoned in the instructions in hex with punch cards to load the program!! I shall continue to experiment, if you have a constructive recomendation, please feel free to help me out.

I attach the error messages for the last attempt in case they mean anything

20/06/2005 00:04:13||Starting BOINC client version 4.45 for windows_intelx86
20/06/2005 00:04:13||Data directory: C:\Program Files\BOINC
20/06/2005 00:04:13|SETI@home|Computer ID: 453566; location: home; project prefs: default
20/06/2005 00:04:13||General prefs: from SETI@home (last modified 2005-06-19 10:28:34)
20/06/2005 00:04:13||General prefs: no separate prefs for home; using your defaults
20/06/2005 00:04:13||Remote control not allowed; using loopback address
20/06/2005 00:04:13||Insufficient work; requesting more
20/06/2005 00:04:13|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 00:04:13|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 00:04:22||request_reschedule_cpus: project op
20/06/2005 00:04:36|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 00:04:36|SETI@home|No schedulers responded
20/06/2005 00:04:37|SETI@home|Deferring communication with project for 6 minutes and 1 seconds
20/06/2005 00:04:53||request_reschedule_cpus: project op
20/06/2005 00:04:54|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 00:04:54|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 00:05:15|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 00:05:15|SETI@home|No schedulers responded
20/06/2005 00:05:16|SETI@home|Deferring communication with project for 14 minutes and 28 seconds
20/06/2005 00:19:46|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 00:19:46|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 00:20:07|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 00:20:07|SETI@home|No schedulers responded
20/06/2005 00:20:08|SETI@home|Deferring communication with project for 22 minutes and 37 seconds
20/06/2005 00:22:34||request_reschedule_cpus: project op
20/06/2005 00:22:34|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 00:22:34|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 00:22:55|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 00:22:55|SETI@home|No schedulers responded
20/06/2005 00:22:56|SETI@home|Deferring communication with project for 53 minutes and 30 seconds
20/06/2005 00:30:37||request_reschedule_cpus: project op
20/06/2005 00:30:37|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 00:30:37|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 00:30:38||request_reschedule_cpus: project op

---

...I cannot see any of the past work, even though I have been a seti@home member since 1999.

Here, http://setiathome.berkeley.edu/show_user.php?userid=375814, you show SETI BOINC credit of 5,859.25. 5,200.85 credits on computer ID 453566 and 658.40 credits on computer ID 486058. You also show, as of March 15, 2005, 800 SETI@home classic workunits and 8,948 hours SETI@home classic CPU time.

What past work isn't showing?

I used to be able to see all of the past work units on the BOINC system now when I go to my account I see only the last 5 uploaded since I changed versions of BOINC. Moreover, having had a problem and changed the version of BOINC I managed to upload the work units now I don't seem to be able to download anything. I know I missed the deadline thats because I had the problem in the first place.

So all of you clever people out there let me, the poor old man know what it is that I have done wrong.

I suffered the Wanadoo argument through France telecom, I changed versions of BOINC, I have tried proxies as recommended elsewhere and I agree I am a bit dim in the detailed computer knowledge required to fix the problem immediately. I learned computing when operating systems were tape resident and you buttoned in the instructions in hex with punch cards to load the program!! I shall continue to experiment, if you have a constructive recomendation, please feel free to help me out.

When a WU has been validated it will be removed from the database to save disk space etc. Four WUs are sent out and once all four have been returned and validated or three have been returned and validated and the deadline has passed for the fourth then a WU will be eligible to be removed from the database that we see for the results. I am not sure of the time scales for when this database cleanup takes place.

You also mention that you can upload but not download. If uploads are happening then your network connection must be OK. I wonder if you have accidentally set the project to "no new work". Open boinc manager, select the seti@home project and check which buttons are available on the lefthand side. If you see "Allow new work" you must have accidentally stopped it downloading, click on this button to allow the client to download work.

---

...I cannot see any of the past work, even though I have been a seti@home member since 1999.

Here, http://setiathome.berkeley.edu/show_user.php?userid=375814, you show SETI BOINC credit of 5,859.25. 5,200.85 credits on computer ID 453566 and 658.40 credits on computer ID 486058. You also show, as of March 15, 2005, 800 SETI@home classic workunits and 8,948 hours SETI@home classic CPU time.

What past work isn't showing?

I used to be able to see all of the past work units on the BOINC system now when I go to my account I see only the last 5 uploaded since I changed versions of BOINC.

Hi Pierre,

you can find a post by "paul d Buck" and click on either the link to the "Boinc documentation" or the "Wiki" and research this further. Try looking up "Validation", "Purger", and "Deleter". Or you can do a keyword search of these boards for those words.

Basically, this is how it works. A result (work unit) is sent out to four (4) hosts. The Validator cycles through the Database, and when it sees that 3 have been returned it tries to Validate them. I looks at the answers each host returned. If they are comparable then it does the calculations and issues credit. Once the WU are validated the answer becomes a canonical result and is moved to a different DB. At this point the answers are not needed and are infact just taking up DB memory without reason. Thats when the "Deleter/purger" get involved and removes the answers from the DB making more room.

Early in Boinc the Deleter/purger wasn't being run but every so often, and so you could look at your results from 3 months ago, but now it's online and working. This is why you can't review your old Results.

does this help?

tony

Just one more side note, there was a time earlier this year when you could see results from longer timespan into the past. That was because UCB was not running the several of the background tasks. Now, however, they are and the database is scavenged fairly rapidly.

To be honest, I wish there was sufficient capactity for them to have left that information on-line ... even better would be to have all the science data available too ... but ... probably won't happen in my lifetime ...

---

[/quote]
When a WU has been validated it will be removed from the database to save disk space etc. Four WUs are sent out and once all four have been returned and validated or three have been returned and validated and the deadline has passed for the fourth then a WU will be eligible to be removed from the database that we see for the results. I am not sure of the time scales for when this database cleanup takes place.

You also mention that you can upload but not download. If uploads are happening then your network connection must be OK. I wonder if you have accidentally set the project to "no new work". Open boinc manager, select the seti@home project and check which buttons are available on the lefthand side. If you see "Allow new work" you must have accidentally stopped it downloading, click on this button to allow the client to download work.


[/quote]
Thank you to all who explained the purging I now understand. However, from the side panel I see that I am set up to receive work (ie 'no new work' showing on the button) but cannot for some reason get any, indeed it is now 3 days without anything: here are the last set of messages: and I am none the wiser!!


20/06/2005 18:48:28||Starting BOINC client version 4.45 for windows_intelx86
20/06/2005 18:48:28||Data directory: C:\Program Files\BOINC
20/06/2005 18:48:28|SETI@home|Computer ID: 453566; location: home; project prefs: default
20/06/2005 18:48:28||General prefs: from SETI@home (last modified 2005-06-19 10:28:34)
20/06/2005 18:48:28||General prefs: no separate prefs for home; using your defaults
20/06/2005 18:48:28||Remote control not allowed; using loopback address
20/06/2005 18:48:28||Insufficient work; requesting more
20/06/2005 18:48:28|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 18:48:28|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 18:49:23|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 18:49:23|SETI@home|No schedulers responded
20/06/2005 18:49:24|SETI@home|Deferring communication with project for 59 seconds
20/06/2005 18:50:44|SETI@home|Master file fetch failed
20/06/2005 18:50:45|SETI@home|Deferring communication with project for 59 seconds
20/06/2005 18:51:45|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 18:51:45|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 18:52:06|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 18:52:06|SETI@home|No schedulers responded
20/06/2005 18:52:07|SETI@home|Deferring communication with project for 59 seconds
20/06/2005 18:53:06|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 18:53:06|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 18:53:27|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 18:53:27|SETI@home|No schedulers responded
20/06/2005 18:53:28|SETI@home|Deferring communication with project for 59 seconds
20/06/2005 18:54:28|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 18:54:28|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 18:54:49|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 18:54:49|SETI@home|No schedulers responded
20/06/2005 18:54:50|SETI@home|Deferring communication with project for 1 minutes and 12 seconds
20/06/2005 18:56:04|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 18:56:04|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 18:56:25|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 18:56:25|SETI@home|No schedulers responded
20/06/2005 18:56:26|SETI@home|Deferring communication with project for 2 minutes and 44 seconds
20/06/2005 18:59:11|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/06/2005 18:59:11|SETI@home|Requesting 432000 seconds of work, returning 0 results
20/06/2005 18:59:32|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
20/06/2005 18:59:32|SETI@home|No schedulers responded
20/06/2005 18:59:33|SETI@home|Deferring communication with project for 6 minutes and 7 seconds

---

Hey Pierre could you cut n paste your preference to this post it may help.

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

Looks to me like BOINC cannot see the internet. First thing to check is if that computer can see the site ... if the computer you post to the internet is the same one with the error, this test passed, if not, try to connect to the web page with your browser ...

If that works, check to see if the firewall rules allow BOINC to get out. You can try this by just turning off the fire wall for a moment and do a forced update, if that works, the firewall is blocking the access ...

---

This appears to be a similar problem to one I'm having in this thread http://setiathome.berkeley.edu/forum_thread.php?id=15890

Live long and crunch.

---

Paul
(S@H1 8888)
And proud of it!

[/quote]
Thank you to all who explained the purging I now understand. However, from the side panel I see that I am set up to receive work (ie 'no new work' showing on the button) but cannot for some reason get any, indeed it is now 3 days without anything: here are the last set of messages: and I am none the wiser!!

[/quote]
========================
Looking at your returned results, most of them came back/were reported late. Check your connect to network setting and reduce it.

Thank you to all who explained the purging I now understand. However, from the side panel I see that I am set up to receive work (ie 'no new work' showing on the button) but cannot for some reason get any, indeed it is now 3 days without anything: here are the last set of messages: and I am none the wiser!!

[/quote]
========================
Looking at your returned results, most of them came back/were reported late. Check your connect to network setting and reduce it. [/quote]

Holy cow, did you really read his problem. He has not been able to connect and when he finally could his results were late. So his "connect to" preference is not causing a problem.

Paul.

========================
Looking at your returned results, most of them came back/were reported late. Check your connect to network setting and reduce it.

Holy cow, did you really read his problem. He has not been able to connect and when he finally could his results were late. So his "connect to" preference is not causing a problem.

Paul.

==================
Golly gee Batman, we're all tossing out ideas here. Looking at some of the earlier posts he upgraded to the 4.45 core which helps return finished units on time. If his connect time is greater than the finished units return time, the schedueler isn't going to let him DL anything.

The completed units that show just barely made it under the 14 day limit.

---

Thanks for the support all of you I am still unable to download work units, I have changed the preferences to 4 days. The message that concerns me is the following:
21/06/2005 18:06:09|SETI@home|Master file fetch failed

Its as though reinstalling a new version of BOINC has lost an addressing file somewhere, yet I can see and modify all of my account details. Seems a shame that I can't continue, I was really only interested in SETI so I didn't need BOINC, the classic worked perfectly without a hitch!

---

Thanks for the support all of you I am still unable to download work units, I have changed the preferences to 4 days. The message that concerns me is the following:
21/06/2005 18:06:09|SETI@home|Master file fetch failed

Its as though reinstalling a new version of BOINC has lost an addressing file somewhere, yet I can see and modify all of my account details. Seems a shame that I can't continue, I was really only interested in SETI so I didn't need BOINC, the classic worked perfectly without a hitch!

Pierre,

That is an indicator that the BOINC application cannot connect to the internet. Most likely the firewall is blocking access.

---

I'm having a similar problem, I can't connect to the server to report my results and d/l new work....and I have just a few days left to report some of my work....

6/21/2005 1:11:56 PM||Starting BOINC client version 4.45 for windows_intelx86
6/21/2005 1:11:56 PM||Data directory: C:\Program Files\BOINC
6/21/2005 1:11:56 PM||Version Change Detected (4.25 -> 4.45); running CPU benchmarks
6/21/2005 1:11:56 PM|SETI@home|Computer ID: 836413; location: home; project prefs: default
6/21/2005 1:11:56 PM||General prefs: from SETI@home (last modified 2005-04-29 21:40:12)
6/21/2005 1:11:56 PM||General prefs: no separate prefs for home; using your defaults
6/21/2005 1:11:56 PM||Remote control not allowed; using loopback address
6/21/2005 1:11:58 PM||Running CPU benchmarks
6/21/2005 1:12:55 PM||Benchmark results:
6/21/2005 1:12:55 PM|| Number of CPUs: 1
6/21/2005 1:12:55 PM|| 2393 double precision MIPS (Whetstone) per CPU
6/21/2005 1:12:55 PM|| 4483 integer MIPS (Dhrystone) per CPU
6/21/2005 1:12:55 PM||Finished CPU benchmarks
6/21/2005 1:12:55 PM|SETI@home|Resuming computation for result 19se03aa.5812.15249.411082.37_1 using setiathome version 4.09
6/21/2005 1:12:55 PM||Resuming computation and network activity
6/21/2005 1:12:55 PM||request_reschedule_cpus: Resuming activities
6/21/2005 1:12:55 PM|SETI@home|Deferring communication with project for 21 seconds
6/21/2005 1:12:55 PM||May run out of work in 10.00 days; requesting more
6/21/2005 1:12:55 PM||Using earliest-deadline-first scheduling because computer is overcommitted.
6/21/2005 1:13:18 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:13:18 PM|SETI@home|Requesting 604877 seconds of work, returning 48 results
6/21/2005 1:13:28 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:13:28 PM|SETI@home|No schedulers responded
6/21/2005 1:13:29 PM|SETI@home|Deferring communication with project for 5 minutes and 0 seconds
6/21/2005 1:13:52 PM||request_reschedule_cpus: project op
6/21/2005 1:13:52 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:13:52 PM|SETI@home|Requesting 604756 seconds of work, returning 48 results
6/21/2005 1:14:01 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:14:01 PM|SETI@home|No schedulers responded
6/21/2005 1:14:02 PM|SETI@home|Deferring communication with project for 8 minutes and 54 seconds
6/21/2005 1:15:31 PM||request_reschedule_cpus: project op
6/21/2005 1:15:31 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:15:31 PM|SETI@home|Requesting 604445 seconds of work, returning 48 results
6/21/2005 1:15:40 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:15:40 PM|SETI@home|No schedulers responded
6/21/2005 1:15:41 PM|SETI@home|Deferring communication with project for 21 minutes and 59 seconds
6/21/2005 1:15:47 PM||request_reschedule_cpus: project op
6/21/2005 1:15:47 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:15:47 PM|SETI@home|Requesting 604399 seconds of work, returning 48 results
6/21/2005 1:15:56 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:15:56 PM|SETI@home|No schedulers responded
6/21/2005 1:15:57 PM|SETI@home|Deferring communication with project for 2 minutes and 16 seconds
6/21/2005 1:16:04 PM|SETI@home|Started upload of 11ja05aa.6290.21522.779818.119_3_0
6/21/2005 1:16:10 PM|SETI@home|Finished upload of 11ja05aa.6290.21522.779818.119_3_0
6/21/2005 1:16:10 PM|SETI@home|Throughput 25998 bytes/sec
6/21/2005 1:16:20 PM||request_reschedule_cpus: project op
6/21/2005 1:16:20 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:16:20 PM|SETI@home|Requesting 604309 seconds of work, returning 49 results
6/21/2005 1:16:29 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:16:29 PM|SETI@home|No schedulers responded
6/21/2005 1:16:30 PM|SETI@home|Deferring communication with project for 2 hours, 42 minutes, and 50 seconds
6/21/2005 1:16:37 PM||request_reschedule_cpus: project op
6/21/2005 1:16:38 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:16:38 PM|SETI@home|Requesting 604261 seconds of work, returning 49 results
6/21/2005 1:16:46 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:16:46 PM|SETI@home|No schedulers responded
6/21/2005 1:16:47 PM|SETI@home|Deferring communication with project for 58 seconds
6/21/2005 1:17:47 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:17:47 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:17:55 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:17:55 PM|SETI@home|No schedulers responded
6/21/2005 1:17:57 PM|SETI@home|Deferring communication with project for 58 seconds
6/21/2005 1:18:56 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:18:56 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:19:05 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:19:05 PM|SETI@home|No schedulers responded
6/21/2005 1:19:06 PM|SETI@home|Deferring communication with project for 58 seconds
6/21/2005 1:20:06 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:20:06 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:20:14 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:20:14 PM|SETI@home|No schedulers responded
6/21/2005 1:20:15 PM|SETI@home|Deferring communication with project for 58 seconds
6/21/2005 1:21:15 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:21:15 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:21:24 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:21:24 PM|SETI@home|No schedulers responded
6/21/2005 1:21:25 PM|SETI@home|Deferring communication with project for 1 minutes and 24 seconds
6/21/2005 1:22:51 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:22:51 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:22:59 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:22:59 PM|SETI@home|No schedulers responded
6/21/2005 1:23:00 PM|SETI@home|Deferring communication with project for 4 minutes and 31 seconds
6/21/2005 1:27:32 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:27:32 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:27:45 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:27:45 PM|SETI@home|No schedulers responded
6/21/2005 1:27:47 PM|SETI@home|Deferring communication with project for 10 minutes and 14 seconds
6/21/2005 1:38:01 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:38:01 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:38:15 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:38:15 PM|SETI@home|No schedulers responded
6/21/2005 1:38:16 PM|SETI@home|Deferring communication with project for 18 minutes and 34 seconds
6/21/2005 1:56:50 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 1:56:50 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:57:06 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 1:57:06 PM|SETI@home|No schedulers responded
6/21/2005 1:57:07 PM|SETI@home|Deferring communication with project for 1 hours, 58 minutes, and 33 seconds
6/21/2005 2:12:56 PM||May run out of work in 10.00 days; requesting more
6/21/2005 2:57:07 PM|SETI@home|Deferring communication with project for 58 minutes and 33 seconds
6/21/2005 3:08:51 PM||request_reschedule_cpus: process exited
6/21/2005 3:08:51 PM|SETI@home|Computation for result 19se03aa.5812.15249.411082.37_1 finished
6/21/2005 3:08:51 PM|SETI@home|Starting result 11ja05aa.6290.21570.454834.255_2 using setiathome version 4.09
6/21/2005 3:08:59 PM|SETI@home|Started upload of 19se03aa.5812.15249.411082.37_1_0
6/21/2005 3:09:06 PM|SETI@home|Finished upload of 19se03aa.5812.15249.411082.37_1_0
6/21/2005 3:09:06 PM|SETI@home|Throughput 40599 bytes/sec
6/21/2005 3:12:57 PM||May run out of work in 10.00 days; requesting more
6/21/2005 3:28:05 PM||request_reschedule_cpus: project op
6/21/2005 3:28:06 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 3:28:06 PM|SETI@home|Requesting 0 seconds of work, returning 50 results
6/21/2005 3:28:22 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 3:28:22 PM|SETI@home|No schedulers responded
6/21/2005 3:28:23 PM|SETI@home|Deferring communication with project for 2 hours, 46 minutes, and 17 seconds
6/21/2005 3:28:45 PM||request_reschedule_cpus: project op
6/21/2005 3:28:54 PM||request_reschedule_cpus: project op
6/21/2005 3:28:54 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 3:28:54 PM|SETI@home|Requesting 0 seconds of work, returning 50 results
6/21/2005 3:29:08 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 3:29:08 PM|SETI@home|No schedulers responded
6/21/2005 3:29:09 PM|SETI@home|Deferring communication with project for 58 seconds
6/21/2005 3:29:17 PM||request_reschedule_cpus: project op
6/21/2005 3:30:08 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 3:30:08 PM|SETI@home|Requesting 0 seconds of work, returning 50 results
6/21/2005 3:30:21 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 3:30:21 PM|SETI@home|No schedulers responded
6/21/2005 3:30:22 PM|SETI@home|Deferring communication with project for 58 seconds
6/21/2005 3:31:22 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 3:31:22 PM|SETI@home|Requesting 0 seconds of work, returning 50 results
6/21/2005 3:31:37 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 3:31:37 PM|SETI@home|No schedulers responded
6/21/2005 3:31:38 PM|SETI@home|Deferring communication with project for 58 seconds
6/21/2005 3:32:38 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 3:32:38 PM|SETI@home|Requesting 0 seconds of work, returning 50 results
6/21/2005 3:32:53 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 3:32:53 PM|SETI@home|No schedulers responded
6/21/2005 3:32:54 PM|SETI@home|Deferring communication with project for 58 seconds
6/21/2005 3:33:54 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/21/2005 3:33:54 PM|SETI@home|Requesting 0 seconds of work, returning 50 results
6/21/2005 3:34:10 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/21/2005 3:34:10 PM|SETI@home|No schedulers responded
6/21/2005 3:34:11 PM|SETI@home|Deferring communication with project for 1 minutes and 32 seconds

---

Something similar happened to me with v4.45 with modem conection. I usually connect once a day, I had severa results to return and new work to ask. In the first scheduler request new work was requested and the results were returned, but after it failed a few times, it stopped asking for new work and only tried to return results. The same thing happened in the log that Joseph Keene posted.

Here it is asking for work:
6/21/2005 1:13:18 PM|SETI@home|Requesting 604877 seconds of work, returning 48 results
6/21/2005 1:13:52 PM|SETI@home|Requesting 604756 seconds of work, returning 48 results
6/21/2005 1:15:31 PM|SETI@home|Requesting 604445 seconds of work, returning 48 results
6/21/2005 1:15:47 PM|SETI@home|Requesting 604399 seconds of work, returning 48 results
6/21/2005 1:16:20 PM|SETI@home|Requesting 604309 seconds of work, returning 49 results
6/21/2005 1:16:38 PM|SETI@home|Requesting 604261 seconds of work, returning 49 results

Now it stops requesting new work and only tries to return the results. Why?

6/21/2005 1:17:47 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:18:56 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:20:06 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:21:15 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:22:51 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:27:32 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:38:01 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 1:56:50 PM|SETI@home|Requesting 0 seconds of work, returning 49 results
6/21/2005 3:28:06 PM|SETI@home|Requesting 0 seconds of work, returning 50 results
6/21/2005 3:28:54 PM|SETI@home|Requesting 0 seconds of work, returning 50 results
6/21/2005 1:17:47 PM|SETI@home|Requesting 0 seconds of work, returning 49 results

---