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

Author	Message
SwissNic Send message Joined: 27 Nov 99 Posts: 78 Credit: 633,713 RAC: 0	Message 3266 - Posted: 1 Jul 2004, 22:36:31 UTC Last modified: 1 Jul 2004, 22:38:43 UTC Anyone else getting this? Happening on all my BOINC/SETI machines... Cheers, Nic. > Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi > Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi Succeeded > SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain > Can't parse scheduler reply ------------------------------------------------ Once you have ruled out the impossible, everything else, however improbable, is possible! A.C. Doyle. ID: 3266 ·

S@NL -TheFons Volunteer tester Send message Joined: 17 Jan 01 Posts: 2 Credit: 4,043,917 RAC: 0	Message 3273 - Posted: 1 Jul 2004, 22:43:44 UTC Yup same here ID: 3273 ·

Jaaku Volunteer tester Send message Joined: 29 Oct 02 Posts: 494 Credit: 346,224 RAC: 0	Message 3274 - Posted: 1 Jul 2004, 22:46:25 UTC http://setiathome.berkeley.edu/ - 2004-07-01 23:44:55 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain same here, o how fun ID: 3274 ·

Fleeting Glimpse Send message Joined: 29 Apr 02 Posts: 13 Credit: 33,268 RAC: 0	Message 3277 - Posted: 1 Jul 2004, 22:52:20 UTC Ditto. ~~ When I was a child, I caught a Fleeting Glimpse. ID: 3277 ·

KWSN_Dagger Volunteer tester Send message Joined: 14 Feb 04 Posts: 36 Credit: 3,578 RAC: 0	Message 3281 - Posted: 1 Jul 2004, 23:00:09 UTC SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain 2004-07-01 15:53:15 [SETI@home] Can't parse scheduler reply Yep :( ID: 3281 ·

LeoSalazar Send message Joined: 22 May 99 Posts: 1 Credit: 4,483,646 RAC: 6	Message 3282 - Posted: 1 Jul 2004, 23:03:26 UTC Same with me... ID: 3282 ·

Kerwin Send message Joined: 7 Dec 99 Posts: 18 Credit: 10,635,562 RAC: 0	Message 3285 - Posted: 1 Jul 2004, 23:24:18 UTC Does anyone know what it means? ID: 3285 ·

cardinalsmurf Send message Joined: 24 Jan 01 Posts: 6 Credit: 2,053,406 RAC: 0	Message 3296 - Posted: 1 Jul 2004, 23:53:10 UTC I came to this thread looking for others having the same problem. I'm getting it too. Seems to have started this afternoon (PDT). Could it be that they have reconfigured the software on their end and haven't yet posted the new client update to the web site? The other functionality of the client seems to be working now as of this afternoon. It was able to finally upload my last WU and grab an update to my account. it just can't get new work. ID: 3296 ·

KWSN - MajorKong Volunteer tester Send message Joined: 5 Jan 00 Posts: 2892 Credit: 1,499,890 RAC: 0	Message 3302 - Posted: 2 Jul 2004, 0:21:03 UTC - in response to Message 3296. > I came to this thread looking for others having the same problem. I'm getting > it too. Seems to have started this afternoon (PDT). > > Could it be that they have reconfigured the software on their end and haven't > yet posted the new client update to the web site? I think this is the case. Last update to the source code I saw was scheduler related. ------------ KWSN-MajorKong KWSN Forum Admin (retired) http://www.kwsnforum.com S@H participant since May 28, 1999 (other acct.) BOINC Beta Tester since Nov 19, 2003 ID: 3302 ·

Chip Long Send message Joined: 2 Aug 00 Posts: 445 Credit: 503,693 RAC: 0	Message 3305 - Posted: 2 Jul 2004, 0:41:29 UTC - in response to Message 3302. Last modified: 2 Jul 2004, 0:42:46 UTC > I think this is the case. Last update to the source code I saw was scheduler > related. Seems like they figured it out... SETI@home - 2004-07-01 19:13:30 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi SETI@home - 2004-07-01 19:13:34 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded SETI@home - 2004-07-01 19:13:34 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain SETI@home - 2004-07-01 19:13:34 - Can't parse scheduler reply SETI@home - 2004-07-01 19:13:34 - Deferring communication with project for 1 hours, 10 minutes, and 25 seconds --- - 2004-07-01 19:45:49 - Fewer active results than CPUs; requesting more work SETI@home - 2004-07-01 19:45:49 - Requesting 54067 seconds of work SETI@home - 2004-07-01 19:45:49 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi SETI@home - 2004-07-01 19:46:23 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded SETI@home - 2004-07-01 19:46:23 - Started download of 01ja04aa.14693.28097.173580.17 SETI@home - 2004-07-01 19:46:30 - Finished download of 01ja04aa.14693.28097.173580.17 SETI@home - 2004-07-01 19:46:30 - Approximate throughput 50957.660058 bytes/sec SETI@home - 2004-07-01 19:46:30 - Starting computation for result 01ja04aa.14693.28097.173580.17_2 using setiathome version 3.08 SETI@home - 2004-07-01 20:32:48 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi SETI@home - 2004-07-01 20:33:02 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded Regards <FONT FACE='ARIAL'>chip w3range.net</FONT> <BR> ID: 3305 ·

