One of my units failed with this error.
Long time no see.

</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>22jl08aa.7244.207012.438086664195.12.53_4_0</file_name>
<error_code>-131</error_code>
</file_xfer_error>

I've got 3 of those too. Every host on every one of them reports the same error. One has already reached "too many errors" status and the others will soon.

If I had time, I'd remote into my machine and abort any more of that series that it may have.

Specifically, abort any WUs that have a 411KB datapak size, instead of the normal 367KB (as discussed earlier in this thread).

That's worth doing, because the error happens at the end of processing, so a lot of time and power is wasted.

I'm having download issues:

13-12-2013 17:25:30 | SETI@home | [error] MD5 check failed for ap_02no13aa_B2_P0_00300_20131212_14449.wu
13-12-2013 17:25:30 | SETI@home | [error] expected 7534b6a53c1d19a55c5f7bc3e428a54c, got 50a4ec6e1c6df9bb1590e3e2c446d805
13-12-2013 17:25:30 | SETI@home | [error] Checksum or signature error for ap_02no13aa_B2_P0_00300_20131212_14449.wu

Never seen that before. Related to the upload issues ?

EDIT: looks like I'm not the only one having issues with this file:

http://setiathome.berkeley.edu/workunit.php?wuid=1377309002

Tom

---

I'm having download issues:

13-12-2013 17:25:30 | SETI@home | [error] MD5 check failed for ap_02no13aa_B2_P0_00300_20131212_14449.wu
13-12-2013 17:25:30 | SETI@home | [error] expected 7534b6a53c1d19a55c5f7bc3e428a54c, got 50a4ec6e1c6df9bb1590e3e2c446d805
13-12-2013 17:25:30 | SETI@home | [error] Checksum or signature error for ap_02no13aa_B2_P0_00300_20131212_14449.wu

Never seen that before. Related to the upload issues ?

EDIT: looks like I'm not the only one having issues with this file:

http://setiathome.berkeley.edu/workunit.php?wuid=1377309002

Tom

I had 3 failed downloads about 2 hours ago, but things seem to have been OK since then.

EDIT...And one more just 10 minutes ago.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Looks like the problem with georgem, still shows up from time to time. I just got this one:

Samsung-Laptop

SETI@home 2013-12-14 15:39 Sending scheduler request: To fetch work.
SETI@home 2013-12-14 15:39 Requesting new tasks for CPU
SETI@home 2013-12-14 15:39 Scheduler request completed: got 1 new tasks
SETI@home 2013-12-14 15:39 Started download of ap_02dc13ac_B5_P1_00219_20131212_17429.wu
SETI@home 2013-12-14 15:39 Giving up on download of ap_02dc13ac_B5_P1_00219_20131212_17429.wu: file not found

Won't be around much longer - there were a couple after you, but no more ;)

http://setiathome.berkeley.edu/workunit.php?wuid=1377309023

One of my units failed with this error.
Long time no see.

</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>22jl08aa.7244.207012.438086664195.12.53_4_0</file_name>
<error_code>-131</error_code>
</file_xfer_error>

I've got 3 of those too. Every host on every one of them reports the same error. One has already reached "too many errors" status and the others will soon.

If I had time, I'd remote into my machine and abort any more of that series that it may have.

Specifically, abort any WUs that have a 411KB datapak size, instead of the normal 367KB (as discussed earlier in this thread).

That's worth doing, because the error happens at the end of processing, so a lot of time and power is wasted.

It appears I caught one of these overnight, WU #1375646975. It came and went while I was sleeping, so no chance to do anything about it. It also looks like it'll be sent out to a couple more unsuspecting hosts before it finally dies.

One of my units failed with this error.
Long time no see.

</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>22jl08aa.7244.207012.438086664195.12.53_4_0</file_name>
<error_code>-131</error_code>
</file_xfer_error>

I've got 3 of those too. Every host on every one of them reports the same error. One has already reached "too many errors" status and the others will soon.

If I had time, I'd remote into my machine and abort any more of that series that it may have.

Specifically, abort any WUs that have a 411KB datapak size, instead of the normal 367KB (as discussed earlier in this thread).

That's worth doing, because the error happens at the end of processing, so a lot of time and power is wasted.

It appears I caught one of these overnight, WU #1375646975. It came and went while I was sleeping, so no chance to do anything about it. It also looks like it'll be sent out to a couple more unsuspecting hosts before it finally dies.

Just found another one lurking on a different machine, WU #1375888293. It only arrived about an hour ago, so I aborted it and it looks like it won't be resent, although it's still "In progress" on one unlucky host.

