Scheduler request failed: couldn't resolve host name
Questions and Answers :
Windows :
Scheduler request failed: couldn't resolve host name
Message board moderation
| Author | Message |
|---|---|
 Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2 
|
Hulloh, I can not connect to any project for at least three days now. I alway get the following messages: 19.12.2007 17:54:00|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi 19.12.2007 17:54:00|climateprediction.net|Reason: To send trickle-up message 19.12.2007 17:54:00|climateprediction.net|(not requesting new work or reporting completed tasks) 19.12.2007 17:54:01||Project communication failed: attempting access to reference site 19.12.2007 17:54:02||Access to reference site succeeded - project servers may be temporarily down. 19.12.2007 17:54:07|climateprediction.net|Scheduler request failed: couldn't resolve host name 19.12.2007 17:54:07|climateprediction.net|Deferring scheduler requests for 52 minutes and 2 seconds 19.12.2007 17:54:12|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 19.12.2007 17:54:12|SETI@home|Reason: To report completed tasks 19.12.2007 17:54:12|SETI@home|Requesting 8640 seconds of new work, and reporting 2 completed tasks 19.12.2007 17:54:12||Project communication failed: attempting access to reference site 19.12.2007 17:54:13||Access to reference site succeeded - project servers may be temporarily down. 19.12.2007 17:54:17|SETI@home|Scheduler request failed: couldn't resolve host name 19.12.2007 17:54:17|SETI@home|Deferring scheduler requests for 1 hours, 16 minutes and 11 seconds Anyone any idea? Btw, I already restarted BOINC. 19.12.2007 17:52:52||Starting BOINC client version 5.4.11 for windows_intelx86 19.12.2007 17:52:52||libcurl/7.15.3 OpenSSL/0.9.8a zlib/1.2.3 19.12.2007 17:52:52||Data directory: C:\\Programme\\BOINC 19.12.2007 17:52:52||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 1.90GHz 19.12.2007 17:52:52||Memory: 767.53 MB physical, 1.12 GB virtual 19.12.2007 17:52:52||Disk: 20.00 GB total, 3.01 GB free 
ID: 692830 ·  |
|
Fred W Send message Joined: 13 Jun 99 Posts: 2524 Credit: 11,954,210 RAC: 0 
|
Hulloh, First thing to try is as in this post. F. 
ID: 692834 · |
|
Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2
|
Thank you, Fred, for the fast reply, but do you care to explain what it does before I do it !? (I don't like doing stuff to my PC unless I understand at least what the idea is; I'm not presumptuous to say I understand everything, but the general order...)
ID: 692839 · |
Jakob Creutzfeld  Send message Joined: 13 Oct 00 Posts: 611 Credit: 2,025,000 RAC: 0 
|
Thank you, Fred, for the fast reply, but do you care to explain what it does before I do it !? Actually it is explained in the linked post itself... :-) You can also type "ipconfig /?" to see further options... HTH Andy ID: 692840 · |
|
Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2
|
Well, did it and as in the post it did nothing. I'm still getting this: 19.12.2007 18:40:42|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi 19.12.2007 18:40:42|climateprediction.net|Reason: To send trickle-up message 19.12.2007 18:40:42|climateprediction.net|(not requesting new work or reporting completed tasks) 19.12.2007 18:40:43||Project communication failed: attempting access to reference site 19.12.2007 18:40:45||Access to reference site succeeded - project servers may be temporarily down. 19.12.2007 18:40:48|climateprediction.net|Scheduler request failed: couldn't resolve host name 19.12.2007 18:40:48|climateprediction.net|Deferring scheduler requests for 2 hours, 3 minutes and 9 seconds 19.12.2007 18:40:53|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 19.12.2007 18:40:53|SETI@home|Reason: To report completed tasks 19.12.2007 18:40:53|SETI@home|Requesting 8640 seconds of new work, and reporting 2 completed tasks 19.12.2007 18:40:54||Project communication failed: attempting access to reference site 19.12.2007 18:40:56||Access to reference site succeeded - project servers may be temporarily down. 19.12.2007 18:40:59|SETI@home|Scheduler request failed: couldn't resolve host name 19.12.2007 18:40:59|SETI@home|Deferring scheduler requests for 1 hours, 6 minutes and 38 seconds
ID: 692842 · |
|
Fred W Send message Joined: 13 Jun 99 Posts: 2524 Credit: 11,954,210 RAC: 0
|
Thank you, Fred, for the fast reply, but do you care to explain what it does before I do it !? Sorry I didn't explain myself adequately earlier. It appeared to me that your machine could see common sites such as Google, etc ("Access to reference site succeeded") but could not see Boinc sites. This can often be resolved by flushing the dns cache. My next move would be to try to "ping" the Berkley address from the Cmd prompt and post the results here but I suspect that Andy will be of use to you if this goes deeper. F.
ID: 692858 · |
|
Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2
|
My next move would be to try to "ping" the Berkley address from the Cmd prompt... Er, how do I do that? I mean what do YOU mean by "cmd prompt"? What program? Which address? I'm sorry if I seem to be too persistant, but it's troublesome that all worked fine until about three days ago. Nothing has changed on my side - or so I believe.
ID: 692862 · |
|
Jakob Creutzfeld Send message Joined: 13 Oct 00 Posts: 611 Credit: 2,025,000 RAC: 0
|
My next move would be to try to "ping" the Berkley address from the Cmd prompt... Ok... Hi Holger, to "Ping" the berkeley servers do the following: - Click "Start" -> "Ausführen...", enter "cmd" in the dialog filed and click < OK > (this opens the DOS Box). Type "ping setiathome.berkeley.edu" (without quotations) end press Enter. You should receive something like this: Ping setiathome.SSL.berkeley.edu [128.32.18.171] mit 32 Bytes Daten: You should receive: Antwort von 128.32.18.171: Bytes=32 Zeit=199ms TTL=44
Antwort von 128.32.18.171: Bytes=32 Zeit=203ms TTL=44
Antwort von 128.32.18.171: Bytes=32 Zeit=203ms TTL=44
Antwort von 128.32.18.171: Bytes=32 Zeit=203ms TTL=44
Ping-Statistik für 128.32.18.171:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust)If you receive something different, please report it here. Next step is a tracert (trace route), so in the same DOS Box type "tracert setiathome.berkeley.edu" (without quotes). You should receive (similar): 10 62 ms 46 ms 62 ms ae-2.ebr2.London1.Level3.net [4.69.132.133] 16 187 ms 187 ms 187 ms ae-21-79.car1.SanJose1.Level3.net [4.68.18.67] 17 187 ms 187 ms 187 ms CENIC.car1.SanJose1.Level3.net [4.79.44.6] 18 187 ms 187 ms 187 ms inet-ucb--svl-isp.cenic.net [137.164.24.106] 19 187 ms 187 ms 187 ms g3-19.inr-201-eva.Berkeley.EDU [128.32.0.58] 20 187 ms 187 ms 187 ms g6-1.inr-230-spr.Berkeley.EDU [128.32.255.110] 21 203 ms 203 ms 202 ms ssl-f1.SSL.Berkeley.EDU [169.229.0.218] 22 203 ms 203 ms 203 ms bane.ssl.berkeley.edu [128.32.18.171] Ablaufverfolgung beendet. If this doesn't work, report it here. Actually, I'm not an "Internet guy", so if both of these suggestions fail, I'm at the end of my Latin. I suspect that Berkeley has changed it's IP adress (or ISP) and the new paths to Berkeley are not published fast enough for all DNS servers. Further suggestions/ideas, anyone? Andy ID: 692866 · |
|
Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2
|
Well, did that. Got Antwort von 128.32.18.171: Bytes=32 Zeit=314ms TTL=45
Antwort von 128.32.18.171: Bytes=32 Zeit=313ms TTL=45
Antwort von 128.32.18.171: Bytes=32 Zeit=363ms TTL=45
Antwort von 128.32.18.171: Bytes=32 Zeit=304ms TTL=45
Ping-Statistik für 128.32.18.171:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust)Then took the next step - the tracert. I received 3 * 298 ms * vel-ncore-1.gigabiteth4-5.swip.net [212.151.137.84] 4 106 ms 104 ms 145 ms par-ncore-1.tengigabiteth1-3.swip.net [212.151.130.125] 5 235 ms 247 ms 258 ms par1-core-1.gigabiteth3-1-0.swip.net [130.244.206.93] 6 168 ms 131 ms 156 ms ash1-core-1.pos4-0-0.swip.net [130.244.218.138] 7 182 ms 223 ms 244 ms sl-st20-ash-14-1-1.sprintlink.net [144.223.246.189] 8 280 ms 275 ms 295 ms dcp-brdr-02.inet.qwest.net [63.146.26.81] 9 278 ms 337 ms 267 ms dcx-core-02.inet.qwest.net [205.171.251.37] 10 303 ms 390 ms 395 ms svl-core-02.inet.qwest.net [67.14.12.54] 11 351 ms 386 ms 400 ms svl-edge-16.inet.qwest.net [205.171.14.170] 12 330 ms 340 ms 402 ms 63.145.224.14 13 353 ms 405 ms 396 ms inet-ucb--svl-isp.cenic.net [137.164.24.106] 14 338 ms 345 ms 275 ms g3-19.inr-201-eva.Berkeley.EDU [128.32.0.58] 15 * 304 ms 303 ms g6-1.inr-230-spr.Berkeley.EDU [128.32.255.110] 16 398 ms 417 ms 426 ms ssl-f1.SSL.Berkeley.EDU [169.229.0.218] 17 284 ms 398 ms 351 ms bane.SSL.Berkeley.EDU [128.32.18.171] Ablaufverfolgung beendet. (I kept the first two steps private - unless there's a good reason to disclose them. But I guess the problem lies after that anyways.)
ID: 692898 · |
Geek@Play  Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0 
|
The scheduler (where work is downloaded and returned) is at http://setiboinc.ssl.berkeley.edu Try pinging and tracert for that address. ID: 692985 · |
|
Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2
|
On first try: Ping setiboinc.ssl.berkeley.edu [208.68.240.16] mit 32 Bytes Daten:
Antwort von 208.68.240.16: Bytes=32 Zeit=424ms TTL=53
Antwort von 208.68.240.16: Bytes=32 Zeit=359ms TTL=53
Zeitüberschreitung der Anforderung. [b]<= exceeding time limit[/b]
Antwort von 208.68.240.16: Bytes=32 Zeit=366ms TTL=53
Ping-Statistik für 208.68.240.16:
Pakete: Gesendet = 4, Empfangen = 3, Verloren = 1 (25% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 359ms, Maximum = 424ms, Mittelwert = 383msThen tried again: Ping setiboinc.ssl.berkeley.edu [208.68.240.16] mit 32 Bytes Daten:
Antwort von 208.68.240.16: Bytes=32 Zeit=225ms TTL=53
Antwort von 208.68.240.16: Bytes=32 Zeit=491ms TTL=53
Zeitüberschreitung der Anforderung.
Antwort von 208.68.240.16: Bytes=32 Zeit=417ms TTL=53
Ping-Statistik für 208.68.240.16:
Pakete: Gesendet = 4, Empfangen = 3, Verloren = 1 (25% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 225ms, Maximum = 491ms, Mittelwert = 377msYep, there seems to be a problem. Still, traced the route: Routenverfolgung zu setiboinc.ssl.berkeley.edu [208.68.240.16] über maximal 30 Abschnitte: 1 <1 ms <1 ms 1 ms [...]* 2 311 ms * * [...]* 3 338 ms 212 ms 343 ms vel-ncore-1.gigabiteth2-25.swip.net [212.151.137.92] 4 260 ms 227 ms 156 ms cbv-ncore-1.tengigabiteth13-1.swip.net [212.151.130.129] 5 328 ms 244 ms 169 ms cbv1-core-1.gigabiteth8-0.swip.net [130.244.193.13] 6 248 ms 368 ms 331 ms ams16-core-1.pos0-0-0.swip.net [130.244.205.146] 7 297 ms 300 ms 269 ms gsr12416.ams.he.net [195.69.145.150] 8 311 ms 284 ms 283 ms 72.52.92.81 9 346 ms 224 ms 213 ms 72.52.92.77 10 444 ms * 425 ms 10gigabitethernet3-1.core1.sjc2.he.net [72.52.92.25] 11 436 ms 544 ms 376 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69] 12 322 ms 452 ms * 64.71.140.42 13 340 ms 258 ms 488 ms 208.68.243.254 14 447 ms 394 ms 306 ms setiboincdata.SSL.Berkeley.EDU [208.68.240.16] Ablaufverfolgung beendet.
ID: 693018 · |
|
Gundolf Jahn Send message Joined: 19 Sep 00 Posts: 3184 Credit: 446,358 RAC: 0
|
I'm sorry if I seem to be too persistant, but it's troublesome that all worked fine until about three days ago. Nothing has changed on my side - or so I believe. Hallo Holger, ich hatte auch das Problem, dass von einem Tag auf den anderen die Verbindung mit Berkeley nicht mehr richtig funktionierte. Ich hatte zwar eine andere Fehlermeldung (HTTP error) und nur der Upload war betroffen, aber vielleicht hilft meine Lösung ja. Ich hab auch die ganze "ping"-Sache durchexerziert (Jakob, der Befehl muss übrigens lauten ping -a -f -l 1472 208.68.240.16da das -f Flag nicht bei allen Versionen Standard ist und 28 Header-Bytes vom MTU-Wert von 1500 abgezogen werden müssen), aber ohne Erfolg. Dann habe ich das HTTP-Protokoll von 1.1 auf 1.0 zurückgesetzt, et voila: alles funktioniert wieder. Du musst eine Datei namens CC_CONFIG.XML im Verzeichnis C:\\Programme\\BOINC erzeugen (wenn sie noch nicht existiert) und darin (z.B. mit Notepad) <cc_config> <options> <http_1_0>1</http_1_0> </options> </cc_config>eintragen. Genaueres zu cc_config.xml findest Du hier. Nach einem Neustart von BOINC (sicherheitshalber Reboot) ist die Option in Kraft. Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz)  SETI@home classic workunits 3,758 SETI@home classic CPU time 66,520 hours ID: 693046 · |
|
Jakob Creutzfeld Send message Joined: 13 Oct 00 Posts: 611 Credit: 2,025,000 RAC: 0
|
(Jakob, der Befehl muss übrigens lauten ... Hi Gundolf, danke für's einspringen und für die Korrektur (wie schon gesagt, bin eigentlich kein "Internet guy", und wenn's um Internetverbindungen usw. geht komm ich dann doch recht schnell mit meinem Latein an's Ende...) Gruss Andy ID: 693059 · |
|
Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2
|
Hallo, Gundolf, okay, habe CC_CONFIG.XML angelegt - hat nichts geändert (zugegeben, ich habe kein komplettes Reboot des PCs gemacht, dies ist im Augenblick nicht möglich; ich lass es aber drin). Danach ping mit allen Flags ergibt ping -a -f -l 1472 208.68.240.16
Ping setiboincdata.SSL.Berkeley.EDU [208.68.240.16] mit 1472 Bytes Daten:
Antwort von 192.168.1.1: Paket müsste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Paket müsste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Paket müsste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Paket müsste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Ping-Statistik für 208.68.240.16:
Pakete: Gesendet = 4, Empfangen = 1, Verloren = 3 (75% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0msC'est frustrant! Hab's nochmal anders versucht: ping 208.68.240.16 [b]also ohne Flags[/b]
Ping wird ausgeführt für 208.68.240.16 mit 32 Bytes Daten:
Antwort von 208.68.240.16: Bytes=32 Zeit=408ms TTL=53
Antwort von 208.68.240.16: Bytes=32 Zeit=517ms TTL=53
Antwort von 208.68.240.16: Bytes=32 Zeit=477ms TTL=53
Antwort von 208.68.240.16: Bytes=32 Zeit=459ms TTL=53
Ping-Statistik für 208.68.240.16:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 408ms, Maximum = 517ms, Mittelwert = 465msDa gibt's keine Probleme. ======================================================= Okay, for anyone not too fluent in German. Gundolf suggested to change the HTT protocol used from 1.1 to 1.0 by means of the cc_config.xml file. Also he suggested to use ping -a -f -l 1472 [ADDRESS] instead of a simple ping. In my case it blocked totally any communication.
ID: 693068 · |
|
Gundolf Jahn Send message Joined: 19 Sep 00 Posts: 3184 Credit: 446,358 RAC: 0
|
Hallo, Gundolf, Schade, aber ich hatte ja auch einen anderen Fehler, nur das Symptom "plötzliches Auftreten ohne eigene Änderungen" hatte mich auf die Idee gebracht.
Sorry for the confusion I caused. That comment was directed at another thread. By the way, it didn't block the communication, it only showed that somewhere on the path from your computer to Berkeley, the maximum transmission units (MTU) are smaller than 1500 bytes. There the data blocks have to be splitted (fragmented), which is prevented by the -f flag. The -a flag only outputs the name of the host according to the numeric address. Probably a value of 1432 for the -l flag, would result in the 'normal' ping output. That is the value for my XP-box, whereas my NT4-box accepts values up to 1472, even though both are connected through the same DSL router. And since I'm no Internet-guy either, I can't explain that behaviour, and no one else did in my previous threads Upload (only) problem with http error and Still can't upload from NT. Ich wünsche Dir viel Glück (und Unterstützung :-) bei der weiteren Fehlersuche. Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) SETI@home classic workunits 3,758 SETI@home classic CPU time 66,520 hours ID: 693091 · |
|
Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2
|
Thank you, Gundolf, it was worth a try, and though it didn't solve my problem, well, I learned something (never new about the tracert). And there was no confusion, just a probable Kernfusion, but who knows that song... By the way, your given name pronounced in English reminds funnily of an tremendously successful bockbuster trilogy of the early 2000s :) Okay, anyone else any idea on how to solve my problem?
ID: 693093 · |
|
Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2
|
Well, since there's no further help available and no change in the behaviour of my BOINC, it looks like the end of my contribution to seti@home or any other project. This is quite unfortunate since I've always been proud to be here, but alas...
ID: 693716 · |
|
Fred W Send message Joined: 13 Jun 99 Posts: 2524 Credit: 11,954,210 RAC: 0
|
Well, since there's no further help available and no change in the behaviour of my BOINC, it looks like the end of my contribution to seti@home or any other project. Holger, Since this is a problem that affects all Boinc projects, have you tried raising it in the Boinc forum. You may find someone there who can help. F.
ID: 693718 · |
|
Holger Burghardt Send message Joined: 23 Jan 04 Posts: 10 Credit: 2,520,456 RAC: 2
|
Well, no, but HAPPILY I can announce that somewhere in this thread may have been a solution, however, today my system crashed, and since rebooting it worked again. 22.12.2007 15:17:50|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi 22.12.2007 15:17:50|climateprediction.net|Reason: To send trickle-up message 22.12.2007 15:17:50|climateprediction.net|(not requesting new work or reporting completed tasks) 22.12.2007 15:18:07||Project communication failed: attempting access to reference site 22.12.2007 15:18:11||Access to reference site failed - check network connection or proxy configuration. 22.12.2007 15:18:15|climateprediction.net|Scheduler request failed: couldn't resolve host name 22.12.2007 15:18:15|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi 22.12.2007 15:18:15|climateprediction.net|Reason: To send trickle-up message 22.12.2007 15:18:15|climateprediction.net|(not requesting new work or reporting completed tasks) 22.12.2007 15:18:22|climateprediction.net|Scheduler request failed: couldn't resolve host name 22.12.2007 15:18:22|climateprediction.net|Deferring scheduler requests for 1 hours, 21 minutes and 44 seconds 22.12.2007 15:18:27|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 22.12.2007 15:18:27|SETI@home|Reason: To report completed tasks 22.12.2007 15:18:27|SETI@home|Requesting 8640 seconds of new work, and reporting 2 completed tasks 22.12.2007 15:18:32|SETI@home|Scheduler request failed: couldn't resolve host name 22.12.2007 15:18:32|SETI@home|Deferring scheduler requests for 2 hours, 0 minutes and 34 seconds 22.12.2007 16:40:11|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi 22.12.2007 16:40:11|climateprediction.net|Reason: To send trickle-up message 22.12.2007 16:40:11|climateprediction.net|(not requesting new work or reporting completed tasks) 22.12.2007 16:40:16|climateprediction.net|Scheduler request succeeded 22.12.2007 17:08:36|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 22.12.2007 17:08:36|SETI@home|Reason: To report completed tasks 22.12.2007 17:08:36|SETI@home|Requesting 8640 seconds of new work, and reporting 2 completed tasks 22.12.2007 17:08:42|SETI@home|Scheduler request succeeded So, whatever the reason, eventually it passed...
ID: 693751 · |
|
Fred W Send message Joined: 13 Jun 99 Posts: 2524 Credit: 11,954,210 RAC: 0
|
Well, no, but HAPPILY I can announce that somewhere in this thread may have been a solution, however, today my system crashed, and since rebooting it worked again. Excellent news. Glad that you are not going to have to leave us. F.
ID: 693843 · |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.