atotos Volunteer tester Send message Joined: 23 Feb 02 Posts: 51 Credit: 11,930 RAC: 0	Message 3409 - Posted: 2 Jul 2004, 9:30:44 UTC - in response to Message 3266. I had this same problem several times last night CET time. It seems now it OK, but there is no work available :-( SETI@home - 2004-07-02 11:23:49 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi SETI@home - 2004-07-02 11:24:02 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded SETI@home - 2004-07-02 11:24:02 - Message from server: No work available SETI@home - 2004-07-02 11:24:02 - No work from project ID: 3409 ·

From Zero Land Send message Joined: 17 Apr 02 Posts: 3 Credit: 33,899 RAC: 0	Message 3530 - Posted: 2 Jul 2004, 16:24:09 UTC SETI@home - 2004-07-02 10:23:32 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain SETI@home - 2004-07-02 10:23:32 - Can't parse scheduler reply It's a problem that's on and off as most things are but I am enjoying the process. ----- ID: 3530 ·

Benjamin Hunt (KG4ESJ) Volunteer tester Send message Joined: 13 Aug 99 Posts: 14 Credit: 113,602 RAC: 0	Message 3555 - Posted: 2 Jul 2004, 17:03:50 UTC - in response to Message 3530. SETI@home - 2004-07-02 12:01:28 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi SETI@home - 2004-07-02 12:01:30 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed SETI@home - 2004-07-02 12:01:30 - No schedulers responded SETI@home - 2004-07-02 12:01:30 - Deferring communication with project for 16 minutes and 15 seconds Unfortunately, it is now back at this stage. I wish the stats would at least update... ID: 3555 ·

Dash Send message Joined: 1 Jan 00 Posts: 22 Credit: 3,425 RAC: 0	Message 3557 - Posted: 2 Jul 2004, 17:06:13 UTC I agree... But its going to be some time before that happens. There are still alot of bugs to be worked out. www.jumppoint.org ID: 3557 ·

slimm Volunteer tester Send message Joined: 7 May 99 Posts: 6 Credit: 3,742,855 RAC: 0	Message 3566 - Posted: 2 Jul 2004, 17:30:22 UTC It's happening again SETI@home - 2004-07-02 13:29:20 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi SETI@home - 2004-07-02 13:29:23 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded SETI@home - 2004-07-02 13:29:23 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain SETI@home - 2004-07-02 13:29:23 - Can't parse scheduler reply SETI@home - 2004-07-02 13:29:23 - Deferring communication with project for 1 minutes and 50 seconds ID: 3566 ·

Kirsten Volunteer tester Send message Joined: 7 Jul 00 Posts: 190 Credit: 566,047 RAC: 0	Message 3572 - Posted: 2 Jul 2004, 17:35:29 UTC - in response to Message 3566. > It's happening again > > SETI@home - 2004-07-02 13:29:20 - Sending request to scheduler: > http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi > SETI@home - 2004-07-02 13:29:23 - Scheduler RPC to > http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded > SETI@home - 2004-07-02 13:29:23 - SCHEDULER_REPLY::parse(): bad first tag > Content-type: text/plain > SETI@home - 2004-07-02 13:29:23 - Can't parse scheduler reply > SETI@home - 2004-07-02 13:29:23 - Deferring communication with project for 1 > minutes and 50 seconds > And here SETI@home - 2004-07-02 19:37:01 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain You might subtract two hours to get GMT. ID: 3572 ·

slimm Volunteer tester Send message Joined: 7 May 99 Posts: 6 Credit: 3,742,855 RAC: 0	Message 3581 - Posted: 2 Jul 2004, 17:45:07 UTC And to think that they have been down some of this time to debug the "new scheduler". ID: 3581 ·

Guido_A_Waldenmeier_ Send message Joined: 3 Apr 99 Posts: 482 Credit: 4,774 RAC: 0	Message 3583 - Posted: 2 Jul 2004, 17:48:59 UTC one picture say more then 1000 words (have you see the new boinc rules) [/url] [/url] another OS like NASA SYSTEM 5 or bsd will follow ID: 3583 ·

[ue] juuso Send message Joined: 9 Dec 02 Posts: 11 Credit: 300,677 RAC: 0	Message 3584 - Posted: 2 Jul 2004, 17:49:36 UTC Same here...still no work... Only wierd errors... Have to be patience...? ID: 3584 ·

©2025 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.