I'm seeing a lot of messages after I send work that say;

Started upload of 13ja04aa.11634.28576.984656.63_3_0
Finished upload of 13ja04aa.11634.28576.984656.63_3_0
No data transfered

When did you download this WU? If it was between the 11th and th 19th, S@H has no record of it, so it probably doesn't see the need to transfer the data.

Just a guess...

<a> [/url]

> When did you download this WU? If it was between the 11th and th 19th, S@H has
> no record of it, so it probably doesn't see the need to transfer the data.
>
> Just a guess...

Don't think thats right. I have a bunch of workunits from the the 16th and 17th, most of them got transferred OK.

The ones that don't get either a "temporary upload failure" (and show in BOINCs Transfer tab until its successfully uploaded) or show the same "no data transferred" message and show very little CPU time in the Work tab. The "transfer error"

My guess is these workunits have interference that overwhelms the receiver, and the seti client stops analyzing it after the output reaches some pre-determined file size. Thats how seti1 worked, don't see how this one is any different.

Walt

I have sometimes the same message. On 5 WU's processed today it happened 3 times. All WU's downloaded yesterday.
There is no data that stays in the transfer tab when it happens.

Greetings from Belgium.

I received it on Aug. 20 2004. It's deadline is 2004-09-03 16:50:38


> When did you download this WU? If it was between the 11th and th 19th, S@H has
> no record of it, so it probably doesn't see the need to transfer the data.
>
> Just a guess...
>
> <a> [/url]
>

> I received it on Aug. 20 2004. It's deadline is 2004-09-03 16:50:38
>
>

