It happened again, but not in so disastrous a fashion.

Workunit #424771170 got to 100%, then promptly reset itself, but only back to 99.6xx% When it worked its way back up to 100%, it declared itself ready to report.

I updated the project and the workunit validated immediately (I was the wingman).

That behavior is normal for 5.03. The project added repetitive pulse finding for negative DMs but didn't revise the progress calculation. So it shows 99.6 to 100% while doing one polarity and again doing the other. Actually that recycle of about 0.4% happens 111 times in total during the crunch, but is only really obvious at the end.

The progress code was updated after the 5.03 release, the versions of AP at SETI Beta no longer have that cosmetic flaw.

I am torn at this point about continuing the troublesome workunit noted in the post immediately prior to this one. I would appreciate any advice.

The host took a little over 8 days for the one it just finished, so with a May 16 deadline there's ample time. I do understand that it is discouraging to have lost so much time. If it were mine I'd probably try to finish it, I feel some sense of obligation to complete work I've downloaded if at all possible.

If you're willing to put in some small additional effort and keep track of ongoing changes, the optimized AP app would probably do the work in about 3 days on your host.

                                                               Joe

{...} I feel some sense of obligation to complete work I've downloaded if at all possible.

If you're willing to put in some small additional effort and keep track of ongoing changes, the optimized AP app would probably do the work in about 3 days on your host.

                                                               Joe

Thanks for your reply :)

I also feel the obligation to finish downloaded work, which is why I was torn about continuing. I will give this one another shot.

Being completely new to optimized apps, I wonder if there is a thread on the boards here that provides instructions for implementing them.

---

...
Being completely new to optimized apps, I wonder if there is a thread on the boards here that provides instructions for implementing them.

Most of the advice here is good, but there's so much of it...

A clear illustrated guide to installing optimized apps is in BOINC FAQ Service SETI: Installing an optimised application. It's not for the exact package you'll want, but explains the procedure well.

MarkJ's originating post in the app_info for AP500, AP503, MB603 and MB608 thread is very good (read p_fpops where it says p_flops, though). You already have the CUDA files and BOINC 6.6.20 installed, so just need the optimised S@H Enhanced and Astropulse files. I suggest the "Win32_AK_AP_SSE3.7z" package from Arkayn's Multibeam and Astropulse Combined Packages page.

I've probably forgotten to mention something, ask if you run into any snags.

                                                                  Joe

Hm, just got this and haven't seen anything like it before:
Error in ap_remove_radar.cpp: generate_envelope: num_ffts_performed < 100. Blanking too much RFI?

Anyone have any ideas? The error happend immediately, so no crunching time lost. Just wondering what would cause this.

-Dave

---

Same here. Error in ap_remove_radar.cpp: generate_envelope: num_ffts_performed < 100. Blanking too much RFI?

Is it just the WU or maby someting wrong with my computer?

---

Sounds like maybe a bad batch of WUs, but I'd like to hear from someone who knows what it actually means.

-Dave

[edit] For those who want to see, Here's the WU I returned

---

A link or two would help us to see the entire message in context.

Opps! sorry.
Here it is 1215329122

---

Opps! sorry.
Here it is 1215329122

Yes, that's the Lunatics app - as it should be for this thread.

I've posted at Lunatics to ask if someone can come and give a fuller explanation, but at first glance it seems like a planned "don't bother wasting any time on this one" sort of message.

However, it's just possible that the developers would be interested in seeing the datafile for one of these WUs, so if anyone sees one before reporting it back to the servers, could they have a go at identifying the 8MB downloaded datafile in their project directory and copying it to a safe place, please?

Maybe it was an error related to the download.
This was the messages prior to the error.

