Questions and Answers :
Sixtrack :
Can't parse scheduler reply
Message board moderation
Author | Message |
---|---|
Send message Joined: 28 Sep 04 Posts: 8 Credit: 11,592 RAC: 0 |
When connecting lhc@home the Boinc client logs a error message. The reason is that the server add a http header to the reply and the client doesn't drop it. The same problem occurs on the alpha project. Boinc messages: LHC@home - 2005-05-07 07:14:41 - Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi LHC@home - 2005-05-07 07:14:44 - Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded LHC@home - 2005-05-07 07:14:44 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain LHC@home - 2005-05-07 07:14:44 - Can't parse scheduler reply LHC@home - 2005-05-07 07:14:44 - Deferring communication with project for 1 minutes and 0 seconds scheduler reply: Content-type: text/plain <scheduler_reply> <message priority="low">Server can't open database</message> <request_delay>3600</request_delay> <project_is_down/> </scheduler_reply> <scheduler_reply> <project_name>LHC@home</project_name> <host_total_credit>0.000000</host_total_credit> <host_expavg_credit>0.000000</host_expavg_credit> <host_venue></host_venue> <host_create_time>0</host_create_time> </scheduler_reply> BamBam |
Send message Joined: 2 Sep 04 Posts: 378 Credit: 10,765 RAC: 0 |
This occurs when the Database is overloaded, and instead of generating a nice reply that your boinc client can read, it sends out a SQL server error message. The Boinc Client doesn't get a nicely formatted message from the server, and reports that it gets an error message. I'm not the LHC Alex. Just a number cruncher like everyone else here. |
©2025 CERN