• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

No uploads for 5 days...

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Voodoo Rufus

Powder Junkie Moderator
Joined
Sep 20, 2001
Location
Bakersfield, CA
I tried a manual update, and both of my seti machines have 5 days of completed work yet to upload. Is it a problem on my end of Berkeley's end?
 
2/17/2008 4:36:55 PM|SETI@home|Computation for task 29no06ag.4132.7436.11.7.74_0 finished
2/17/2008 4:36:55 PM|SETI@home|Starting 26ja07aa.10569.296758.5.7.151_1
2/17/2008 4:36:55 PM|SETI@home|Starting task 26ja07aa.10569.296758.5.7.151_1 using setiathome_enhanced version 528
2/17/2008 4:36:57 PM|SETI@home|[file_xfer] Started upload of file 29no06ag.4132.7436.11.7.74_0_0
2/17/2008 4:36:59 PM|SETI@home|[error] Error on file upload: no command
2/17/2008 4:36:59 PM|SETI@home|[file_xfer] Permanently failed upload of 29no06ag.4132.7436.11.7.74_0_0
2/17/2008 4:36:59 PM|SETI@home|Giving up on upload of 29no06ag.4132.7436.11.7.74_0_0: server rejected file
2/17/2008 5:36:24 PM|SETI@home|Sending scheduler request: Requested by user
2/17/2008 5:36:24 PM|SETI@home|Requesting 367784 seconds of new work, and reporting 29 completed tasks
2/17/2008 5:36:29 PM|SETI@home|Scheduler RPC succeeded [server version 601]
2/17/2008 5:36:29 PM|SETI@home|Message from server: Incomplete request received.
2/17/2008 5:36:29 PM|SETI@home|Deferring communication for 1 min 0 sec
2/17/2008 5:36:29 PM|SETI@home|Reason: no work from project
2/17/2008 5:37:33 PM|SETI@home|Fetching scheduler list
2/17/2008 5:37:38 PM|SETI@home|Master file download succeeded
2/17/2008 5:37:43 PM|SETI@home|Sending scheduler request: To report completed tasks
2/17/2008 5:37:43 PM|SETI@home|Requesting 367766 seconds of new work, and reporting 29 completed tasks
2/17/2008 5:37:48 PM|SETI@home|Scheduler RPC succeeded [server version 601]
2/17/2008 5:37:48 PM|SETI@home|Message from server: Incomplete request received.
2/17/2008 5:37:48 PM|SETI@home|Deferring communication for 1 min 0 sec
2/17/2008 5:37:48 PM|SETI@home|Reason: no work from project
2/17/2008 5:38:49 PM|SETI@home|Sending scheduler request: To report completed tasks
2/17/2008 5:38:49 PM|SETI@home|Requesting 367714 seconds of new work, and reporting 29 completed tasks
2/17/2008 5:38:54 PM|SETI@home|Scheduler RPC succeeded [server version 601]
 
I'm presently on the rig at work and I haven't had any problems with my laptop uploading. Looking at my stats, it seems that my home rigs are generally uploading ok too, except for 1 machine. Hopefully I will be able to get in from the job tomorrow; this job has stretched out wayyyy longer than it should have and I've been on it for 18 days now. :( Makes for a good paycheck but sucks as far as living goes.
 
Okay Voodoo.. Ive had a look around, and it seems theres a growing list of people having the same/similar problems to you (instead of "Message from server: Incomplete request received.", they are getting "[file_xfer] Giving up on upload of xxxx: permanent upload error")...

Its been brought to the attention of the BOINC devs, and hopefully they are looking into it. Until then, there have been reports of people who have stopped the BOINC service and restarted it, and the problem went away. If youre not running it as a service, then close BOINC, and restart. (Snooze before hand if you're using Vista).

If that doesnt help, Im not sure what will. It sounds like a server problem to me. A quick check of the Bandwidth usage graphs show that the upload/download servers are being hit pretty hard. Most probably due to these small WU that we have been having the past couple of days.

I guess my only advice is to wait it out Im afraid :(.. another alternative is to basically "cut your losses" and do a project reset, but that should be a last resort imo.
 
Well I stopped BOINC and restarted it, and now all of my completed WUs are not displayed?
It is downloading new units now, with some failures.

I know the feeling, Doctor. I just finished an 18 day hitch as well, and I'm beat both mentally and physically. The next paycheck should be phenomenal, though. But was it worth it?
 
Hmm. A quick read on the SETI forums gave me this:

Volunteer Tester @ SETI forums said:
# 'Validate error' (and we're not talking about anything else here, like computation errors) tends only to happen if you try to "report" a result too soon after "uploading" it.
# 'Reporting too soon' can happen sporadically to anyone, but is endemic to BOINC v5.10.(<=13) with a connect interval of zero, or with certain third-party 'optimised' BOINC clients.
# The staff run a manual script once every 24 hours or so, to correct as many of these errors as they can.
# The script does not parse this thread looking for result ID numbers! It works directly on the underlying database at Berkeley.

Though the problem doesnt specifically apply to you, the general idea of getting work claimed in retrospect is at least there. I had a look at the cosmology@home site, as people over there were having the same problem, and the project mods decided to grant credit to everyone for current WU, regardless of whether they had crunched them or not. I can sense something similar happening to SETI. Its been brought to the devs attention, and as the number of people affected complain rises, so too will the rate at which SETI fixes the problem.

Ill keep and eye on these threads Thread 1 - error on file upload, Thread 2 - BOINC developers' forum, and Thread 3 - Validation errors (long thread..) and see what happens.
 
Well I know the feeling, Doctor. I just finished an 18 day hitch as well, and I'm beat both mentally and physically. The next paycheck should be phenomenal, though. But was it worth it?

God, the drama seems to be getting worse. They decided to block squeeze and went and shot some perfs at a water sand they want to isolate and now they can't get an injection rate. Since we still have mud in the hole I am still stuck out here until they decide what to do next. There is talk of doing a direct displacement with their CaBr fluid, but no telling when that will happen. When they went to retrieve the retainer the slips broke off and now they are running a junk basket to try to get them.

Sorry about the thread hijack folks; I am one frustrated person right now (as well as horny).:bang head
 
Back