>>Copied from BOINC problem pages<<

Running Boing 5.28. Seti & Einstein. Dial Up to ISP. When Boinc tries to connect to the "network" the program returns:
[color=red]12/30/2005 10:41:33 AM||Couldn't resolve hostname [setiboinc.ssl.berkeley.edu]
12/30/2005 10:41:37 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -113
12/30/2005 10:41:37 AM|SETI@home|No schedulers responded [color=black]
Then the dial-up is activated (10:41:56), and the connection made (10:42:08), and promptly disconnected. (10:42:18) I'm forced to connect manually, then open B Manager and update. Any Suggestions?

I have the same problem under 5.2.13 ... with the following twist -

BOINC mamager is not always dialing out, so keeps beating its head on the wall of no connection ...

03/01/2006 09:52:56|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
03/01/2006 09:52:56|SETI@home|Reason: To fetch work
03/01/2006 09:52:56|SETI@home|Requesting 15738 seconds of new work
03/01/2006 09:52:56||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
03/01/2006 09:53:01|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
03/01/2006 09:53:01|SETI@home|No schedulers responded
03/01/2006 09:53:16|SETI@home|Started upload of 18fe05ab.2322.30514.167318.1.205_3_0
03/01/2006 09:53:16||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
03/01/2006 09:53:17|SETI@home|Temporarily failed upload of 18fe05ab.2322.30514.167318.1.205_3_0: system I/O
03/01/2006 09:53:17|SETI@home|Backing off 5 minutes and 33 seconds on upload of file 18fe05ab.2322.30514.167318.1.205_3_0

Options - Connections setting is "Automatically detect network connection settings"
-and-
Commands setting is "Network activity based on preferences" (which are 24/7)

Please help - it's driving me and B.M. crazy with frustation!

Second quote was me - and we are still frustarted.

---

Chas - Orme's Tun, Mercia, Albion.

Well, if you are on dialup, you better should use the setting "Use my Dial-up ..." instead of the automatic detection. It is told that the detection does not work quite well if mutiple network devices are installed.

Besides that: does the firewall REALLY allow connects from boinc.exe via port 80 to any internet host address?

Well, if you are on dialup, you better should use the setting "Use my Dial-up ..." instead of the automatic detection. It is told that the detection does not work quite well if mutiple network devices are installed.

Had it on "Use my Dial-up..." for a while with similar success - that's why I changed to "Auto..." - so that's not the reason/answer.

Besides that: does the firewall REALLY allow connects from boinc.exe via port 80 to any internet host address?

Unless ZoneAlarm is lying (always possible), all BOINC programs have access - so, no joy there, either.

Sorry for being so negative but if it ain't the answer, it ain't the answer

---

Chas - Orme's Tun, Mercia, Albion.

Besides that: does the firewall REALLY allow connects from boinc.exe via port 80 to any internet host address?

Unless ZoneAlarm is lying (always possible), all BOINC programs have access - so, no joy there, either.

It's well possible Zone Alarm is lying. But have you made absolutely sure that the XP firewall isn't interfering either?

Even if you have disabled the XP firewall, it may still want to block things. So make sure that Boinc is also allowed through the XP firewall.

---

Ageless,

Thanks for your thoughts.

I have (always) disabled the XP Firewall - just don't trust Microsoft.

Because of the shut-downs at Berkley, followed by the one on CPDN, I have not been able to do any real testing - doing manual control dial-up and start BOINC access a couple of times a day! Otherwise, my messages would be a sea of red (and give me a bigger headache ;-) ).

I'll come back with more, later in the week.

---

Chas - Orme's Tun, Mercia, Albion.

Hi, All,

Basically - NO PROGRESS!

Run ...and... Network activity based on preferences - but the actual activity looks like this:

BOINC Messages

