This error has appeared in the log:

0008_000024993 - PH 1 TS 032503 - 18/10/1812 03:30 - H:M:S=0042:09:09 AVG= 4.67 DLT= 2.40
2004-08-08 00:19:10 [climateprediction.net] Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
2004-08-08 00:19:10 [climateprediction.net] Scheduler RPC to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
2004-08-08 00:19:10 [climateprediction.net] SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain
2004-08-08 00:19:10 [climateprediction.net] SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain
2004-08-08 00:19:10 [climateprediction.net] Can\'t parse scheduler reply
2004-08-08 00:19:10 [climateprediction.net] Can\'t parse scheduler reply
2004-08-08 00:19:10 [climateprediction.net] Deferring communication with project for 13 minutes and 6 seconds
2004-08-08 00:19:10 [climateprediction.net] Deferring communication with project for 13 minutes and 6 seconds
0008_000024993 - PH 1 TS 032504 - 18/10/1812 04:00 - H:M:S=0042:09:26 AVG= 4.67 DLT=16.77


Kill and restart?
New boinc client required??
Related to the boincstat note for bad xml tags?
Connected with the \'failing to trickle\' thread?

Regards,
Martin

Hello Martin,

this sound like a problem created by the server or the line, not by the client. So nothing you can do with the client can help there.

When the server answers the client, the answer is to find in a file sched_reply.xml. The BOINC client read and parse this file and if something is wrong with it you get a message like you see.

You can easy have look in this file with a editor (if you know how to use one with linux :-)). Mostly it is easy to see when the XML in the file is malformed. May be a programming error with the BOINC server send a wrong tag or only strange chars are in the file (transfer problem) or the file is empty and so on.

You may report what you find in the file.

If you post lines of xml files, you should replace the ">" char and its counterpart with "}" and "{" and please be sure to remove things like email_hash, authenticator or code_sign_key for being secure.

Greetings from Bremen/Germany
Jens Seidler
Webmaster http://www.boinc.de/

> this sound like a problem created by the server or the line, not by the
> client. So nothing you can do with the client can help there.

Looks like it was server or comms problems. A few attempts later and it got through ok.

The simulation continues.

Regards,
Martin

(Yes, most linux people can use a keyboard (;-))


FYI:

2004-08-08 00:32:16 [climateprediction.net] Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
2004-08-08 00:32:16 [climateprediction.net] Scheduler RPC to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded