Hi, All -

A lot of people have been having trouble connecting to our scheduler lately. Well, I think I fixed the problem, or at least one problem. If you were having trouble connecting before, can you try again and post positive/negative results to this thread?

Thanks,

- 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

Hi Matt, can you post a similar thread in one of the Q&A forums? A lot of people who try to attach, but cannot, don't have credit yet. So they can't post here.

---

no Probs here from Germany

SETI@home - 2005-09-20 23:30:10 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-09-20 23:30:16 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

all is working perfectly



Greetings from Germany NRW
Ulli

I didn't have a problem connecting, but did get an odd message:

20/09/2005 2:38:00 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/09/2005 2:38:00 PM|SETI@home|Requesting 0 seconds of work, returning 0 results
20/09/2005 2:38:01 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
20/09/2005 2:38:02 PM|SETI@home|Deferring communication with project for 10 minutes and 4 seconds

I was refreshing my preferences at the time, and was set to no new work, hence the request for 0 seconds of work, but even after a successful connection I get the deferring communication message afterwards.

I don't know if this is a symptom of a bigger problem, so... now you know about it! There was no harm done on my end that I could see.

[EDIT] I should add, also, that BOINC did not connect again after the 10:04 was up.[/EDIT]

---

20/09/2005 2:38:00 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
20/09/2005 2:38:00 PM|SETI@home|Requesting 0 seconds of work, returning 0 results
20/09/2005 2:38:01 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
20/09/2005 2:38:02 PM|SETI@home|Deferring communication with project for 10 minutes and 4 seconds

I am getting the exact same thing on a manual update to the project.

---

20/09/2005 2:38:02 PM|SETI@home|Deferring communication with project for 10 minutes and 4 seconds

I am getting the exact same thing on a manual update to the project.

It's spreading... sigh. Einstein started doing this a few days ago, people are complaining, they're trying to find a way to tell the client to hold off connecting WITHOUT sending this annoying message. And now SETI _adds_ it?

getting the same message in Pennsylvania - using S@H 4.18 and BOINC 4.19. But I am connecting okay.

SETI@home - 2005-09-20 15:51:03 - Deferring communication with project for 10 minutes and 6 seconds

(EDIT) I just updated manually okay, and did not get the "deferring" msg.

Seeing the same thing, but still getting work.

9/20/2005 5:27:35 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/20/2005 5:27:35 PM|SETI@home|Reason: To fetch work
9/20/2005 5:27:35 PM|SETI@home|Requesting 1 seconds of work, returning 0 results
9/20/2005 5:27:36 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
9/20/2005 5:27:37 PM|SETI@home|Deferring communication with project for 10 minutes and 4 seconds
9/20/2005 5:27:37 PM|SETI@home|Started download of 26ja04aa.9681.31665.504824.197
9/20/2005 5:27:41 PM|SETI@home|Finished download of 26ja04aa.9681.31665.504824.197
9/20/2005 5:27:41 PM|SETI@home|Throughput 90140 bytes/sec

Its a miracle. Not a single server 500 error. Not one. I had got to the point of having to leave the dial up on overnight just to get an update thru. It took 20 or 30 tries to get an update. At the weekend's it was almost impossible to get an update thru.
Today I have got all machines updated.

Just in case we have forgotten the problem:-
9/20/05 1:43:00 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
9/20/05 1:43:00 PM|SETI@home|No schedulers responded

I dont give a toss about the 10 min wait that's appeared.

Give that man a nobel prize.

Nairb

---

20/09/2005 2:38:02 PM|SETI@home|Deferring communication with project for 10 minutes and 4 seconds

I am getting the exact same thing on a manual update to the project.

It's spreading... sigh. Einstein started doing this a few days ago, people are complaining, they're trying to find a way to tell the client to hold off connecting WITHOUT sending this annoying message. And now SETI _adds_ it?

I've gotten it from both LHC, E@H, and Seti in the last week or so. LHC likes to back off about 27 hours instead of 10 minutes, then chirp about it every hour after that. Good thing I log some face time with my BOINC Client...

I'm running BOINC 4.72 on XP SP2 and 4.45 on 2000 SP4.

(j)
James

LHC likes to back off about 27 hours instead of 10 minutes