15/01/2006 01:13:50|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
15/01/2006 02:37:51||request_reschedule_cpus: process exited
15/01/2006 02:37:51|LHC@home|Computation for result woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2 finished
15/01/2006 02:37:51|SETI@home|Restarting result 05oc03ab.24335.8001.492326.1.24_3 using setiathome version 418
15/01/2006 02:37:53|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:37:55||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:37:55|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:37:55|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:38:55|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:38:55||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:38:56|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:38:56|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:39:56|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:39:56||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:39:57|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:39:57|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:40:57|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:40:57||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:40:58|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:40:58|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:41:58|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:41:58||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:41:59|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:41:59|LHC@home|Backing off 2 minutes and 20 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:44:20|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:44:20||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:44:21|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:44:21|LHC@home|Backing off 2 minutes and 18 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:46:40|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:46:40||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 02:46:41|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 02:46:41|LHC@home|Backing off 17 minutes and 53 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 02:52:13||request_reschedule_cpus: process exited
15/01/2006 02:52:13|SETI@home|Computation for result 05oc03ab.24335.8001.492326.1.24_3 finished
15/01/2006 02:52:14|SETI@home|Starting result 05se04aa.9555.23298.17324.1.1_2 using setiathome version 418
15/01/2006 02:52:16|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:52:16||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:52:17|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:52:17|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:53:17|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:53:17||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:53:18|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:53:18|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:54:18|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:54:18||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:54:19|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:54:19|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:55:19|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:55:19||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:55:20|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:55:20|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:56:20|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:56:20||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:56:21|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:56:21|SETI@home|Backing off 2 minutes and 8 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:58:30|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 02:58:30||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 02:58:31|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 02:58:31|SETI@home|Backing off 5 minutes and 5 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:03:37|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:03:37||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 03:03:38|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 03:03:38|SETI@home|Backing off 7 minutes and 26 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:04:36|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 03:04:36||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 03:04:37|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 03:04:37|LHC@home|Backing off 27 minutes and 42 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 03:11:05|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:11:05||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 03:11:06|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 03:11:06|SETI@home|Backing off 12 minutes and 0 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:23:07|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:23:07||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 03:23:08|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 03:23:08|SETI@home|Backing off 36 minutes and 52 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 03:32:20|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 03:32:20||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 03:32:21|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 03:32:21|LHC@home|Backing off 1 hours, 38 minutes, and 56 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 04:00:01|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 04:00:01||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 04:00:02|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 04:00:02|SETI@home|Backing off 19 minutes and 25 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 04:19:28|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 04:19:28||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 04:19:29|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 04:19:29|SETI@home|Backing off 53 minutes and 36 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 04:52:14|climateprediction.net|Restarting result sulphur_g69o_000754620_0 using sulphur_cycle version 422
15/01/2006 04:52:14|SETI@home|Pausing result 05se04aa.9555.23298.17324.1.1_2 (removed from memory)
15/01/2006 04:52:15||request_reschedule_cpus: process exited
15/01/2006 04:52:20|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:52:20|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:52:20|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:52:20||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:52:25|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:52:25|climateprediction.net|No schedulers responded
15/01/2006 04:53:25|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:53:25|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:53:25|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:53:26||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:53:30|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:53:30|climateprediction.net|No schedulers responded
15/01/2006 04:54:31|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:54:31|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:54:31|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:54:31||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:54:36|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:54:36|climateprediction.net|No schedulers responded
15/01/2006 04:55:36|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:55:36|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:55:36|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:55:37||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:55:41|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:55:41|climateprediction.net|No schedulers responded
15/01/2006 04:56:41|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:56:41|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:56:41|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:56:42||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:56:46|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:56:46|climateprediction.net|No schedulers responded
15/01/2006 04:58:36|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 04:58:36|climateprediction.net|Reason: To send trickle-up message
15/01/2006 04:58:36|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 04:58:37||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 04:58:41|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 04:58:41|climateprediction.net|No schedulers responded
15/01/2006 05:02:06|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 05:02:06|climateprediction.net|Reason: To send trickle-up message
15/01/2006 05:02:06|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 05:02:07||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 05:02:11|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 05:02:11|climateprediction.net|No schedulers responded
15/01/2006 05:10:27|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 05:10:27|climateprediction.net|Reason: To send trickle-up message
15/01/2006 05:10:27|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 05:10:27||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 05:10:32|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 05:10:32|climateprediction.net|No schedulers responded
15/01/2006 05:11:18|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 05:11:19||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 05:11:19|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 05:11:19|LHC@home|Backing off 3 hours, 49 minutes, and 51 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 05:13:06|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 05:13:07||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 05:13:07|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 05:13:07|SETI@home|Backing off 2 hours, 13 minutes, and 11 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 05:40:47|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 05:40:47|climateprediction.net|Reason: To send trickle-up message
15/01/2006 05:40:47|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 05:40:48||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 05:40:52|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 05:40:52|climateprediction.net|No schedulers responded
15/01/2006 06:52:15|climateprediction.net|Pausing result sulphur_g69o_000754620_0 (removed from memory)
15/01/2006 06:52:18|LHC@home|Starting result woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4 using sixtrack version 467
15/01/2006 06:52:22||request_reschedule_cpus: process exited
15/01/2006 07:01:06|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 07:01:06|climateprediction.net|Reason: To send trickle-up message
15/01/2006 07:01:06|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 07:01:07||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 07:01:11|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 07:01:11|climateprediction.net|No schedulers responded
15/01/2006 07:26:19|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 07:26:19||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 07:26:20|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 07:26:20|SETI@home|Backing off 1 hours, 50 minutes, and 21 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 08:35:55||request_reschedule_cpus: process exited
15/01/2006 08:35:55|LHC@home|Computation for result woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4 finished
15/01/2006 08:35:55|SETI@home|Restarting result 05se04aa.9555.23298.17324.1.1_2 using setiathome version 418
15/01/2006 08:35:57|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:35:58||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:35:58|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:35:58|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:36:58|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:36:59||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:36:59|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:36:59|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:37:59|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:38:00||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:38:00|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:38:00|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:39:00|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:39:01||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:39:01|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:39:01|LHC@home|Backing off 1 minutes and 0 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:40:01|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:40:02||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:40:02|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:40:02|LHC@home|Backing off 2 minutes and 12 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:42:15|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:42:16||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:42:16|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:42:16|LHC@home|Backing off 3 minutes and 41 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:45:58|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:45:59||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:45:59|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:45:59|LHC@home|Backing off 3 minutes and 30 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:49:30|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 08:49:31||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 08:49:31|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 08:49:31|LHC@home|Backing off 42 minutes and 47 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 09:01:11|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 09:01:11||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 09:01:12|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0: can't resolve hostname
15/01/2006 09:01:12|LHC@home|Backing off 2 hours, 35 minutes, and 35 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__12__64.232_59.242__8_10__6__35_1_sixvf_boinc32886_2_0
15/01/2006 09:10:15|SETI@home|Result 05se04aa.9555.23298.17324.1.1_2 exited with zero status but no 'finished' file
15/01/2006 09:10:15|SETI@home|If this happens repeatedly you may need to reset the project.
15/01/2006 09:10:15||request_reschedule_cpus: process exited
15/01/2006 09:10:15|SETI@home|Restarting result 05se04aa.9555.23298.17324.1.1_2 using setiathome version 418
15/01/2006 09:16:41|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 09:16:42||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 09:16:42|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 09:16:42|SETI@home|Backing off 36 minutes and 22 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 09:32:19|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 09:32:20||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 09:32:20|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 09:32:20|LHC@home|Backing off 26 minutes and 17 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 09:43:21|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
15/01/2006 09:43:21|climateprediction.net|Reason: To send trickle-up message
15/01/2006 09:43:21|climateprediction.net|Note: not requesting new work or reporting results
15/01/2006 09:43:21||Couldn't resolve hostname [climateapps2.oucs.ox.ac.uk]
15/01/2006 09:43:26|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed with a return value of -113
15/01/2006 09:43:26|climateprediction.net|No schedulers responded
15/01/2006 09:44:26|climateprediction.net|Fetching master file
15/01/2006 09:44:26||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 09:44:31|climateprediction.net|Master file fetch failed
15/01/2006 09:44:31|climateprediction.net|Too many backoffs - fetching master file
15/01/2006 09:45:31|climateprediction.net|Fetching master file
15/01/2006 09:45:31||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 09:45:36|climateprediction.net|Master file fetch failed
15/01/2006 09:45:36|climateprediction.net|Too many backoffs - fetching master file
15/01/2006 09:47:01|climateprediction.net|Fetching master file
15/01/2006 09:47:01||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 09:47:06|climateprediction.net|Master file fetch failed
15/01/2006 09:47:06|climateprediction.net|Too many backoffs - fetching master file
15/01/2006 09:49:26|climateprediction.net|Fetching master file
15/01/2006 09:49:26||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 09:49:31|climateprediction.net|Master file fetch failed
15/01/2006 09:49:31|climateprediction.net|Too many backoffs - fetching master file
15/01/2006 09:53:06|SETI@home|Started upload of 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 09:53:06||Couldn't resolve hostname [setiboincdata.ssl.berkeley.edu]
15/01/2006 09:53:07|SETI@home|Temporarily failed upload of 05oc03ab.24335.8001.492326.1.24_3_0: can't resolve hostname
15/01/2006 09:53:07|SETI@home|Backing off 53 minutes and 54 seconds on upload of file 05oc03ab.24335.8001.492326.1.24_3_0
15/01/2006 09:58:38|LHC@home|Started upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 09:58:38||Couldn't resolve hostname [lhcathome.cern.ch]
15/01/2006 09:58:39|LHC@home|Temporarily failed upload of woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0: can't resolve hostname
15/01/2006 09:58:39|LHC@home|Backing off 58 minutes and 28 seconds on upload of file woct1_v6s4hvnom_mqx-oct1__4__64.227_59.237__8_10__6__35_1_sixvf_boinc10242_4_0
15/01/2006 10:05:01|climateprediction.net|Fetching master file
15/01/2006 10:05:01||Couldn't resolve hostname [www.climateprediction.net]
15/01/2006 10:05:06|climateprediction.net|Master file fetch failed
15/01/2006 10:05:06|climateprediction.net|Too many backoffs - fetching master file



