I'm on a dial-up line. For more than a day now, whenever I am connected to the internet and my client attempts to connect, that attempt fails for lack of a response from the server end.

Typical console messages:

Scheculer RPC to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed.
No scheduler responded

I tried manually 'ping' to the above site and to climateprediction.net. No response there, either. I don't know if you have 'ping' turned off, or if the path is down.

mikus
.

that's odd, could it be a firewall issue, i.e. you're computer is blocking CPDN/BOINC from contacting the server. If you cut and paste the scheduler URL into a web browser do you get anything (should get some messages with "Incomplete request received." in the middle): http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi

I really have NO IDEA as to what was going on. Typing what you said into a browser got the response you said - but the CPDN client would NOT complete any transfers - it always claimed "no server responded" and waited some more.

I let things run until my computer went idle (because phase 3 had finished). Then I restarted with -update_prefs, which allowed it to upload the five results files. I manually changed client_state.xml to "short-circuit" its wait, but it STILL claimed it had no server response, and did not send the accumulated trickles.

I said "enough of this", and detached from the CPDN project. When I re-attached, the client made no mention of any leftover trickles.

Applications that "require no user input" are fine if they work, but when things go wrong they are a bitch. '-update_prefs' is NOT enough, when it does not FORCE a "stuck" trickle to become "unstuck".