LHC@home

Hi,

I keep getting this:

LHC@home - 2004-11-04 11:54:12 - Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi
LHC@home - 2004-11-04 11:54:17 - Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
LHC@home - 2004-11-04 11:54:17 - SCHEDULER_REPLY::parse(): bad first tag
LHC@home - 2004-11-04 11:54:17 - Can't parse scheduler reply
LHC@home - 2004-11-04 11:54:17 - Deferring communication with project for 1 minutes and 40 seconds

Any suggestions/comments?

Thanks

Oswald

copy/paste didn't work properly...

This is the actual problem.

LHC@home - 2004-11-04 11:53:12 - SCHEDULER_REPLY::parse(): bad first tag

Thanks

Oswald aka Venox7

let's try again

html gets screwed when posting.. added " "

LHC@home - 2004-11-04 11:53:12 - SCHEDULER_REPLY::parse(): bad first tag ""

removed html brackets, maybe this will work.

SCHEDULER_REPLY::parse(): bad first tag DOCTYPE HTML PUBLIC "-//W3C//DTD HTML FINAL//EN

Problem solved.

Deleted sched_reply_lhcathome.cern.ch.xml and sched_request_lhcathome.cern.ch.xml so that BOINC is forced to regenerate the file.

That did the trick!!

Venox7

> Problem solved.
>
> Deleted sched_reply_lhcathome.cern.ch.xml and
> sched_request_lhcathome.cern.ch.xml so that BOINC is forced to regenerate the
> file.
>
> That did the trick!!
>
> Venox7
>
Thank for this trick!!! This helps also with other projects problem. Great !


Seid gegr�sst Programme und happy crunching

> Problem solved.
>
> Deleted sched_reply_lhcathome.cern.ch.xml and
> sched_request_lhcathome.cern.ch.xml so that BOINC is forced to regenerate the
> file.
>
> That did the trick!!
>
> Venox7
>
Thank for this trick!!! This helps also with other projects problem. Great !


Seid gegr�sst Programme und happy crunching

> Problem solved.
>
> Deleted sched_reply_lhcathome.cern.ch.xml and
> sched_request_lhcathome.cern.ch.xml so that BOINC is forced to regenerate the
> file.
>
> That did the trick!!
>
> Venox7
>
Thank for this trick!!! This helps also with other projects problem. Great !


Seid gegr�sst Programme und happy crunching

The problem is the response. You can see it in the file 'sched_reply_lhcathome.cern.ch.xml'. The lhc server sends an error message, saying: "Server can't open database". They made a mistake, when they implemented the response. The first two lines shouldn't be there:
"ContentType: text/plain" and the empty line. I expect, that they set the content type to the http header of the response.

BamBam

The problem is the response. You can see it in the file 'sched_reply_lhcathome.cern.ch.xml'. The lhc server sends an error message, saying: "Server can't open database". They made a mistake, when they implemented the response. The first two lines shouldn't be there:
"ContentType: text/plain" and the empty line. I expect, that they set the content type to the http header of the response.

BamBam

p.s.: On the first try to post the answer i got:

Warning: Too many connections in /shift/lxfsrk429/data01/boinc/projects/lhcathome/html/inc/db.inc on line 40
Unable to connect to database - please try again later Error: 1040Too many connections

> The problem is the response. You can see it in the file
> 'sched_reply_lhcathome.cern.ch.xml'. The lhc server sends an error message,
> saying: "Server can't open database". They made a mistake, when they
> implemented the response. The first two lines shouldn't be there:
> "ContentType: text/plain" and the empty line. I expect, that they set the
> content type to the http header of the response.
>

BamBam,

Thanks for the reply, however, the problem was not the typical text/plain error but was the following (had problems pasting it as it was in html format)

SCHEDULER_REPLY::parse(): bad first tag DOCTYPE HTML PUBLIC "-//W3C//DTD HTML FINAL//EN

by deleting the xml files I forced boinc to regenerate it, and that seems to have corrected the problem. I'm running two hosts at one site, and only the one had this problem while the other connected successfully.

Regards,

Venox7

Oswald,

to help the developers of the project you should look into the file and post it's content, so that the CERN staff could analyse it and correct the real error.
Deleting the file has not other effect than that the file is deleted.
The BOINC client stores the result of the server in that file. With the next response it will be overwritten. So, not the lack of the file heals the connection, retrying to connect heals it!

So be kind to the developers and post the erroneous content of the file.

Regards,

Sven

> Deleting the file has not other effect than that the file is deleted.
> The BOINC client stores the result of the server in that file. With the next
> response it will be overwritten. So, not the lack of the file heals the
> connection, retrying to connect heals it!
>

Deleted both request and reply xml.Deleting the request xml probably helped (?)

Developer's email?