Sounds like they are using Mars times. Is LHC trying to build their large hadron collider on our neighbour planet? ;)

(I must edit and say: Someone has had fun minusing all our posts. Maybe someone who thought this wasn't the correct forum for these posts. ;))

---

Hi Matt,
I've controlled now my 3 hosts and all have a long queue of wu in transfer with many message of deferring download, but that work units was not listed in Work tab. Restarting BOINC, the queue of WU disappeared and BOINC continue with the work in cache, but try to DONWLOAD new WU and the download queue has been reformed, with deferring and this error:

21/09/2005 3.23.34|SETI@home|Unrecoverable error for result 09no03aa.23825.18768.59646.132_0 (WU download error: couldn't get input files:<file_xfer_error> <file_name>09no03aa.23825.18768.59646.132</file_name> <error_code>-200</error_code> <error_message></error_message></file_xfer_error>)

I don't understand why the Wu in transfer do not compare in the Work tab.....what's happening at the scheduler and download server? :(

---

GHz
BOINC.Italy

2 hosts are getting this about 1 to 1hr 1/2, nothing else just this one line.....

SETI@home 9/20/2005 4:56:28 PM Deferring communication with project for 9 minutes and 31 seconds

SETI@home 9/20/2005 6:03:37 PM Deferring communication with project for 10 minutes and 5 seconds

---

And the beat goes on
Sonny and Cher

BOINC Wiki

Hi Matt,
I've controlled now my 3 hosts and all have a long queue of wu in transfer with many message of deferring download, but that work units was not listed in Work tab. Restarting BOINC, the queue of WU disappeared and BOINC continue with the work in cache, but try to DONWLOAD new WU and the download queue has been reformed, with deferring and this error:

21/09/2005 3.23.34|SETI@home|Unrecoverable error for result 09no03aa.23825.18768.59646.132_0 (WU download error: couldn't get input files:<file_xfer_error> <file_name>09no03aa.23825.18768.59646.132</file_name> <error_code>-200</error_code> <error_message></error_message></file_xfer_error>)

I don't understand why the Wu in transfer do not compare in the Work tab.....what's happening at the scheduler and download server? :(

OK, no allarm, problem solved! It was my router! All OK now! Fiuuu :P

---

GHz
BOINC.Italy

Hi, All -

A lot of people have been having trouble connecting to our scheduler lately. Well, I think I fixed the problem, or at least one problem. If you were having trouble connecting before, can you try again and post positive/negative results to this thread?

Thanks,

- Matt

I'vcew beeb having lots of trouble over the lastg couple of months. I just tried several times in a row after learning of your fix and connected successfully every time. I don't believe that has happened sincce I have been using the BOINC version.

- Jim

---

I didn't have a problem connecting, but did get an odd message: ....

Same here, contacts the scheduler OK, and then defers communication for 10 minutes or so.

Edit- just did a manaul update after all my results had been returned & new work downloaded, no deferral this time.

---

Grant
Darwin NT

Works a treat!

"Same here, contacts the scheduler OK, and then defers communication for 10 minutes or so." This is new behaviour.

Live long and crunch.

---

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

Worked nicely using a proxy (apparently a local router problem as an alternate router works without proxy) until some time within the last 12-24 hours. Now it doesn't work. So it would seem you've perhaps fixed one bug, but at the same time introduced another... wouldn't be the first time in the history of programming.. :o)

---

Just a "ditto" to what others have posted... Running BOINC 4.45, WinXP Home, DSL connection. Not causing problems at the moment (still work in the queue), but I'm seeing the same behavior. The deferral is always 10 minutes, 4 seconds.


9/21/2005 6:20:42 AM|SETI@home|Finished upload of 09no03aa.23825.7121.292318.226_1_0
9/21/2005 6:20:42 AM|SETI@home|Throughput 233040 bytes/sec
9/21/2005 6:20:43 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
9/21/2005 6:20:43 AM|SETI@home|Requesting 0 seconds of work, returning 1 results
9/21/2005 6:20:45 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
9/21/2005 6:20:46 AM|SETI@home|Deferring communication with project for 10 minutes and 4 seconds

---

If you think education is expensive, try ignorance.

To be a bit more specific - when disabling the proxy server I can upload results, but when running 'update' manually the connection fails, with and without the use of proxy...

---