1) Message boards : Number crunching : i need help (Message 939)
Posted 17 Dec 2015 by DigiK-oz
Post:
It is :( Setting "no new work" and hitting update does work fine and reports completed tasks, however. Only trying to get new work gives the internal server error.
2) Message boards : Number crunching : BHspin v0.05 (Message 869)
Posted 5 Dec 2015 by DigiK-oz
Post:
Just a tad more info : The replies from the server appear to be encrypted, even though the protocol used is HTTP, not HTTPS

Good luck in finding the issue!
3) Message boards : Number crunching : BHspin v0.05 (Message 860)
Posted 4 Dec 2015 by DigiK-oz
Post:
Well, still the same issue, but the 8K limit seems to not always be true, I now get some 12K replies from the server, but still truncated XML :(
4) Message boards : Number crunching : BHspin v0.05 (Message 857)
Posted 4 Dec 2015 by DigiK-oz
Post:
Same issue here :(

12/4/2015 7:40:55 AM | Universe@Home | Requesting new tasks for CPU
12/4/2015 7:40:58 AM | Universe@Home | [error] Can't parse workunit in scheduler reply: unexpected XML tag or syntax
12/4/2015 7:40:58 AM | Universe@Home | [error] No close tag in scheduler reply

Looking at the network traffic with fiddler, I see that the request that is sent to the server is complete, valid XML (about 80 Kbytes) However, the reply that arrives from U@H server is XML, but clearly truncated at 8.168 bytes.

Is it possible that this only happens when a lot of tasks are reported/requested in one scheduler request? I have this on one machine which does not have network connectivity the whole day, so it is usually reporting and requesting a full day worth of WU's. Maybe there is a maximum size for the server reply set somewhere?

If I set "no new tasks", my finished tasks are immediately reported correctly (since the server reply is very small, probably?). After that, I can request work again, but it fails again...and again exactly 8.168 bytes of truncated XML arrives from the U@H server.

Resetting the project does not help. But after removing it and adding it again, I got 1 WU (and the XML reply from U@H server was 7.897 bytes).

It seems that there is a limit in the reply size somewhere. If you have a network connection all day, you will normally only get one new WU per reply, and the reply will be under 8.168 bytes. All will work fine. But once you do request more than one WU, you might run into this...
This *may* fix it (remporarily?)

- Set "no new work" and wait for finished WU's to be reported
- Remove and re-add the project

Can someone please look into this as I am running out of WU's on a regular basis due to this.







Copyright © 2024 Copernicus Astronomical Centre of the Polish Academy of Sciences
Project server and website managed by Krzysztof 'krzyszp' Piszczek