So the day before yesterday I finished a run (with BOINC 4.19 on Linux). It\'s trickling fine (host 60701), but it\'s not uploading:

2005-06-09 17:08:08 [climateprediction.net] Temporarily failed upload of 2kui_200141547_1_1.zip
2005-06-09 17:08:08 [climateprediction.net] Backing off 1 minutes and 0 seconds on transfer of file 2kui_200141547_1_1.zip
2005-06-09 17:08:08 [climateprediction.net] Started upload of 2kui_200141547_1_3.zip
2005-06-09 17:08:23 [climateprediction.net] Temporarily failed upload of 2kui_200141547_1_2.zip
2005-06-09 17:08:23 [climateprediction.net] Backing off 1 minutes and 0 seconds on transfer of file 2kui_200141547_1_2.zip

and it\'s still waiting:

2005-06-11 17:59:59 [climateprediction.net] Temporarily failed upload of 2kui_200141547_1_1.zip
2005-06-11 17:59:59 [climateprediction.net] Backing off 3 hours, 54 minutes, and 7 seconds on transfer of file 2kui_200141547_1_1.zip

Yet scheduler RPCs are succeeding fine:
2005-06-11 07:04:49 [climateprediction.net] Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
2005-06-11 07:05:51 [climateprediction.net] Scheduler RPC to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded

Is this my end, or the remote end? If it\'s the remote end, that\'s OK: all I need to do is wait... but I fear it isn\'t, as i haven\'t seen anyone else mention this problem.

Is your model trying to upload to Oxford,
cpdn-upload1.comlab.ox.ac.uk/cpdn_cgi/file_upload_handler

or Bern?
phkup21.unibe.ch/boinc/file_upload_handler

You can see this by looking in client_state.xml in the BOINC folder. Look for a mention of the zip files, and one of these will be a few lines earlier.
I think Bern was having some problems a few days ago.

However, BOINC is patient. It will continue to attempt an upload until it succeeds.

Trickles go to Oxford on a different server.

> Is your model trying to upload to Oxford,
> cpdn-upload1.comlab.ox.ac.uk/cpdn_cgi/file_upload_handler

http://cpdn-upload1.comlab.ox.ac.uk/cpdn_cgi/file_upload_handler, I'm afraid.

I still think it must be my end, but what could it be?

I'm not a Linux person, but the usual answers seem to be to check the firewall / proxy server settings.
Otherwise, what has changed since the previous model? Hardware, software, ISP, etc.

Les

> I'm not a Linux person, but the usual answers seem to be to check the firewall
> / proxy server settings.
> Otherwise, what has changed since the previous model? Hardware, software, ISP,
> etc.

Proxy server: none needed. Firewall, ISP, hardware: no change. OS: a minor kernel upgrade (2.6.10 -> 2.6.11.10), but that's all.

I'll do a packet capture shortly and see what's going on at that level.

> I'll do a packet capture shortly and see what's going on at that level.

Got it. client_state.xml has preserved the name of an old HTTP proxy (renamed and moved some time ago), and boinc is using it in preference to the value of $HTTP_PROXY (which is in any case unset, as I don't want boinc to use a proxy anymore).

... and now it's trying to upload to Bern and only one of my nameservers can see it:

hades 32 ~% dig @192.168.14.14 phkup21.unibe.ch

; > DiG 9.3.1rc1 > @192.168.14.14 phkup21.unibe.ch
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER> DiG 9.3.1rc1 > @192.168.14.16 phkup21.unibe.ch
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER

Hey, good news. Glad you're getting somewhere. Linux and Mac users usually end up with problems and no answers.
You're way out of my area now. But my next computer will probably have to run Linux, with MS going the way it is. Used Unix ten years ago on a mainframe, and struggled with the difference, so I'll not looking foward to it.

Les

> Hey, good news. Glad you're getting somewhere. Linux and Mac users usually end
> up with problems and no answers.

:)

Anyway, uploads are working OK now (I've diked that broken nameserver out until I figure out what's wrong with it; you get used to weird bugs like this when running diverse platforms).

Arguably the HTTP proxy in use should not be part of the client state: but that's a BOINC thing, not anything CPDN can do anything about.