2009-04-29 19:00:25|SETI@home|Sending scheduler request: To fetch work. Requesting 6623 seconds of work, reporting 0 completed tasks
2009-04-29 19:01:26|SETI@home|Scheduler request completed: got 1 new tasks
2009-04-29 19:01:28|SETI@home|Started download of ap_14mr09aa_B3_P1_00328_20090429_18241.wu
2009-04-29 19:01:44||Project communication failed: attempting access to reference site
2009-04-29 19:01:44|SETI@home|Temporarily failed download of ap_14mr09aa_B3_P1_00328_20090429_18241.wu: HTTP error
2009-04-29 19:01:44|SETI@home|Backing off 1 min 0 sec on download of ap_14mr09aa_B3_P1_00328_20090429_18241.wu
2009-04-29 19:01:45||Internet access OK - project servers may be temporarily down.
2009-04-29 19:02:44|SETI@home|Started download of ap_14mr09aa_B3_P1_00328_20090429_18241.wu
2009-04-29 19:04:12|SETI@home|Finished download of ap_14mr09aa_B3_P1_00328_20090429_18241.wu
2009-04-29 19:04:13|SETI@home|Starting ap_14mr09aa_B3_P1_00328_20090429_18241.wu_0
2009-04-29 19:04:13|SETI@home|Starting task ap_14mr09aa_B3_P1_00328_20090429_18241.wu_0 using astropulse_v5 version 503
2009-04-29 19:04:15|SETI@home|Computation for task ap_14mr09aa_B3_P1_00328_20090429_18241.wu_0 finished
2009-04-29 19:04:15|SETI@home|Output file ap_14mr09aa_B3_P1_00328_20090429_18241.wu_0_0 for task ap_14mr09aa_B3_P1_00328_20090429_18241.wu_0 absent

---

Unrelated:

Not really a problem or an issue, just felt like posting this somewhere.. Typically the "exited with zero status, but no finished file" applies for all running tasks (at least, that's how I've always seen it happen), but on one of my rigs, just one of the two running AP_v5's with r112 did that, and 33 hours in (which is about 67%), decided to start over at zero.

*sigh* I know it happens, but I don't think I've ever noticed one start over at zero, even though I contribute elsewhere in the forum saying "most times it just picks up where it left off, but every now and then, it starts over at the beginning."

That's weird that just one did that and not both. I went in three weeks ago and added the data directory to the exclusion list for the A/V software just to make sure it wouldn't interfere with anything.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

The "generate_envelope: num_ffts_performed < 100." error is related to the improved radar blanking code using "shaped noise". In order to determine how to filter the random sequence used for blanking, the code needs to find enough good data to establish an envelope. So the error definitely is caused by the WU having almost continuous noise.

The sample I got was task 1214787541 for WU 437550542. As you can see, that WU has reached the "Too many error results" state, with stock applications reporting the same error.

The optimized apps are using stock code for that part, there may be some optimization possible but it hasn't been coded yet. That code just does an exit(-1) without ever writing an output file, so also leads to BOINC complaining that there's nothing to upload.

The 5.05 being tested at SETI Beta would produce the same stderr text. But it does write an output file, touch a finished file, and uses exit(0) so it would not be charged as a "client error". Instead it's like a result_overflow case claiming miniscule credit but a succesful completion. Results would have no signals so the first two result files should match and no resends would go out.

                                                                Joe

Thanks for the explanation, Joe. Should we still try to capture any data if this happens again? (I currently have all my APs that are in cache since earlier today saved.)

-Dave

---

Thanks for the explanation, Joe. Should we still try to capture any data if this happens again? (I currently have all my APs that are in cache since earlier today saved.)

-Dave

If the wingmate hosts agree the work is too noisy to process, IMO there's no need to save the WUs. If the project wants to investigate, there are probably plenty which have 2 or 3 errors but still have some "in progress" tasks so the WU is still on the download server. I doubt they'll want to, anyhow, the data is just too noisy sometimes and there's nothing which can be done. It's expected there will be some fraction like that, a fully redundant backup of all the data chain isn't practical on a shoestring budget and noise can be encountered at any stage of delivery.

                                                                 Joe

I have not been able to download projects for seveal days. The download starts and then seems to crash for some reason. I have aborted several downloads thinking that a clean download would solve the problem. But the new project download starts but does not complete.

Below is my log from today.

Is there anything I can to to fix things on my end?

