Message boards :
Number crunching :
New error/bug? Or has anyone seen this
Message board moderation
Author | Message |
---|---|
CyberGoyle Send message Joined: 2 Jun 99 Posts: 160 Credit: 3,622,756 RAC: 26 |
2004-10-14 23:36:24 [---] Starting BOINC client version 4.13 for windows_intelx86 2004-10-14 23:36:24 [SETI@home] Project prefs: using your defaults 2004-10-14 23:36:24 [SETI@home] Host ID is 60623 2004-10-14 23:36:24 [---] General prefs: from SETI@home (last modified 2004-09-29 08:06:35) 2004-10-14 23:36:24 [---] General prefs: using your defaults 2004-10-14 23:36:24 [SETI@home] Resuming computation for result 04mr04aa.22434.9314.773582.216_1 using setiathome version 4.05 2004-10-14 23:36:26 [SETI@home] Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 2004-10-14 23:36:43 [---] Can't resolve hostname setiboinc.ssl.berkeley.edu (host name not found) 2004-10-14 23:36:43 [SETI@home] scheduler init_op_project to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed, error -113 2004-10-14 23:36:43 [SETI@home] Deferring communication with project for 1 minutes and 0 seconds 2004-10-14 23:38:00 [---] Can't resolve hostname setiboinc.ssl.berkeley.edu (host name not found) 2004-10-14 23:38:00 [SETI@home] scheduler init_op_project to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed, error -113 2004-10-14 23:38:00 [SETI@home] Deferring communication with project for 1 minutes and 50 seconds 4.09 worked fine on this PC until upgrade - Windows 2000 SP4. <a><img src="http://boinc.mundayweb.com/stats.php?userID=525"> <a><img src="http://www.wombatradio.com/stats/rtb/sig.php"> |
[ue] s-o lybeck Send message Joined: 25 Nov 99 Posts: 16 Credit: 4,024,140 RAC: 0 |
Connect to Internet. error -113 = no connection SOL |
Geoff Send message Joined: 9 Oct 04 Posts: 4 Credit: 20,111 RAC: 0 |
Yes I got that all last night, resolved itself this AM (my time) thinks SETI had some problem, also notice similar thing with CPDN right now, thinks they are all server probs |
CyberGoyle Send message Joined: 2 Jun 99 Posts: 160 Credit: 3,622,756 RAC: 26 |
Only problem is that I was using a remote control over the internet to update that PC to 4.13 (meaning I had live internet), and my 35 other PC's were all communicating with Seti just fine.....weird. <a><img src="http://boinc.mundayweb.com/stats.php?userID=525"> <a><img src="http://www.wombatradio.com/stats/rtb/sig.php"> |
Mac-Nic Send message Joined: 29 Jun 00 Posts: 165 Credit: 551,008 RAC: 0 |
=>Error 113: No route to host >Internal webserver is shutdown just to disappoint you. >If it were up&running, you'd be redirected to it. "The FUTURE is only a PARTICLE away from the PRESENT and the PAST." |
Papa Zito Send message Joined: 7 Feb 03 Posts: 257 Credit: 624,881 RAC: 0 |
> 2004-10-14 23:36:24 [---] Starting BOINC client version 4.13 for > windows_intelx86 > 2004-10-14 23:36:24 [SETI@home] Project prefs: using your defaults > 2004-10-14 23:36:24 [SETI@home] Host ID is 60623 > 2004-10-14 23:36:24 [---] General prefs: from SETI@home (last modified > 2004-09-29 08:06:35) > 2004-10-14 23:36:24 [---] General prefs: using your defaults > 2004-10-14 23:36:24 [SETI@home] Resuming computation for result > 04mr04aa.22434.9314.773582.216_1 using setiathome version 4.05 > 2004-10-14 23:36:26 [SETI@home] Sending request to scheduler: > http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi > 2004-10-14 23:36:43 [---] Can't resolve hostname setiboinc.ssl.berkeley.edu > (host name not found) > 2004-10-14 23:36:43 [SETI@home] scheduler init_op_project to > http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed, error -113 > 2004-10-14 23:36:43 [SETI@home] Deferring communication with project for 1 > minutes and 0 seconds > 2004-10-14 23:38:00 [---] Can't resolve hostname setiboinc.ssl.berkeley.edu > (host name not found) > 2004-10-14 23:38:00 [SETI@home] scheduler init_op_project to > http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed, error -113 > 2004-10-14 23:38:00 [SETI@home] Deferring communication with project for 1 > minutes and 50 seconds > > 4.09 worked fine on this PC until upgrade - Windows 2000 SP4. > > I had that happen once. Turned out that my firewall (on that particular PC) wasn't allowing the connection through. It happened after a BOINC upgrade... it thought the new version was a different program. |
©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.