Corresponding Modem Log, as at 10:24 15/01/2006

01-15-2006 01:25:59.984 - 115200,8,N,1, ctsfl=1, rtsctl=2
01-15-2006 01:25:59.984 - Initializing modem.
01-15-2006 01:26:00.000 - Send: AT<cr>
01-15-2006 01:26:00.000 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.000 - Interpreted response: OK
01-15-2006 01:26:00.000 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
01-15-2006 01:26:00.156 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.156 - Interpreted response: OK
01-15-2006 01:26:00.171 - Send: ATS7=120L1M0+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
01-15-2006 01:26:00.187 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.187 - Interpreted response: OK
01-15-2006 01:26:00.187 - Waiting for a call.
01-15-2006 01:26:00.203 - Send: at+vcid=1<cr>
01-15-2006 01:26:00.218 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.218 - Interpreted response: OK
01-15-2006 01:26:00.234 - Send: ATS0=0<cr>
01-15-2006 01:26:00.250 - Recv: <cr><lf>OK<cr><lf>
01-15-2006 01:26:00.250 - Interpreted response: OK
01-15-2006 01:26:00.250 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
01-15-2006 01:26:00.250 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
01-15-2006 01:26:00.250 - TSP Completing Async Operation(0x000100c6) Status 0x00000000
01-15-2006 01:26:00.250 - TSP(0000): Dropping Call
01-15-2006 01:26:00.250 - TSP Completing Async Operation(0x000100d7) Status 0x00000000
01-15-2006 01:26:00.250 - TSP(0000): Closing Call
01-15-2006 01:26:00.250 - Session Statistics:
01-15-2006 01:26:00.250 - Reads : 30 bytes
01-15-2006 01:26:00.250 - Writes: 99 bytes

When I manually connected and hit the "Retry communications" option, everything cleared.

Secondary problem:
On the odd occassion BOINC does dial-out, comms are initiated before connection is made; errors ensue; as soon as connection completes, BOINC disconnects!!

Not a lot of help.

---

Chas - Orme's Tun, Mercia, Albion.

When I manually connected and hit the "Retry communications" option, everything cleared.

Hmm, do you have other applications running that dial-up, transfer data and disconnect? Does these applications work well?

As I already stated, you'd better use the "Use my Dial-up .." with your selected modem in BOINC Manager options.

Another idea: Is BOINC being started on startup before the RAS adapters for modems are initialized?

Secondary problem:
On the odd occassion BOINC does dial-out, comms are initiated before connection is made; errors ensue; as soon as connection completes, BOINC disconnects!!

Sounds to me that the RAS adapter went nuts? ;)

You could try this: Set the "Use my Dial-up .." as described above, then shut down BOINC completely (no boinc.exe running in task manager anymore), then go online with the modem, then offline. Now we should have a clean state for BOINC: no modem active, no BOINC active. Now start BOINC. Select a project and press "Update". What BOINC is doing now?