4/29/2009 5:57:24 PM Starting BOINC client version 6.6.20 for windows_intelx86
4/29/2009 5:57:24 PM log flags: task, file_xfer, sched_ops
4/29/2009 5:57:24 PM Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
SNIP
4/29/2009 5:57:25 PM Processor: 1 AuthenticAMD AMD Athlon(tm) XP 3200+ [x86 Family 6 Model 10 Stepping 0]
4/29/2009 5:57:25 PM Processor features: fpu tsc sse 3dnow mmx
4/29/2009 5:57:25 PM OS: Microsoft Windows XP: Home x86 Editon, Service Pack 3, (05.01.2600.00)
4/29/2009 5:57:25 PM Memory: 1.44 GB physical, 2.08 GB virtual
4/29/2009 5:57:25 PM Disk: 149.05 GB total, 95.71 GB free
4/29/2009 5:57:25 PM Local time is UTC -5 hours
4/29/2009 5:57:26 PM No CUDA devices found
4/29/2009 5:57:26 PM No coprocessors
4/29/2009 5:57:27 PM Not using a proxy
4/29/2009 5:57:27 PM SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 1840584; location: home; project prefs: default
4/29/2009 5:57:28 PM SETI@home General prefs: from SETI@home (last modified 30-Nov-2008 15:37:51)
4/29/2009 5:57:28 PM SETI@home Computer location: home
4/29/2009 5:57:28 PM SETI@home General prefs: no separate prefs for home; using your defaults
4/29/2009 5:57:28 PM Reading preferences override file
4/29/2009 5:57:28 PM Preferences limit memory usage when active to 735.74MB
4/29/2009 5:57:28 PM Preferences limit memory usage when idle to 1324.34MB
4/29/2009 5:57:28 PM Preferences limit disk usage to 74.52GB
4/29/2009 5:57:29 PM SETI@home [error] File ap_14mr09aa_B1_P1_00233_20090428_20313.wu has wrong size: expected 8392045, got 1054056
4/29/2009 5:57:29 PM SETI@home Started download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu
4/29/2009 5:59:09 PM Project communication failed: attempting access to reference site
4/29/2009 5:59:11 PM SETI@home Temporarily failed download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu: HTTP error
4/29/2009 5:59:11 PM SETI@home Backing off 1 min 0 sec on download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu
4/29/2009 5:59:15 PM Internet access OK - project servers may be temporarily down.
4/29/2009 6:00:09 PM SETI@home [error] File ap_14mr09aa_B1_P1_00233_20090428_20313.wu has wrong size: expected 8392045, got 1327584
4/29/2009 6:00:09 PM SETI@home Started download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu
4/29/2009 6:01:59 PM Project communication failed: attempting access to reference site
4/29/2009 6:01:59 PM SETI@home Temporarily failed download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu: HTTP error
4/29/2009 6:01:59 PM SETI@home Backing off 1 min 30 sec on download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu
4/29/2009 6:02:00 PM Internet access OK - project servers may be temporarily down.
4/29/2009 6:03:29 PM SETI@home [error] File ap_14mr09aa_B1_P1_00233_20090428_20313.wu has wrong size: expected 8392045, got 1629784
4/29/2009 6:03:29 PM SETI@home Started download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu
4/29/2009 6:04:43 PM SETI@home Sending scheduler request: To fetch work.
4/29/2009 6:04:43 PM SETI@home Reporting 1 completed tasks, requesting new tasks
4/29/2009 6:04:58 PM SETI@home Scheduler request completed: got 1 new tasks
4/29/2009 6:05:00 PM SETI@home Started download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:06:31 PM Project communication failed: attempting access to reference site
4/29/2009 6:06:31 PM SETI@home Temporarily failed download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu: HTTP error
4/29/2009 6:06:31 PM SETI@home Backing off 1 min 0 sec on download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:06:33 PM Internet access OK - project servers may be temporarily down.
4/29/2009 6:07:31 PM SETI@home [error] File ap_14mr09ac_B5_P1_00074_20090429_31827.wu has wrong size: expected 8392043, got 253048
4/29/2009 6:07:31 PM SETI@home Started download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:09:13 PM Project communication failed: attempting access to reference site
4/29/2009 6:09:13 PM SETI@home Temporarily failed download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu: HTTP error
4/29/2009 6:09:13 PM SETI@home Backing off 1 min 0 sec on download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:09:15 PM Internet access OK - project servers may be temporarily down.
4/29/2009 6:10:13 PM SETI@home [error] File ap_14mr09ac_B5_P1_00074_20090429_31827.wu has wrong size: expected 8392043, got 534768
4/29/2009 6:10:13 PM SETI@home Started download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:12:33 PM Project communication failed: attempting access to reference site
4/29/2009 6:12:33 PM SETI@home Temporarily failed download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu: HTTP error
4/29/2009 6:12:33 PM SETI@home Backing off 1 min 0 sec on download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:12:35 PM Internet access OK - project servers may be temporarily down.
4/29/2009 6:13:33 PM SETI@home [error] File ap_14mr09ac_B5_P1_00074_20090429_31827.wu has wrong size: expected 8392043, got 922984
4/29/2009 6:13:33 PM SETI@home Started download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:15:21 PM Project communication failed: attempting access to reference site
4/29/2009 6:15:21 PM SETI@home Temporarily failed download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu: HTTP error
4/29/2009 6:15:21 PM SETI@home Backing off 1 min 0 sec on download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:15:22 PM Internet access OK - project servers may be temporarily down.
4/29/2009 6:16:22 PM SETI@home [error] File ap_14mr09ac_B5_P1_00074_20090429_31827.wu has wrong size: expected 8392043, got 1221088
4/29/2009 6:16:22 PM SETI@home Started download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:18:07 PM Project communication failed: attempting access to reference site
4/29/2009 6:18:07 PM SETI@home Temporarily failed download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu: HTTP error
4/29/2009 6:18:07 PM SETI@home Backing off 1 min 52 sec on download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:18:08 PM Internet access OK - project servers may be temporarily down.
4/29/2009 6:20:00 PM SETI@home [error] File ap_14mr09ac_B5_P1_00074_20090429_31827.wu has wrong size: expected 8392043, got 1511000
4/29/2009 6:20:00 PM SETI@home Started download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:21:41 PM Project communication failed: attempting access to reference site
4/29/2009 6:21:41 PM SETI@home Temporarily failed download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu: HTTP error
4/29/2009 6:21:41 PM SETI@home Backing off 4 min 16 sec on download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:21:42 PM Internet access OK - project servers may be temporarily down.
4/29/2009 6:25:58 PM SETI@home [error] File ap_14mr09ac_B5_P1_00074_20090429_31827.wu has wrong size: expected 8392043, got 1788624
4/29/2009 6:25:58 PM SETI@home Started download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:27:47 PM Project communication failed: attempting access to reference site
4/29/2009 6:27:47 PM SETI@home Temporarily failed download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu: HTTP error
4/29/2009 6:27:47 PM SETI@home Backing off 1 min 1 sec on download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:27:48 PM Internet access OK - project servers may be temporarily down.
4/29/2009 6:28:48 PM SETI@home [error] File ap_14mr09ac_B5_P1_00074_20090429_31827.wu has wrong size: expected 8392043, got 2090824
4/29/2009 6:28:48 PM SETI@home Started download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:30:26 PM Project communication failed: attempting access to reference site
4/29/2009 6:30:26 PM SETI@home Temporarily failed download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu: HTTP error
4/29/2009 6:30:26 PM SETI@home Backing off 45 min 27 sec on download of ap_14mr09ac_B5_P1_00074_20090429_31827.wu
4/29/2009 6:30:27 PM Internet access OK - project servers may be temporarily down.