More problems brewing?
Aother stuck tape? Result creation rate has dropped off, ready-to-send buffer is OK, but showing signs of being affected.
Also the AP Awaiting Validation & assimilator queues are backing up.
Also noticed a lot more database queries per seconbd than usual over the last few feeks. Usually it's less than 1,000 with a couple of spkies over 1,000 each day. Last week it was around 1,500 as a minimum for most of the week. Even now it's running around 1,000 with spikes up to 3,000.

---

Grant
Darwin NT

What is: <error_code>-131</error_code>

I get few WU crunched and at the end exit with this error.

---

What is: <error_code>-131</error_code>

With the crash of the sever there were a batch of WUs that are around 416kB in size instead of the usual 367kB (or so) in size. That's the error that results when they are processed & you try to report them.

Just had a look in my data directory & noticed a bunch that are 22kB in size.

---

Grant
Darwin NT

What is: <error_code>-131</error_code>

With the crash of the sever there were a batch of WUs that are around 416kB in size instead of the usual 367kB (or so) in size. That's the error that results when they are processed & you try to report them.

Just had a look in my data directory & noticed a bunch that are 22kB in size.

Thanks for the info.

Anything to worry about beside the loose of processing time? If they are with the wrong size and will end on a error i imagine is easy to clear them at the server side or not?

---

What is: <error_code>-131</error_code>

With the crash of the sever there were a batch of WUs that are around 416kB in size instead of the usual 367kB (or so) in size. That's the error that results when they are processed & you try to report them.

Just had a look in my data directory & noticed a bunch that are 22kB in size.

The small ones are normally (but check) ones which end with a double underscore: _n_0

Those are the results you're crunching ready to send back to the server. Don't delete them, whatever you do!

Just had a look in my data directory & noticed a bunch that are 22kB in size.

Take a look at those small files again Grant, the appear to be additional files attached to a vlar with a vlar_1_0 suffix on them. They have the same name as the vlar.
I have no idea what that means however?

edit::I see you answered my question Richard. Thanks for that info.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Aother stuck tape?

Actually, I think 20jn12ac might finally be unstuck, after all these months. I just noticed a task from that file just arrived on one of my machines.

edit::I see you answered my question Richard. Thanks for that info.

Yep, thanks Richard.

---

Grant
Darwin NT

Aother stuck tape?

Actually, I think 20jn12ac might finally be unstuck, after all these months. I just noticed a task from that file just arrived on one of my machines.

It'll be interesting to see if 20jn12ac actually finishes this time without causing the bad effect like it has many times before.

Cheers.

Pretty impressive shape of the throughput on the cricket graph. 560mbit for..approaching 30 continuous hours now.

---

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

Aother stuck tape?

Actually, I think 20jn12ac might finally be unstuck, after all these months. I just noticed a task from that file just arrived on one of my machines.

It'll be interesting to see if 20jn12ac actually finishes this time without causing the bad effect like it has many times before.

Cheers.

It certainly does look like its stuck again, on the last channel. Perhaps they need to shoot it and put it out of it's misery. However, the tasks I did receive from that file seem to process okay. I just finished 3 on one machine, WU #s 1378744682, 1378744651, and 1378744673, without any problems, so I guess the data's okay, if the splitter can just dig it out. I've also got 2 in the queue on another machine, but they probably won't run until tomorrow.

Hi !

Four days ago. my modem stopped to function. I called the internet server (Bell Canada) and they sent me a new one. Since I restart the connexion with Seti, it seems that I can not send you the results of the works. Plus, Seti give me a new user number. I spoke with Bell Canada (Server service) and my internet connexion is OK. But having completed 10 works for you and nothing has been transferred for validation. The forums access are functioning properly.

Please, I need suggestions...

Thank you.

---

Hi !

Four days ago. my modem stopped to function. I called the internet server (Bell Canada) and they sent me a new one. Since I restart the connexion with Seti, it seems that I can not send you the results of the works. Plus, Seti give me a new user number. I spoke with Bell Canada (Server service) and my internet connexion is OK. But having completed 10 works for you and nothing has been transferred for validation. The forums access are functioning properly.

Please, I need suggestions...

Thank you.

Disable the internal firewall of the modem to see what happen.

Tim

---

If you have a new modem this will not influence BOINC.

At least a reboot of the PC and the new modem should work with the PC (maybe - after successful detection/installation of driver).

If you open the BOINC Manager/tab 'Transfers', there are deferred results ready for upload?
Select the results and press 'retry' or something similar (I use an other Manager).

If this won't resolve your problem, please write a message again.

* Best regards! :-) * Philip J. Fry, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *

---