Message boards :
Number crunching :
Unable to attach a machine
Message board moderation
Author | Message |
---|---|
Send message Joined: 27 Aug 07 Posts: 46 Credit: 8,529,766 RAC: 0 |
My Linux box got the message that http://milkyway.cs.rpi.edu is no longer the right URL, and that I should detach and re-attach to the correct URL. So I did. I tried various possibilities: http://milkyway.cs.rpi.edu http://milkyway.cs.rpi.edu/ http://milkyway.cs.rpi.edu/milkyway http://milkyway.cs.rpi.edu/milkyway/ Each of these prompts for my login and password, but then attaching fails. It says something like "The web page at http://milkyway.cs.rpi.edu contains no BOINC information.It may not be the URL of a BOINC project.Please check the URL and try again." If you look at http://milkyway.cs.rpi.edu/get_project_config.php, you see that it contains a warning message. Maybe that's related? BOINC.BE: For Belgians who love the smell of glowing red cpu's in the morning Tutta55's Lair |
Send message Joined: 27 Aug 07 Posts: 647 Credit: 27,592,547 RAC: 0 |
I am attached to my Win 5.10.20 client but if I try to get some of these rare work units the following message occurs: 03.10.2007 20:57:11|Milkyway@home|Deferring communication for 1 days 0 hr 0 min 0 sec Hmmm.... ;-) Lovely greetings, Cori |
Send message Joined: 29 Aug 07 Posts: 21 Credit: 1,050,702 RAC: 0 |
I am attached to my Win 5.10.20 client but if I try to get some of these rare work units the following message occurs: I get the same message! The scheduler does not want to give us work! ;) Regards, Bob P. |
Send message Joined: 30 Aug 07 Posts: 125 Credit: 207,206 RAC: 0 |
This problem should now be fixed. Perhaps not for all... 04-Oct-07 0:45:07|Milkyway@home|Fetching scheduler list 04-Oct-07 0:45:12|Milkyway@home|Deferring communication for 1 days 0 hr 0 min 0 sec 04-Oct-07 0:45:12|Milkyway@home|Reason: 7 consecutive failures fetching scheduler list Jord. The BOINC FAQ Service. |
Send message Joined: 30 Aug 07 Posts: 125 Credit: 207,206 RAC: 0 |
OK, but I should be able to download the scheduler list without needing to get work. It's not asking for work, it's trying to fetch the master URL file. Once I got that, perhaps maybe then that my BOINC will try to ask for work. ;-) Jord. The BOINC FAQ Service. |
Send message Joined: 28 Aug 07 Posts: 49 Credit: 556,559 RAC: 0 |
ditto to Ageless' comments 10/3/2007 6:53:54 PM|Milkyway@home|Fetching scheduler list 10/3/2007 6:53:59 PM|Milkyway@home|Deferring communication for 1 days 0 hr 0 min 0 sec 10/3/2007 6:53:59 PM|Milkyway@home|Reason: 5 consecutive failures fetching scheduler list |
Send message Joined: 30 Aug 07 Posts: 125 Credit: 207,206 RAC: 0 |
In case you don't know what I am trying to do, I am not even asking for work. So, starting with a clean slate. Detached, reattached. And these are the messages I get. 04-Oct-07 0:54:55|Milkyway@home|Detaching from project 04-Oct-07 0:55:22||Fetching configuration file from http://milkyway.cs.rpi.edu/get_project_config.php 04-Oct-07 0:55:45|Milkyway@home|Deferring communication for 1 min 0 sec 04-Oct-07 0:55:45|Milkyway@home|Reason: Couldn't parse scheduler list 04-Oct-07 0:56:50|Milkyway@home|Deferring communication for 1 min 0 sec 04-Oct-07 0:56:50|Milkyway@home|Reason: Couldn't parse scheduler list 04-Oct-07 0:57:55|Milkyway@home|Deferring communication for 1 days 0 hr 0 min 0 sec 04-Oct-07 0:57:55|Milkyway@home|Reason: 3 consecutive failures fetching scheduler list BOINC isn't asking for work. It can't ask for work if it doesn't know where the schedulers live. I can't get BOINC to download Milkyway's scheduler list. Easy. :-) This is Windows 2000 SP4 and I am currently using World Community Grid's BOINC 5.10.22, as a service. Jord. The BOINC FAQ Service. |
Send message Joined: 9 Sep 07 Posts: 22 Credit: 320,035 RAC: 0 |
I'm in the same boat as Jord. I tried with both of my hosts. First one is Fedora 7/BOINC 5.10.21/Installed as a daemon. Second one is XP Pro SP2/BOINC 5.10.21/Single User install. Log from Linux Host: 2007-10-04 08:14:58 [---] Fetching configuration file from http://milkyway.cs.rpi.edu/get_project_config.php 2007-10-04 08:15:16 [Milkyway@home] Deferring communication for 1 min 0 sec 2007-10-04 08:15:16 [Milkyway@home] Reason: Couldn't parse scheduler list 2007-10-04 08:16:23 [Milkyway@home] Deferring communication for 1 min 0 sec 2007-10-04 08:16:23 [Milkyway@home] Reason: Couldn't parse scheduler list 2007-10-04 08:17:29 [Milkyway@home] Deferring communication for 1 days 0 hr 0 min 0 sec 2007-10-04 08:17:29 [Milkyway@home] Reason: 3 consecutive failures fetching scheduler list Kathryn :o) The BOINC FAQ Service The Unofficial BOINC Wiki The Trac System More BOINC information than you can shake a stick of RAM at. |
Send message Joined: 29 Aug 07 Posts: 115 Credit: 502,527,662 RAC: 102 |
Perhaps this will provide clues to track down the problem: I have had two machines attached for several weeks now, one windows and one linux. In fact the linux machine even downloaded, crunched, and returned two results. Yesterday, I attached several more machines. However, when I go into my account page, and display computers, only the original two show. As far as the project server can see, I have only the original two attached. But when I look at the client on the new machines, they show attached. All machines, new and old, are now getting the "failure fetching scheduler list". |
Send message Joined: 30 Aug 07 Posts: 125 Credit: 207,206 RAC: 0 |
I turned on the http_debug flag in cc_config.xml 04-Oct-07 2:05:27||[http_debug] HTTP_OP::init_get(): http://milkyway.cs.rpi.edu/ 04-Oct-07 2:05:27|Milkyway@home|Fetching scheduler list 04-Oct-07 2:05:28||[http_debug] [ID#2] info: About to connect() to milkyway.cs.rpi.edu port 80 (#0) 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Trying 128.213.28.20... 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Connected to milkyway.cs.rpi.edu (128.213.28.20) port 80 (#0) 04-Oct-07 2:05:28||[http_debug] [ID#2] Sent header to server: GET / HTTP/1.1 User-Agent: BOINC client (windows_intelx86 5.10.22) Host: milkyway.cs.rpi.edu Accept: */* Accept-Encoding: deflate, gzip Content-Type: application/x-www-form-urlencoded 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: HTTP/1.1 301 Moved Permanently 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: Date: Thu, 04 Oct 2007 00:05:10 GMT 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: Server: Apache 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: Location: http://milkyway.cs.rpi.edu/milkyway/ 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: Content-Length: 313 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: Content-Type: text/html; charset=iso-8859-1 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Ignoring the response-body 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Expire cleared 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Closing connection #0 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Issue another request to this URL: 'http://milkyway.cs.rpi.edu/milkyway/' 04-Oct-07 2:05:28||[http_debug] [ID#2] info: About to connect() to milkyway.cs.rpi.edu port 80 (#0) 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Trying 128.213.28.20... 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Connected to milkyway.cs.rpi.edu (128.213.28.20) port 80 (#0) 04-Oct-07 2:05:28||[http_debug] [ID#2] Sent header to server: GET /milkyway/ HTTP/1.1 User-Agent: BOINC client (windows_intelx86 5.10.22) Host: milkyway.cs.rpi.edu Accept: */* Accept-Encoding: deflate, gzip Referer: http://milkyway.cs.rpi.edu/ Content-Type: application/x-www-form-urlencoded 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: HTTP/1.1 200 OK 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: Date: Thu, 04 Oct 2007 00:05:10 GMT 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: Server: Apache 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: Transfer-Encoding: chunked 04-Oct-07 2:05:28||[http_debug] [ID#2] Received header from server: Content-Type: text/html; charset=ISO-8859-1 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Expire cleared 04-Oct-07 2:05:28||[http_debug] [ID#2] info: Closing connection #0 04-Oct-07 2:05:32|Milkyway@home|Deferring communication for 1 days 0 hr 0 min 0 sec 04-Oct-07 2:05:32|Milkyway@home|Reason: 7 consecutive failures fetching scheduler list (that preview option would be nice around here. ;-)) Jord. The BOINC FAQ Service. |
Send message Joined: 30 Aug 07 Posts: 125 Credit: 207,206 RAC: 0 |
I don't see your ID number anywhere in the logs either... have you tried detaching and reattaching? Yes, I tried detaching/reattaching prior to this post. Now I checked my computers and saw that up till 4pm this afternoon, I did have hostID 629 attached. What happened to it is anyone's guess. I haven't seen it be attached at any time. Jord. The BOINC FAQ Service. |
Send message Joined: 30 Aug 07 Posts: 125 Credit: 207,206 RAC: 0 |
I sent you an email with the log of how I reattached to BOINC alpha. It shows some differences to my log in post 62. Jord. The BOINC FAQ Service. |
©2024 Astroinformatics Group