---

You have two things happening potenially that I see.

The first is anytime the Severs State
Temporarily failed download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu: HTTP error there could be a prblem with the server or the coomunications with the server
This can happen when the servers are very busy or there is a problem with the Internet getting to them.

The Second is that in this situation somtimes a Project Reset can clear things that are being caused by corrupt files on your computer that affect the commincations. If you have no Workunits in Progess then a Reset will no hurt and it will resend any scheduled work.

Regards

Pappa

I have not been able to download projects for seveal days. The download starts and then seems to crash for some reason. I have aborted several downloads thinking that a clean download would solve the problem. But the new project download starts but does not complete.

Below is my log from today.

Is there anything I can to to fix things on my end?

4/29/2009 5:57:24 PM Starting BOINC client version 6.6.20 for windows_intelx86
4/29/2009 5:57:24 PM log flags: task, file_xfer, sched_ops
4/29/2009 5:57:24 PM Libraries: libcurl/7.19.4 OpenSSL/0.9.8j zlib/1.2.3
SNIP
4/29/2009 5:57:25 PM Processor: 1 AuthenticAMD AMD Athlon(tm) XP 3200+ [x86 Family 6 Model 10 Stepping 0]
4/29/2009 5:57:25 PM Processor features: fpu tsc sse 3dnow mmx
4/29/2009 5:57:25 PM OS: Microsoft Windows XP: Home x86 Editon, Service Pack 3, (05.01.2600.00)
4/29/2009 5:57:25 PM Memory: 1.44 GB physical, 2.08 GB virtual
4/29/2009 5:57:25 PM Disk: 149.05 GB total, 95.71 GB free
4/29/2009 5:57:25 PM Local time is UTC -5 hours
4/29/2009 5:57:26 PM No CUDA devices found
4/29/2009 5:57:26 PM No coprocessors
4/29/2009 5:57:27 PM Not using a proxy
4/29/2009 5:57:27 PM SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 1840584; location: home; project prefs: default
4/29/2009 5:57:28 PM SETI@home General prefs: from SETI@home (last modified 30-Nov-2008 15:37:51)
4/29/2009 5:57:28 PM SETI@home Computer location: home
4/29/2009 5:57:28 PM SETI@home General prefs: no separate prefs for home; using your defaults
4/29/2009 5:57:28 PM Reading preferences override file
4/29/2009 5:57:28 PM Preferences limit memory usage when active to 735.74MB
4/29/2009 5:57:28 PM Preferences limit memory usage when idle to 1324.34MB
4/29/2009 5:57:28 PM Preferences limit disk usage to 74.52GB
4/29/2009 5:57:29 PM SETI@home [error] File ap_14mr09aa_B1_P1_00233_20090428_20313.wu has wrong size: expected 8392045, got 1054056
4/29/2009 5:57:29 PM SETI@home Started download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu
4/29/2009 5:59:09 PM Project communication failed: attempting access to reference site
4/29/2009 5:59:11 PM SETI@home Temporarily failed download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu: HTTP error
4/29/2009 5:59:11 PM SETI@home Backing off 1 min 0 sec on download of ap_14mr09aa_B1_P1_00233_20090428_20313.wu
4/29/2009 5:59:15 PM Internet access OK - project servers may be temporarily down.

