SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain

Questions and Answers : Windows : SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain

Author	Message
Paul Webster Send message Joined: 29 May 99 Posts: 3 Credit: 1,581,314 RAC: 124	Message 3408 - Posted: 2 Jul 2004, 9:24:58 UTC
	On BOINC uploading some results I see an unexpected error message: 2004-07-02 00:00:44 [SETI@home] SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain 2004-07-02 00:00:44 [SETI@home] Can't parse scheduler reply
	ID: 3408 ·

John McLeod VII Volunteer developer Volunteer tester Send message Joined: 15 Jul 99 Posts: 22343 Credit: 439,020 RAC: 429	Message 3481 - Posted: 2 Jul 2004, 15:02:29 UTC
	Several others have seen this, it is apparently a server side issue.
	ID: 3481 ·

Shai Malul Send message Joined: 29 May 99 Posts: 4 Credit: 447,934 RAC: 302	Message 3542 - Posted: 2 Jul 2004, 16:45:55 UTC - in response to Message 3481.
	> Several others have seen this, it is apparently a server side issue. Same problem here: SETI@home - 2004-07-02 19:39:46 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi SETI@home - 2004-07-02 19:40:00 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded SETI@home - 2004-07-02 19:40:00 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain SETI@home - 2004-07-02 19:40:00 - Can't parse scheduler reply SETI@home - 2004-07-02 19:40:00 - Deferring communication with project for 5 minutes and 14 seconds I also haven't managed to get any work units in days.
	ID: 3542 ·

Benjamin Hunt (KG4ESJ) Volunteer tester Send message Joined: 13 Aug 99 Posts: 14 Credit: 113,602 RAC: 0	Message 3547 - Posted: 2 Jul 2004, 16:53:33 UTC - in response to Message 3481.
	Having participated in Beta since the beginning, I'm less concerned with not getting any work than I am about not being able to send my completed work units that have been sitting on my computer for the past several days. Beyond that, my stats seem to have reset to zero, though this might be due to the maintenance done to the servers coupled with the apparent communication failure between the clients and SAH. While I am sure this will eventually be sorted out, I must agree with the masses on this one: more news would be spiffy. It seems to me that Alpha and Beta were kept up to date much better than this.
	ID: 3547 ·

Questions and Answers : Windows : SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain