The project is completed, but the result isnt reported. This message is displayed over and over again.

2/20/2006 12:26:12 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
2/20/2006 12:26:12 PM|climateprediction.net|Reason: To report results
2/20/2006 12:26:12 PM|climateprediction.net|Requesting 8640 seconds of new work, and reporting 1 results
2/20/2006 12:26:21 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
2/20/2006 12:26:21 PM|climateprediction.net|Message from server: Incomplete request received.

(I am running BOINC 5.2.13 on a AMD Athlon 64 3200+ computer with XP64 as OS)

This is interesting, as your Pentium is the only one to report up to date and has 100 trickles to go. The 3200 has not connected to the server since the 10th and has only 57 trickles finished.

---

BOINC Wiki

This is interesting, as your Pentium is the only one to report up to date and has 100 trickles to go. The 3200 has not connected to the server since the 10th and has only 57 trickles finished.

Seems I\'ve had this problem for a while then. I do have 30-ish trickle_up_<something>.xml.sent messages in BOINC, presumably waiting for them to be sent. These are all 113-144 bytes large, except the first one which is sized 1,400 bytes. Maybe the latter poses a problem?

Yes, and it\'s most likely a comms problem.
What version of BOINC are you using?
What lines of messages are there in the Messages tab related to this?

Yes, and it\'s most likely a comms problem.
What version of BOINC are you using?
What lines of messages are there in the Messages tab related to this?

2/20/2006 10:50:32 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
2/20/2006 10:50:32 PM|climateprediction.net|Reason: To report results
2/20/2006 10:50:32 PM|climateprediction.net|Requesting 8640 seconds of new work, and reporting 1 results
2/20/2006 10:50:37 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
2/20/2006 10:50:37 PM|climateprediction.net|Message from server: Incomplete request received.
2/20/2006 10:50:42 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
2/20/2006 10:50:42 PM|climateprediction.net|Reason: To report results
2/20/2006 10:50:42 PM|climateprediction.net|Requesting 8640 seconds of new work, and reporting 1 results
2/20/2006 10:50:47 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
2/20/2006 10:50:47 PM|climateprediction.net|Message from server: Incomplete request received.
2/20/2006 10:50:53 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
2/20/2006 10:50:53 PM|climateprediction.net|Reason: To report results
2/20/2006 10:50:53 PM|climateprediction.net|Requesting 8640 seconds of new work, and reporting 1 results
2/20/2006 10:50:58 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
2/20/2006 10:50:58 PM|climateprediction.net|Message from server: Incomplete request received.

etc etc etc

BOINC 5.2.13

Okay. This is getting annoying.

I have a problem to which I get no answer. I have no idea whether anyone is actually working on it to get it solved. So ... whom do I contact to find out? Or even better, by who can I dump my finished data so they can salvage what they presumably need? (the trickle up messages that cannot be sent are there after all, just as the packed data of all the results).

Okay. This is getting annoying.

I have a problem to which I get no answer. I have no idea whether anyone is actually working on it to get it solved. So ... whom do I contact to find out? Or even better, by who can I dump my finished data so they can salvage what they presumably need? (the trickle up messages that cannot be sent are there after all, just as the packed data of all the results).

Never saw the message before. Have you rebooted and retried it? Any problems with proxy or firewall(s)?

BTW, the reason suppost is limited here ATM is that everyone is buried in supporting 90k, or thereabouts, sign-ons to the new bbc.cpdn launch. Sorry about that.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Unusual problem.

In your work tab of the BOINC GUI, what does the status say for the sulphur work unit?

Perhaps there is some corruption of a trickle file? You could delete the oldest trickle, then do a Project Update. You also might want to try to reinstall BOINC, either the same version, or a newer one from http://boinc.berkeley.edu/dl/

I\'m running 5.3.17 without problem so you could give that a try. Backup the BOINC folder before doing this though, just to be safe.

The trickle_up_*.sent files indicate (as you know from bitter experience) that you\'ve tried to send the files and got a bad response.

The last time that system successfully uploaded a trickle was at 10 Feb 2006 14:07:20 UTC. Did you change anything at your end shortly after this? Upgrade to BOINC 5.2.13? Internet connection change?

There\'s also something strange about your computer list ndr. Your Athlon 3200+ has 3 different host ids (330493, 331046 and 331919) but all the trickles are recorded for the first one. When the host id changes trickles are normally recorded with the new host id. My first step would be to merge the 3 ids.

If that didn\'t work I\'d try to send the trickle_up files in smaller batches (move some to a separate directory, do a project update, move a few back do another update etc).

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

I\'m not sure. I left the tenth in the evening only to come back a week later (and left compu running). There would be some internet failure later that week, but there was none that weekend.

Didnt know i could merge them, I was already wondering why it said I had three compu\'s. Anyways, merging them didnt help.

Removing the oldest file didnt help (restarted BOINC after I tried that). Nor did removing all but one (left the second oldest).

Status in my work tab says ready to report.

I reinstalled BOINC earlier this week, but i installed 5.2.13 again. Downloaded it from climate.net again, so i wouldnt know where to get 5.3.17.

So... I could try sending them from another compu, but i thought it would be the corrupt message (and a broken chain). It will have to happen next week anyways, since ive to go now. Sorry :(

Well, for some reasons I just connected to the server again. Don\'t know how, don\'t know why, but it seems I am back in business again.