---

Please consider a Donation to the Seti Project.

...
The Second is that in this situation somtimes a Project Reset can clear things that are being caused by corrupt files on your computer that affect the commincations. If you have no Workunits in Progess then a Reset will no hurt and it will resend any scheduled work.

Regards

Pappa

The resend feature is not turned on here, though it is at SETI Beta. A Project Reset here turns any uncompleted work into ghosts, since there's nothing which tells the servers that the work has been deleted.

If the situation is serious enough, detaching from the project then reattaching is the best way of cleaning up. That also deletes all work, but when the host attaches again the servers deduce that the user detached it, mark the work "Client detached" and create new tasks to be sent to other hosts. That's not an error, so the host's daily quota isn't reduced. The detach does clear almost all project information on the host, so it starts with nothing on the statistics tab of BOINC Manager, for instance.

                                                                 Joe

I reset the project and ran into the same problem. This never happened with the old product.

Frustrated in South Dakota :o)

4/29/2009 10:49:33 PM SETI@home Resetting project
4/29/2009 10:49:35 PM SETI@home Sending scheduler request: To fetch work.
4/29/2009 10:49:35 PM SETI@home Requesting new tasks
4/29/2009 10:49:40 PM SETI@home Scheduler request completed: got 1 new tasks
4/29/2009 10:49:42 PM SETI@home Started download of astropulse_5.03_windows_intelx86.exe
4/29/2009 11:10:24 PM Project communication failed: attempting access to reference site
4/29/2009 11:10:24 PM SETI@home Temporarily failed download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu: HTTP error
4/29/2009 11:10:24 PM SETI@home Backing off 2 min 21 sec on download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 11:10:27 PM Internet access OK - project servers may be temporarily down.

