Hien:
Do you have an example of a scheduler request that causes this problem?
(look for a sched_request_xxx.xml file on one of your clients
when it's reporting a result).
-- David

On 02-May-2013 12:09 PM, Nx Hien wrote:
Hello everyone,

Our project recently upgraded our 2010 BOINC server to commit
2091b257876cfdc4f12fedc0f2a1116f1c85cd8f and now when processing requests
from clients, our server often says:

SCHEDULER_REQUEST::parse(): unexpected: ...a part of our result's stderr...
Incomplete request received from IP ......


And the message "no end tag" is displayed on the client's UI.

I am wondering if  this error is related to the size of our task's stderr
because our task does produce a remarkably large stderr but this error didn't
happen to us when we used our 2010 BOINC server source code.

Any help would be very much appreciated.

Best regards, _______________________________________________ boinc_dev
mailing list [email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe,
visit the above URL and (near bottom of page) enter your email address.

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to