Message boards :
climateprediction.net Science :
SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain
Message board moderation
Author | Message |
---|---|
Send message Joined: 28 Feb 05 Posts: 4 Credit: 129,354 RAC: 0 |
Getting errors from scheduler. Already have a work unit (500hrs away from complete), so unsure why it is contacting scheduler anyway... but is there a server problem?? (Time is US Central) climateprediction.net - 2005-03-11 10:49:44 - Sending request to scheduler: http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi climateprediction.net - 2005-03-11 10:49:47 - Scheduler RPC to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded climateprediction.net - 2005-03-11 10:49:47 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain climateprediction.net - 2005-03-11 10:49:47 - Can't parse scheduler reply climateprediction.net - 2005-03-11 10:49:47 - Deferring communication with project for 1 hours, 35 minutes, and 19 seconds |
Send message Joined: 26 Aug 04 Posts: 67 Credit: 10,110,630 RAC: 7,465 |
Hi there I kept getting these errors also this afternoon from approx 14:00 to 17:00 (UK time, so in the same real time range as yourself) during repeated attempts at normal trickles. It looks like a temporary server problem therefore so no doubt it will be resolved in time. Pete |
Send message Joined: 2 Sep 04 Posts: 1 Credit: 111,619 RAC: 0 |
> I kept getting these errors also this afternoon from approx 14:00 to 17:00 (UK > time, so in the same real time range as yourself) during repeated attempts at > normal trickles. It looks like a temporary server problem therefore so no > doubt it will be resolved in time. > > Pete I've been getting these identical errors ever since the 4.19 upgrade. Still happening as of Monday morning, 14/03/2005. It may indeed be a server error, but the coincidence between the timing of the upgrade and the incidence of this error is suspicious. Dennis |
Send message Joined: 30 Aug 04 Posts: 7 Credit: 1,554,414 RAC: 0 |
I'm getting this error too. I'm also attached the the Einstein@home project and can update with them with no problem. Gotta be a server on CPDN's end with the problem. |
Send message Joined: 30 Aug 04 Posts: 7 Credit: 1,554,414 RAC: 0 |
> I've been getting these identical errors ever since the 4.19 upgrade. Still > happening as of Monday morning, 14/03/2005. > > It may indeed be a server error, but the coincidence between the timing of the > upgrade and the incidence of this error is suspicious. > > Dennis > I've had ver4.19 for weeks now and this is the first time I've had this problem occur. |
Send message Joined: 20 Sep 04 Posts: 1 Credit: 111,623 RAC: 0 |
I have just started getting this error this afternoon i am on 4.13 and have been for months first time i have seen this error. I am currently 96.7% through a run so i hope it trickles soon, I am not attached to any other project Steve What do you know 5 mins after writing this it connected after not working all afternoon seems ok now |
Send message Joined: 3 Sep 04 Posts: 268 Credit: 256,045 RAC: 0 |
From LHC@home (sorry, I don't know the user who posted this message) <i>A definitive answer (at least, it's as definitive as anything is with BOINC) When the server is under heavy load it can exceed the number of connections allowed to the database resulting in the message 'Server can't open database'. There is a problem with the server software that returns a malformed XML message in this circumstance that the client can't understand. The result is a 'Cannot parse scheduler reply' message displayed by the client. What it means is 'Server is a bit busy right now'. Reinstalling the BOINC software won't help directly since this is a server problem. Waiting a few minutes (while you re-install BOINC, perhaps) will allow some connections to clear, and things might then work. The connection limit is configurable by the admins. Raising it can improve connection performance, but raising it too far can result in much reduced throuhput. Currently it's set at 100 connections unless Markku has changed it recently. It had been set at 400 connections prior, but this resulted in only 25% of the throughput! IMO the whole BOINC database set up needs a good overhaul since these performance problems pop up at what seems to be quite low levels. As always, I suspect that the database performance may only be improved by the expenditure of money - something which most BOINC projects are short of. I think that's it. Anyone got anything to add? </i> Arnaud |
Send message Joined: 5 Aug 04 Posts: 390 Credit: 2,475,242 RAC: 0 |
Yeah, it may be so. BOINC forum starts lagging as well which indicates to some press on forum database as well. <i>phpBB forum for CPDN, all are </i><a href="http://www.climateprediction.net/board">invited</a> |
Send message Joined: 8 Aug 04 Posts: 7 Credit: 374,800 RAC: 0 |
hi there I have been having problems with the upload schedulers, error message is "No schedulers responded" this is now been going on for over a week, I now have 2 models waiting to get new data, yet when the model finished it uploaded no problem, but no work downloaded. does anyone else have this problem? |
Send message Joined: 8 Aug 04 Posts: 7 Credit: 374,800 RAC: 0 |
hi there its okay sorted the problem which I found in another thread. |
©2024 cpdn.org