4/29/2009 10:49:42 PM SETI@home Started download of astropulse_5.03_AUTHORS
4/29/2009 10:49:43 PM SETI@home Finished download of astropulse_5.03_AUTHORS
4/29/2009 10:49:43 PM SETI@home Started download of astropulse_5.03_COPYING
4/29/2009 10:49:52 PM SETI@home Finished download of astropulse_5.03_COPYING
4/29/2009 10:49:52 PM SETI@home Started download of astropulse_5.03_COPYRIGHT
4/29/2009 10:49:54 PM SETI@home Finished download of astropulse_5.03_COPYRIGHT
4/29/2009 10:49:54 PM SETI@home Started download of ap_graphics_5.03_windows_intelx86.exe
4/29/2009 10:53:08 PM Project communication failed: attempting access to reference site
4/29/2009 10:53:08 PM SETI@home Temporarily failed download of astropulse_5.03_windows_intelx86.exe: HTTP error
4/29/2009 10:53:08 PM SETI@home Backing off 1 min 0 sec on download of astropulse_5.03_windows_intelx86.exe
4/29/2009 10:53:08 PM SETI@home Started download of libfftw3f-3-1-1a_upx.dll
4/29/2009 10:53:09 PM Internet access OK - project servers may be temporarily down.
4/29/2009 10:53:20 PM Project communication failed: attempting access to reference site
4/29/2009 10:53:20 PM SETI@home Temporarily failed download of ap_graphics_5.03_windows_intelx86.exe: HTTP error
4/29/2009 10:53:20 PM SETI@home Backing off 1 min 0 sec on download of ap_graphics_5.03_windows_intelx86.exe
4/29/2009 10:53:20 PM SETI@home Started download of ap403.jpg
4/29/2009 10:53:21 PM Internet access OK - project servers may be temporarily down.
4/29/2009 10:53:23 PM SETI@home Finished download of ap403.jpg
4/29/2009 10:53:23 PM SETI@home Started download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 10:56:33 PM Project communication failed: attempting access to reference site
4/29/2009 10:56:35 PM SETI@home Temporarily failed download of libfftw3f-3-1-1a_upx.dll: HTTP error
4/29/2009 10:56:35 PM SETI@home Backing off 1 min 0 sec on download of libfftw3f-3-1-1a_upx.dll
4/29/2009 10:56:35 PM SETI@home Started download of arecibo_181.png
4/29/2009 10:56:36 PM Internet access OK - project servers may be temporarily down.
4/29/2009 10:56:49 PM Project communication failed: attempting access to reference site
4/29/2009 10:56:49 PM SETI@home Temporarily failed download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu: HTTP error
4/29/2009 10:56:49 PM SETI@home Backing off 1 min 0 sec on download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 10:56:49 PM SETI@home Started download of sah_40.png
4/29/2009 10:56:50 PM Internet access OK - project servers may be temporarily down.
4/29/2009 10:56:50 PM SETI@home Finished download of sah_40.png
4/29/2009 10:56:50 PM SETI@home Started download of sah_banner_290.png
4/29/2009 10:56:59 PM SETI@home Finished download of sah_banner_290.png
4/29/2009 10:56:59 PM SETI@home Started download of sah_ss_290.png
4/29/2009 10:57:05 PM SETI@home Finished download of arecibo_181.png
4/29/2009 10:57:06 PM SETI@home [error] File astropulse_5.03_windows_intelx86.exe has wrong size: expected 471040, got 285816
4/29/2009 10:57:07 PM SETI@home Started download of astropulse_5.03_windows_intelx86.exe
4/29/2009 10:57:19 PM SETI@home Finished download of sah_ss_290.png
4/29/2009 10:57:20 PM SETI@home [error] File ap_graphics_5.03_windows_intelx86.exe has wrong size: expected 294912, got 285816
4/29/2009 10:57:20 PM SETI@home Started download of ap_graphics_5.03_windows_intelx86.exe
4/29/2009 10:57:23 PM SETI@home Finished download of ap_graphics_5.03_windows_intelx86.exe
4/29/2009 10:57:34 PM SETI@home [error] File libfftw3f-3-1-1a_upx.dll has wrong size: expected 448600, got 285816
4/29/2009 10:57:35 PM SETI@home Started download of libfftw3f-3-1-1a_upx.dll
4/29/2009 10:59:14 PM SETI@home Finished download of astropulse_5.03_windows_intelx86.exe
4/29/2009 10:59:14 PM SETI@home [error] File ap_15fe09aa_B5_P0_00297_20090412_09702.wu has wrong size: expected 8392047, got 285816
4/29/2009 10:59:14 PM SETI@home Started download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 10:59:21 PM SETI@home Finished download of libfftw3f-3-1-1a_upx.dll
4/29/2009 11:01:21 PM Project communication failed: attempting access to reference site
4/29/2009 11:01:21 PM SETI@home Temporarily failed download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu: HTTP error
4/29/2009 11:01:21 PM SETI@home Backing off 1 min 0 sec on download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 11:01:22 PM Internet access OK - project servers may be temporarily down.
4/29/2009 11:02:21 PM SETI@home [error] File ap_15fe09aa_B5_P0_00297_20090412_09702.wu has wrong size: expected 8392047, got 633072
4/29/2009 11:02:21 PM SETI@home Started download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 11:04:32 PM Project communication failed: attempting access to reference site
4/29/2009 11:04:32 PM SETI@home Temporarily failed download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu: HTTP error
4/29/2009 11:04:32 PM SETI@home Backing off 1 min 0 sec on download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 11:04:33 PM Internet access OK - project servers may be temporarily down.
4/29/2009 11:05:32 PM SETI@home [error] File ap_15fe09aa_B5_P0_00297_20090412_09702.wu has wrong size: expected 8392047, got 1000808
4/29/2009 11:05:32 PM SETI@home Started download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 11:07:39 PM Project communication failed: attempting access to reference site
4/29/2009 11:07:39 PM SETI@home Temporarily failed download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu: HTTP error
4/29/2009 11:07:39 PM SETI@home Backing off 1 min 0 sec on download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 11:07:41 PM Internet access OK - project servers may be temporarily down.
4/29/2009 11:08:39 PM SETI@home [error] File ap_15fe09aa_B5_P0_00297_20090412_09702.wu has wrong size: expected 8392047, got 1352160
4/29/2009 11:08:39 PM SETI@home Started download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu

