[error] Can't parse workunit in scheduler reply: unexpected XML tag or syntax
14 May 2014 6:58:23 UTC
Topic 197581
(moderation:
I'm getting this error on one of my machines participating in the GWopencl-ati-Beta testing. Here is a log snippet
Wed 14 May 2014 03:52:22 PM EST Einstein@Home Sending scheduler request: To fetch work. Wed 14 May 2014 03:52:22 PM EST Einstein@Home Requesting new tasks for ATI Wed 14 May 2014 03:52:26 PM EST Einstein@Home [error] Can't parse workunit in scheduler reply: unexpected XML tag or syntax Wed 14 May 2014 03:52:26 PM EST Einstein@Home [error] No close tag in scheduler reply
A google search reveals quite a few hits at various projects including this rather old one at Rosetta. The final response from a Dev is interesting
Quote:
Okay, I think I may have fixed the issue. I had to recompile our scheduling server programs with a larger xml_doc max buffer. A few batches were submitted that had so many input files that the scheduler reply from our server was truncated for these tasks. Please ignore the "ghost" work units. They will eventually get cleared.
I've noticed that .... blocks in the state file of my machine do seem to be alarmingly large with huge numbers of references to data files. So, perhaps, we too are exceeding this 'xml_doc max buffer' so that the sched_reply is being truncated, causing the client to have problems with it?
Edit: I should add that there are no GWopencl-ati-Beta tasks on this host at the moment. On the website, the host is shown as having this task. It would appear that each time the host contacts the scheduler, the scheduler tries to resend this very task as a 'lost' task. The client doesn't receive the task correctly, instead producing the error messages listed above.
I haven't reset the project (yet) because there are also SSE2-Beta CPU tasks from the same frequency set, a couple of which are in progress. Each time a work request fails, BOINC goes into a longish backoff so it's certainly not asking (and getting the error) all that often.
Cheers,
Gary.