Does the workunit still show in the Work tab? If its still there (status would be "Ready to report", what does it show for the CPU time? And how does that compare with normal workunits?

> Does the workunit still show in the Work tab? If its still there (status
> would be "Ready to report", what does it show for the CPU time? And how does
> that compare with normal workunits?

In my case, the WU's had still the "Ready to report" status. The 3 Wu's had a normal CPU time compared to the others.

It is still listed on the work tab and says "Ready to report". The CPU time is short for that wu. I have had three in a row at least that say "No data transfered". The other ones have normal completion times.



>
> > I received it on Aug. 20 2004. It's deadline is 2004-09-03 16:50:38
> >
> >
>
> Does the workunit still show in the Work tab? If its still there (status
> would be "Ready to report", what does it show for the CPU time? And how does
> that compare with normal workunits?
>

That what I get, short CPU tine, no data transferred. Too bad it doesn't leave the output file around so we can see just how big it is. But the short CPU time indicates thats what the problem is, there nothing else mentioned that would stop the analysis.

The original project FAQ had an explanation for this. Figured it still held even with the newer software. See Why do some work units take very little time to complete?

Walt

Sorry to burst some bubbles here about the CPU time having an impact on the "No data transfered" thing. My last WU took an average time of 03:43:18 and when uploaded, "No data transfered". 4 WUs prior to this one I had one that did not have the "No data transfered" message and yet it only took 00:04:39 to complete. There must be some other explanation for or problem causing this phenomenon. I have had 8 such uploads since 8:00 AM Friday, 8/20/04 (California USA time). Other "No data transfered" WUs were completed in the above "average" time, give or take a few minutes/seconds. L8R....

---
<p>Rick A. - BOINCing right along now....</p>

> I received it on Aug. 20 2004. It's deadline is 2004-09-03 16:50:38
>
>
> > When did you download this WU? If it was between the 11th and th 19th,
> S@H has
> > no record of it, so it probably doesn't see the need to transfer the
> data.
> >
> > Just a guess...
> >
> > <a>

I watched the last wu go through on the transfer tab. It happened fast but it appeared that nothing was sent through under the size column. It took the normal 3hrs. 20min to complete.

Hm, perhaps I overstated the CPU thing, I was using it as in indicator that the processing was cut short. And my best guess is RFI, as documented by the seti people in the past.

Knowing the file sizes and whats in them would certainly help in narrowing down the problem. Too bad they don't stick around for a day or so, "just in case".

Undelete for Windows - http://www.softwareshelf.com/products/display2.asp?p=58 - is one such product. Its $30, but has a free trial. Anyone with "no data transfered" workunits want to try it out?

I'm not affiliated with the company and haven't tried the product, it was just the first one I found in a Google search.

Detach and then re-attach to the project. I know what they said about the date range of the invalid work units, but all of my machines were exhibiting the same problem. Doing what I suggested above fixed the issue on all of them.

> > I've been adding my 2 cents worth of input on this very subject in the
> > "Questions and Problems" section. Some of what I have read just makes
> no
> > logical sense. This is what I get in my "Messages" tab:
> >
> > 2004-08-21 17:59:19 [SETI@home] Started upload of
> > 09se03ab.22694.5024.240896.132_5_0
> > 2004-08-21 17:59:42 [SETI@home] Finished upload of
> > 09se03ab.22694.5024.240896.132_5_0
> > 2004-08-21 17:59:42 [SETI@home] Approximate throughput 4586.049587
> bytes/sec
> >
> > The above tells me that the data was transferred.
> >
> > 2004-08-21 21:45:59 [SETI@home] Started upload of
> > 09se03ab.22694.5024.240896.73_3_0
> > 2004-08-21 21:46:05 [SETI@home] Finished upload of
> > 09se03ab.22694.5024.240896.73_3_0
> > 2004-08-21 21:46:05 [SETI@home] No data transferred
> >
> > This tells me that no data was transferred and this WU is NOT waiting in
> the
> > "Transfers" tab to be uploaded. Nor, do I have any other WUs waiting in
> the
> > "Transfers" tab.
> >
> > So, I think the real question is: If the upload starts, and the upload
> > finishes, and no data is transferred, what has happened to that data?
> Someone
> > over there said that it may have something to do with the size of the
> output
> > file getting too large and the processing stops because of it and the WU
> gets
> > uploaded. My average CPU time is 3hr 43min. I had 2 WU with the message
> "No
> > data transferred" which had the times of 03:43:18 and 03:43:25. I had
> one WU
> > that only took 00:04:39 to complete and I did NOT get the "No data
> > transferred" message. I got one like the first example above. That
> would, in
> > my opinion, blow that theory out of the water, so to speak. I wish we
> could
> > get a definitive answer on this phenomenon and not all the conjectures.
> > L8R....
> >
> >
>
> You have summed up the problem beautifully. In case anyone would like to check
> on the SETI end, I would like to add;
>
> No data transferred.
> 2004-08-21 13:55:12 13ja04aa.11634.28576.984656.43_4_0
> 2004-08-21 13:57:15 13ja04aa.11634.28576.984656.63_3_0
> 2004-08-21 16:58:03 13ja04aa.11634.28576.984656.70_3_0
> 2004-08-21 20:53:16 13ja04aa.11634.28529.273560.163_4_0
>
>
> Transfered OK.
> 2004-08-21 20:26:10 13ja04aa.11634.28576.984656.74_3_0
> 2004-08-21 17:23:39 13ja04aa.11634.28576.984656.36_4_0
>
> I'm running a 3.2 Ghz HyperThreaded chip is why some of the times are sort of
> close together.
>
>

Sorry about the double posting of this information. It comes from the message boards and sums up the problem That I have been having.

> Knowing the file sizes and whats in them would certainly help in narrowing
> down the problem. Too bad they don't stick around for a day or so, "just in
> case".

Using BoincLogX v1.05, this program saves the different log files.

This is what I got:

For normal data transfer

SETI@home - 2004-08-21 12:27:18 - Finished upload of 13ja04aa.11634.31122.61078.251_5_0
SETI@home - 2004-08-21 12:27:18 - Approximate throughput 6413.395349 bytes/sec
13ja04aa.11634.31122.61078.251.logX 21/08/2004 12:27:26 353 KB
13ja04aa.11634.31122.61078.251_5_0.logX 21/08/2004 12:13:26 10 KB
13ja04aa.11634.31122.61078.251_5_0_state.logX 21/08/2004 12:26:26 2 KB

SETI@home - 2004-08-21 12:56:29 - Finished upload of 13ja04aa.11634.31074.392322.254_3_0
SETI@home - 2004-08-21 12:56:29 - Approximate throughput 6487.829787 bytes/sec
13ja04aa.11634.31074.392322.254.logX 21/08/2004 12:56:26 353 KB
13ja04aa.11634.31074.392322.254_3_0.logX 21/08/2004 12:56:26 18 KB
13ja04aa.11634.31074.392322.254_3_0_state.logX 21/08/2004 12:55:26 2 KB

SETI@home - 2004-08-21 23:04:47 - Finished upload of 13ja04aa.11634.31169.779818.36_3_0
SETI@home - 2004-08-21 23:04:47 - Approximate throughput 7379.500000 bytes/sec
13ja04aa.11634.31169.779818.36.logX 21/08/2004 23:04:58 353 KB
13ja04aa.11634.31169.779818.36_3_0.logX 21/08/2004 21:00:26 10 KB
13ja04aa.11634.31169.779818.36_3_0_state.logX 21/08/2004 23:03:58 5 KB

SETI@home - 2004-08-22 09:38:58 - Finished upload of 13ja04aa.11634.31458.861088.223_5_0
SETI@home - 2004-08-22 09:38:58 - Approximate throughput 8332.595745 bytes/sec
13ja04aa.11634.31458.861088.223.logX 22/08/2004 9:38:58 353 KB
13ja04aa.11634.31458.861088.223_5_0.logX 22/08/2004 9:38:58 23 KB
13ja04aa.11634.31458.861088.223_5_0_state.logX 22/08/2004 9:37:58 5 KB

SETI@home - 2004-08-22 10:13:57 - Finished upload of 13ja04aa.29764.18049.842330.98_5_0
SETI@home - 2004-08-22 10:13:57 - Approximate throughput 6557.460317 bytes/sec
13ja04aa.29764.18049.842330.98.logX 22/08/2004 10:13:58 353 KB
13ja04aa.29764.18049.842330.98_5_0.logX 22/08/2004 10:13:58 18 KB
13ja04aa.29764.18049.842330.98_5_0_state.logX 22/08/2004 10:12:58 2 KB


No transfer

SETI@home - 2004-08-21 17:43:49 - Finished upload of 13ja04aa.11634.31074.392322.246_4_0
SETI@home - 2004-08-21 17:43:49 - No data transferred
13ja04aa.11634.31074.392322.246.logX 21/08/2004 17:44:28 353 KB
13ja04aa.11634.31074.392322.246_4_0.logX 21/08/2004 16:29:26 10 KB
13ja04aa.11634.31074.392322.246_4_0_state.logX 21/08/2004 17:43:26 2 KB

SETI@home - 2004-08-21 18:09:48 - Finished upload of 13ja04aa.11634.31169.779818.18_4_0
SETI@home - 2004-08-21 18:09:48 - No data transferred
13ja04aa.11634.31169.779818.18.logX 21/08/2004 18:10:26 353 KB
13ja04aa.11634.31169.779818.18_4_0.logX 21/08/2004 18:04:26 20 KB
13ja04aa.11634.31169.779818.18_4_0_state.logX 21/08/2004 18:09:26 5 KB

SETI@home - 2004-08-21 23:33:22 - Finished upload of 28au03aa.4213.12114.211072.16_3_0
SETI@home - 2004-08-21 23:33:22 - No data transferred
28au03aa.4213.12114.211072.16.0.logX missing
28au03aa.4213.12114.211072.16_3_0.logX 21/08/2004 23:27:58 15 KB
28au03aa.4213.12114.211072.16_3_0_state.logX 21/08/2004 23:32:58 5 KB

SETI@home - 2004-08-22 04:40:10 - Finished upload of 13ja04aa.29764.16976.953400.86_4_0
SETI@home - 2004-08-22 04:40:10 - No data transferred
13ja04aa.29764.16976.953400.86.logX 22/08/2004 4:40:58 363 KB
13ja04aa.29764.16976.953400.86_4_0.logX 22/08/2004 3:58:58 10 KB
13ja04aa.29764.16976.953400.86_4_0_state.logX 22/08/2004 4:39:58 5 KB

SETI@home - 2004-08-22 04:53:07 - Finished upload of 09se03ab.22694.10704.572166.156_3_0
SETI@home - 2004-08-22 04:53:07 - No data transferred
09se03ab.22694.10704.572166.156.logX 22/08/2004 4:53:58 353 KB
09se03ab.22694.10704.572166.156_3_0.logX 22/08/2004 4:29:58 10 KB
09se03ab.22694.10704.572166.156_3_0_state.logX 22/08/2004 4:52:58 5 KB

If everybody agree, I propose to continu the posting/ investigating etc. in this thread.