4/29/2009 11:10:24 PM Project communication failed: attempting access to reference site
4/29/2009 11:10:24 PM SETI@home Temporarily failed download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu: HTTP error
4/29/2009 11:10:24 PM SETI@home Backing off 2 min 21 sec on download of ap_15fe09aa_B5_P0_00297_20090412_09702.wu
4/29/2009 11:10:27 PM Internet access OK - project servers may be temporarily down.

---

[mode=whining]

{...} Workunit #424771170 got to 100%, then promptly reset itself, but only back to 99.6xx% When it worked its way back up to 100%, it declared itself ready to report.

I updated the project and the workunit validated immediately {...}

It appears I spoke too soon about the above referenced workunit. It is no longer valid, it is not invalid, it is not pending...

It is vanished!

That workunit apparently no longer exists in the project's database.

I'm not in this for the credits. I know that their value in the real world is precisely nil. What the credits represent for me is evidence that I am contributing to the goals of the project. When a workunit representing over 200 hours of CPU time just vanishes into thin air, I have to question whether or not I'm wasting my time (and electricity) by attempting to contribute to the goals of the project.

Is vanishing workunits a vanishingly rare occurrence?

This is my record on Astropulse workunits so far:

1 valid
1 vanished
1 started over from scratch
2 in progress

[/whining]

Thank you for indulging my whining :p

---

D@mm

If I was thinking elsewise, I would say that we have some corrupt WU's
More Likely is that you are experiencing a "timeout condition" in which you have less than a quarter of the "larger files" (the Ap workunit). The tiny files do okay, the larger files do not.

So without trying to have you learn how to debug these issues need to find a quick solution.

From My Standpoint that leaves us with two things to look, The network or writing to the Hardisk.

If I think first about the Hard Drive, Fragmentation or a Dying Drive can cause a write/fail/retry that slows the inflow of traffic and timeouts. Small Files are okay.

Second, depending on the OS (registry settings) and Network Card Driver issues things slow to a crawl.

So I ask when was the last time that you ran "defrag" on the harddrive?
Second do you know what CHKDSK is?

In an enviroment where the default states write work in progress to your harddrive every 60 seconds... Time can be our enemy.

Hope this is starting to help, I look forward to your answers.

Regards

---

Please consider a Donation to the Seti Project.