Pretty much.

400, 500, failure to connect and system I/O are the same cause.

If you're getting a 404 error, make sure your PROXY is either clear or using the correct authentication for your particular network setup.

O.K. is this the same type ERROR ?????

12/6/2005 1:43:06 PM|SETI@home|Started upload of 17oc03aa.12303.2464.90902.214_2_0
12/6/2005 1:44:50 PM|SETI@home|Temporarily failed upload of 17oc03aa.12303.2464.90902.214_2_0: error 400
12/6/2005 1:44:50 PM|SETI@home|Backing off 1 hours, 50 minutes, and 51 seconds on upload of file 17oc03aa.12303.2464.90902.214_2_0

Been getting this on two files for 24HRs.

---

Stewie: So, is there any tread left on the tires? Or at this point would it be like throwing a hot dog down a hallway?

Fox Sunday (US) at 9PM ET/PT

Error 500 is:

500 Internal Server Error The Server experienced an internal error and could not process the request.

Error 400 is not specifically listed, but :

403 Forbidden The server understood the request, but is refusing to fulfill it. Typically due to file access permissions on the server.
In the case oif the BOINC System, the Web Server thinks that the HTTP data stream sent by the client (e.g. a Web Browser or the BOINC Daemon) was correct, but access to the resource identified by the URL is forbidden for some reason.

This indicates a fundamental access problem, which may be difficult to resolve because the HTTP protocol allows the Web Server to give this response without providing any reason at all. So the 403 error is equivalent to a blanket 'NO' by the Server - with no further discussion allowed.

By far the most common reason for this error is that directory browsing is forbidden for the Web Site. In the case of a response to a Scheduler Request Message or an Upload/Download action is because of an error on the server-side of BOINC System.

404 Not Found Couldn't find the Web Page. The server has not found anything matching the URI/URL.

Error 500's all over the place. But .....
One result snuck through this morning! Yeah!

---

Grover says ... "Just go with the flow"

Error 500 is:

500 Internal Server Error The Server experienced an internal error and could not process the request.

Error 400 is not specifically listed, but :

403 Forbidden The server understood the request, but is refusing to fulfill it. Typically due to file access permissions on the server.
In the case oif the BOINC System, the Web Server thinks that the HTTP data stream sent by the client (e.g. a Web Browser or the BOINC Daemon) was correct, but access to the resource identified by the URL is forbidden for some reason.

This indicates a fundamental access problem, which may be difficult to resolve because the HTTP protocol allows the Web Server to give this response without providing any reason at all. So the 403 error is equivalent to a blanket 'NO' by the Server - with no further discussion allowed.

By far the most common reason for this error is that directory browsing is forbidden for the Web Site. In the case of a response to a Scheduler Request Message or an Upload/Download action is because of an error on the server-side of BOINC System.

404 Not Found Couldn't find the Web Page. The server has not found anything matching the URI/URL.

Tony
I saw this in the source code and I recall its a HTTP error code. 400 means ;
The HTTP error 400, bad request, means that the Web server received a request that it could not process, because it is not configured to do so, or because it expects certain headers or parameters in the request that are not present.

---

Took a lot of time to get this active, then all of the problems over the weekend -- and continuing for me. I upgraded from 5.2.8 to 5.2.13, and ever since have not had a successful connect. I have two results to upload, waiting since Monday morning; I have had no new work downloaded since Saturday.

Here's the last few lines where I tried to re-update SETI again on my Project tab -- it also shows "Scheduler request pending. Communication defferred 61:59:22"

12/6/2005 12:38:44||request_reschedule_cpus: project op
12/6/2005 12:38:47|SETI@home|Fetching master file
12/6/2005 12:38:51||Couldn't connect to hostname [setiathome.berkeley.edu]
12/6/2005 12:38:53|SETI@home|Master file fetch failed
12/6/2005 12:38:53|SETI@home|Too many backoffs - fetching master file
12/6/2005 14:10:17|SETI@home|Started upload of 13au01aa.6597.13170.11064.30_0_0
12/6/2005 14:10:21||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
12/6/2005 14:10:21|SETI@home|Temporarily failed upload of 13au01aa.6597.13170.11064.30_0_0: system I/O
12/6/2005 14:10:21|SETI@home|Backing off 3 hours, 16 minutes, and 47 seconds on upload of file 13au01aa.6597.13170.11064.30_0_0

Any ideas? Thanks.

---

1) 1024 Kbytes/sec. Cable
2)Cablemodem (MotorolaSB5100)
3)Running alone
4) Direct connect to the cablemodem.
5)Not sharing network
6)

A few of us are trying to track the cause of 500 errors.
It appears that it may have something to do with MTU sizes.

To get to the source of this I have several questions.

1. What type of connection do you have to your ISP?
(dial-up, DSL, Cable, Other [specify other]

2. What equipment are you using to access your ISP?
(cable modem [manufacturer, mode], DSL Modem, Other)

3. Are you running other applications that could consume bandwidth? (bit torrent, win mx, napster, etc)

4. Are you connected directly to your cable/dsl modem or is there a router or switch in line?

5. Are you willing to share a network trace with one of us?

If you don't want to answer these questions on line e-mail the answer to me at boinc@emacolet.com I set this address up on my mail server to get these answers.

Your answers and any traces you will share will be kept bewteen me, you and the developers of this project.

---

Another example of what I am seeing. Have been unable to manually upload one result for the past few days. Allowed the next result to complete and watched as its transfer was attempted, in what looked like good error handling by BONIC on this end. Cogent graphs looked, well normal for the past few days with nothing unusual happening at the time of this Message log. Note this sequence seems to support both the idea that there is a network overload within the Berkeley lab and a problem handling deferred transfers on the server.

          [i]Last rescheduled attempt at transfering result pending for two days.[/i]
12/6/2005 1:00:33 PM|SETI@home|Started upload of 15ap04aa.22158.3042.379824.13_2_0
12/6/2005 1:03:46 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.3042.379824.13_2_0: error 500
12/6/2005 1:03:46 PM|SETI@home|Backing off 2 hours, 21 minutes, and 41 seconds on upload of file 15ap04aa.22158.3042.379824.13_2_0
          [i]New result completes, first attempt fails with [color=red]system I/O[/color] error as server appears not to respond.[/i]
12/6/2005 2:17:19 PM||request_reschedule_cpus: process exited
12/6/2005 2:17:19 PM|SETI@home|Computation for result 15ap04aa.22158.6913.729802.124_3 finished
12/6/2005 2:17:19 PM|SETI@home|Starting result 21mr05ab.11361.30466.473568.153_3 using setiathome version 418
12/6/2005 2:17:22 PM|SETI@home|Started upload of 15ap04aa.22158.6913.729802.124_3_0
12/6/2005 2:17:45 PM|[color=red]|Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu][/color]
12/6/2005 2:17:45 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.6913.729802.124_3_0: system I/O
12/6/2005 2:17:45 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 15ap04aa.22158.6913.729802.124_3_0
          [i]Second attemp - Progress does not proceed beyond 0.00% but times out.[/i]
12/6/2005 2:18:46 PM|SETI@home|Started upload of 15ap04aa.22158.6913.729802.124_3_0
12/6/2005 2:21:59 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.6913.729802.124_3_0: error 500
12/6/2005 2:21:59 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 15ap04aa.22158.6913.729802.124_3_0
          [i]Third attempt - Progress does not proceed beyond 0.00% - Server does not respond.[/i]
12/6/2005 2:23:00 PM|SETI@home|Started upload of 15ap04aa.22158.6913.729802.124_3_0
12/6/2005 2:23:22 PM|[color=red]|Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu][/color]
12/6/2005 2:23:22 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.6913.729802.124_3_0: system I/O
12/6/2005 2:23:22 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 15ap04aa.22158.6913.729802.124_3_0
          [i]Forth attempt - Progress proceeds to 2.99% and times out.[/i]
12/6/2005 2:24:22 PM|SETI@home|Started upload of 15ap04aa.22158.6913.729802.124_3_0
12/6/2005 2:27:34 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.6913.729802.124_3_0: error 500
12/6/2005 2:27:34 PM|SETI@home|Backing off 1 minutes and 0 seconds on upload of file 15ap04aa.22158.6913.729802.124_3_0
          [i]Fifth attemp - Goes through but takes minute and 15 seconds to transfer?[/i]
12/6/2005 2:28:34 PM|SETI@home|Started upload of 15ap04aa.22158.6913.729802.124_3_0
12/6/2005 2:29:45 PM|SETI@home|Finished upload of 15ap04aa.22158.6913.729802.124_3_0
12/6/2005 2:29:45 PM|SETI@home|Throughput 277 bytes/sec

          [i]Scheduled transfer of older result continues to fail after proceeding to 2.86%[/i]
12/6/2005 2:30:33 PM|SETI@home|Started upload of 15ap04aa.22158.3042.379824.13_2_0
12/6/2005 2:30:54 PM|[color=red]|Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu][/color]
12/6/2005 2:30:54 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.3042.379824.13_2_0: system I/O
12/6/2005 2:30:54 PM|SETI@home|Backing off 42 minutes and 21 seconds on upload of file 15ap04aa.22158.3042.379824.13_2_0
12/6/2005 2:31:25 PM|SETI@home|Started upload of 15ap04aa.22158.3042.379824.13_2_0
12/6/2005 2:34:34 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.3042.379824.13_2_0: error 500
12/6/2005 2:34:34 PM|SETI@home|Backing off 1 hours, 2 minutes, and 58 seconds on upload of file 15ap04aa.22158.3042.379824.13_2_0

Manual attempts to transfer the older results continue to fail.

I have a two day old result that refuses to upload as well. It's strange how results of some work units will upload but others will not.

---

Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws.
Douglas Adams (1952 - 2001)

I'm starting to wonder if the 'B' in BOINC should stand for Beta. Sorry if this sounds like a rant, but I just had to vent a little. I've been on BOINC for over a year, and I've been through several of the birthing pains. It's just disappointing everytime it starts to run relatively smoothly for several weeks and then something new blows up.

I know the good folks at Berkely are working hard to isolate and correct the problem though, and I wish them Godspeed. I also hope all the newbs coming over from classic don't get too frustrated and run away.

---

http://www.setiusa.net

I'm starting to wonder if the 'B' in BOINC should stand for Beta. Sorry if this sounds like a rant, but I just had to vent a little. I've been on BOINC for over a year, and I've been through several of the birthing pains. It's just disappointing everytime it starts to run relatively smoothly for several weeks and then something new blows up.

I know the good folks at Berkely are working hard to isolate and correct the problem though, and I wish them Godspeed. I also hope all the newbs coming over from classic don't get too frustrated and run away.

I finally soved the "firewall" problem and now the server continues for 2 day without a reasonable "message" I get:

12/6/2005 2:36:15 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
12/6/2005 2:36:15 PM|SETI@home|Temporarily failed upload of 21mr05ab.11361.28785.636084.176_2_0: system I/O
12/6/2005 2:36:15 PM|SETI@home|Backing off 3 hours, 48 minutes, and 31 seconds on upload of file 21mr05ab.11361.28785.636084.176_2_0
12/6/2005 2:58:14 PM||request_reschedule_cpus: project op
12/6/2005 2:58:18 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
12/6/2005 2:58:18 PM|SETI@home|Reason: Requested by user
12/6/2005 2:58:18 PM|SETI@home|Requesting 8640 seconds of new work
12/6/2005 2:58:23 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
12/6/2005 2:58:23 PM|SETI@home|Message from server: No work sent
12/6/2005 2:58:23 PM|SETI@home|Message from server: (reached daily quota of 1 results)
12/6/2005 2:58:34 PM|SETI@home|Started upload of 21mr05ab.11361.28785.636084.176_2_0
12/6/2005 2:58:35 PM|SETI@home|Temporarily failed upload of 21mr05ab.11361.28785.636084.176_2_0: error 500
12/6/2005 2:58:35 PM|SETI@home|Backing off 3 hours, 0 minutes, and 42 seconds on upload of file 21mr05ab.11361.28785.636084.176_2_0
12/6/2005 2:58:48 PM|SETI@home|Started upload of 15ap04aa.22158.30353.236066.236_2_0

What the Hell are these CHILDREN or Students?

If this were a business they would be Chapter 11 or 7.

Dimitri

(finished ranting)

...What the Hell ...
Dimitri

Please take all rants and any unhelpful comments to the Cafe forum.

I will be very happy to explain your childishness there.

Can we keep this thread useful to HELP people please?

Regards,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

1. What type of connection do you have to your ISP? CABLE


2. What equipment are you using to access your ISP? cable modem : AMBIT, MODEL # U10C018


3. Are you running other applications that could consume bandwidth? (bit torrent, win mx, napster, etc) NO

4. Are you connected directly to your cable/dsl modem or is there a router or switch in line? DIRECTLY CONNECTED

5. Are you willing to share a network trace with one of us? YES, IF NEED BE.


6. THIS DIDN'T START UNTIL LAST WEEK AND I HAVE BEEN USING THE SAME VERSION SINCE I STARTED, VERSION 5.2.8... BELOW IS A SNIPET OF MY ERROR MESSAGES AND MY WORK WILL UPLOAD BUT IT TAKES MANY TRIES AND IT IS GETTING WORSE. I WAS ONLY 2 BEHIND BUT NOW IT HAS GROWN TO FOUR BEHIND.


12/6/2005 3:51:46 PM|SETI@home|Temporarily failed upload of 20mr05aa.6043.19073.29846.149_3_0: error 500
12/6/2005 3:51:46 PM|SETI@home|Backing off 3 hours, 43 minutes, and 41 seconds on upload of file 20mr05aa.6043.19073.29846.149_3_0
12/6/2005 3:53:46 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.8272.709636.125_3_0: error 500
12/6/2005 3:53:46 PM|SETI@home|Backing off 1 hours, 5 minutes, and 6 seconds on upload of file 15ap04aa.22158.8272.709636.125_3_0
12/6/2005 4:16:07 PM|SETI@home|Started download of 19mr05ab.16926.30001.567336.21
12/6/2005 4:16:30 PM|SETI@home|Temporarily failed download of 19mr05ab.16926.30001.567336.21: error 500
12/6/2005 4:16:30 PM|SETI@home|Backing off 1 hours, 9 minutes, and 2 seconds on download of file 19mr05ab.16926.30001.567336.21
12/6/2005 4:56:04 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
12/6/2005 4:56:04 PM|SETI@home|Reason: To report results
12/6/2005 4:56:04 PM|SETI@home|Reporting 1 results
12/6/2005 4:56:15 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
12/6/2005 4:58:04 PM|SETI@home|Started upload of 15ap04aa.22158.8272.709636.125_3_0
12/6/2005 4:58:27 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
12/6/2005 4:58:27 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.8272.709636.125_3_0: system I/O
12/6/2005 4:58:27 PM|SETI@home|Backing off 36 minutes and 53 seconds on upload of file 15ap04aa.22158.8272.709636.125_3_0
12/6/2005 5:03:20 PM||request_reschedule_cpus: project op
12/6/2005 5:03:22 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
12/6/2005 5:03:22 PM|SETI@home|Reason: Requested by user
12/6/2005 5:03:22 PM|SETI@home|Note: not requesting new work or reporting results
12/6/2005 5:03:27 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
12/6/2005 5:25:33 PM|SETI@home|Started download of 19mr05ab.16926.30001.567336.21
12/6/2005 5:26:17 PM|SETI@home|Finished download of 19mr05ab.16926.30001.567336.21
12/6/2005 5:26:17 PM|SETI@home|Throughput 8599 bytes/sec
12/6/2005 5:26:18 PM||request_reschedule_cpus: files downloaded
12/6/2005 5:26:18 PM|SETI@home|Starting result 19mr05ab.16926.30001.567336.21_1 using setiathome version 418
12/6/2005 5:30:21 PM|SETI@home|Started upload of 15ap04aa.22158.8272.709636.125_3_0
12/6/2005 5:32:33 PM|SETI@home|Started upload of 20mr05aa.6043.19073.29846.149_3_0
12/6/2005 5:33:32 PM|SETI@home|Temporarily failed upload of 15ap04aa.22158.8272.709636.125_3_0: error 500
12/6/2005 5:33:32 PM|SETI@home|Backing off 1 hours, 40 minutes, and 23 seconds on upload of file 15ap04aa.22158.8272.709636.125_3_0
12/6/2005 5:33:32 PM|SETI@home|Started upload of 13au01aa.6597.29361.642322.214_2_0
12/6/2005 5:35:44 PM|SETI@home|Temporarily failed upload of 20mr05aa.6043.19073.29846.149_3_0: error 500
12/6/2005 5:35:44 PM|SETI@home|Backing off 1 hours, 16 minutes, and 17 seconds on upload of file 20mr05aa.6043.19073.29846.149_3_0
12/6/2005 5:36:43 PM|SETI@home|Temporarily failed upload of 13au01aa.6597.29361.642322.214_2_0: error 500
12/6/2005 5:36:43 PM|SETI@home|Backing off 44 minutes and 11 seconds on upload of file 13au01aa.6597.29361.642322.214_2_0

---

1. Cable
2. Motorola SurfBoard Cable modem
3. No but i use a software personal firewall (non microsoft)
4. Connected Directly
5. See below:

OS=Win98 SE

first few hops have been removed:

4 21 ms 17 ms 26 ms h66-38-198-13.gtconnect.net [66.38.198.13]

5 13 ms 18 ms 30 ms 216.18.63.13

6 28 ms 27 ms 25 ms 66.59.191.110

7 36 ms 23 ms 27 ms 66.59.191.114

8 34 ms 50 ms 31 ms p12-0.core01.ord01.atlas.cogentco.com [154.54.2.237]

9 79 ms 91 ms 87 ms p5-0.core01.sfo01.atlas.cogentco.com [66.28.4.185]

10 89 ms 100 ms 80 ms UC-Berkeley.demarc.cogentco.com [66.250.4.74]

11 84 ms 83 ms 90 ms setiboincdata.ssl.berkeley.edu [66.28.250.125]

Error messages:

12/6/05 5:45:02 PM|SETI@home|Started upload of 17ja04aa.20660.13824.884652.135_0_0
12/6/05 5:45:51 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
12/6/05 5:45:52 PM|SETI@home|Temporarily failed upload of 17ja04aa.20660.13824.884652.135_0_0: system I/O
12/6/05 5:45:52 PM|SETI@home|Backing off 1 minutes and 45 seconds on upload of file 17ja04aa.20660.13824.884652.135_0_0
12/6/05 5:47:39 PM|SETI@home|Started upload of 17ja04aa.20660.13824.884652.135_0_0
12/6/05 5:48:28 PM|SETI@home|Temporarily failed upload of 17ja04aa.20660.13824.884652.135_0_0: error 500
12/6/05 5:48:28 PM|SETI@home|Backing off 5 minutes and 23 seconds on upload of file 17ja04aa.20660.13824.884652.135_0_0
12/6/05 5:53:52 PM|SETI@home|Started upload of 17ja04aa.20660.13824.884652.135_0_0
12/6/05 5:58:00 PM|SETI@home|Temporarily failed upload of 17ja04aa.20660.13824.884652.135_0_0: error 500
12/6/05 5:58:00 PM|SETI@home|Backing off 11 minutes and 21 seconds on upload of file 17ja04aa.20660.13824.884652.135_0_0
12/6/05 6:09:23 PM|SETI@home|Started upload of 17ja04aa.20660.13824.884652.135_0_0
12/6/05 6:10:11 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
12/6/05 6:10:11 PM|SETI@home|Temporarily failed upload of 17ja04aa.20660.13824.884652.135_0_0: system I/O
12/6/05 6:10:11 PM|SETI@home|Backing off 19 minutes and 35 seconds on upload of file 17ja04aa.20660.13824.884652.135_0_0

I upgraded to version 5.2.13 on December 4 and use an optimized client. I have had successful uploads/downloads since the upgrade with no processing errors and am attached only to SETI.

hope this helps

---

12/6/2005 2:58:23 PM|SETI@home|Message from server: (reached daily quota of 1 results)

That in your Message log suggests you have been having a lot of problems with bad results being returned. Check your Results page. And until you start returning valid results you might be limited to one result file download per day!

1. Cable
2. SurfBoard 5100
3. No
4. Linksys Router
5. See Image below if it worked.





Dusty

We now have close to 50 results from the last several days waiting to upload - all are held up by 500 errors. Periodically I see a result uploading with a reasonable data rate, but the list of pending uploads is growing faster than uploads are succeeding (and I've not tracked closely enough to notice if these do succeed, or if they end up back in the retry queue).

---

1. Cable
2. RCA/Thomson
3. No
4. WRT54G
5.
traceroute to setiboincdata.ssl.berkeley.edu (66.28.250.125), 30 hops max, 38 byte packets
4 srp10-0.gnboncsg-rtr1.triad.rr.com (24.28.224.225) 36 bytes to 192.168.1.20 62.539 ms 11.554 ms 9.665 ms
5 srp1-0.gnboncsg-rtr4.triad.rr.com (24.28.226.195) 36 bytes to 192.168.1.20 63.070 ms 15.156 ms
12.395 ms
6 son0-0-2.chrlncsa-rtr6.carolina.rr.com (24.93.64.41) 36 bytes to 192.168.1.20 62.303 ms 13.964
ms 19.736 ms
7 son0-0-1.rlghncrdc-rtr3.nc.rr.com (24.93.64.54) 36 bytes to 192.168.1.20 17.009 ms 24.93.64.18 (24.93.64.18) 36 bytes to 192.168.1.20 29.471 ms son0-0-1.rlghncrdc-rtr3.nc.rr.com (24.93.64.54) 36 bytes to 192.168.1.20 26.707 ms
8 so-9-1.car1.Washington1.Level3.net (67.29.172.9) 36 bytes to 192.168.1.20 33.229 ms so-8-1.car1.Washington1.Level3.net (67.29.172.5) 36 bytes to 192.168.1.20 25.325 ms 36.565 ms
9 ae-2-52.bbr2.Washington1.Level3.net (4.68.121.33) 36 bytes to 192.168.1.20 45.536 ms ae-1-55.bbr1.Washington1.Level3.net (4.68.121.129) 36 bytes to 192.168.1.20 25.789 ms ae-1-53.bbr1.Washington1.Level3.net (4.68.121.65) 36 bytes to 192.168.1.20 37.024 ms
10 so-7-0-0.edge2.Washington1.Level3.net (64.159.3.66) 36 bytes to 192.168.1.20 31.768 ms so-6-0-0.edge2.Washington1.Level3.net (64.159.3.62) 36 bytes to 192.168.1.20 29.422 ms so-7-0-0.edge2.Washington1.Level3.net (64.159.3.66) 36 bytes to 192.168.1.20 36.514 ms
11 cogent-level3-oc48.Washington1.Level3.net (4.68.127.10) 36 bytes to 192.168.1.20 32.820 ms 30.888 ms 37.156 ms
12 p11-0.core01.dca01.atlas.cogentco.com (154.54.2.201) 36 bytes to 192.168.1.20 32.107 ms 39.071
ms 28.453 ms
13 p4-0.core01.phl01.atlas.cogentco.com (66.28.4.18) 36 bytes to 192.168.1.20 44.207 ms 33.992 ms
39.809 ms
14 p5-0.core02.jfk02.atlas.cogentco.com (66.28.4.1) 36 bytes to 192.168.1.20 68.495 ms 241.618 ms
218.158 ms
15 p12-0.core01.mci01.atlas.cogentco.com (154.54.3.202) 36 bytes to 192.168.1.20 68.660 ms 67.365
ms 67.859 ms
16 p10-0.core02.sfo01.atlas.cogentco.com (66.28.4.209) 36 bytes to 192.168.1.20 107.438 ms 265.282 ms 253.497 ms
17 p15-0.core01.sfo01.atlas.cogentco.com (66.28.4.69) 36 bytes to 192.168.1.20 104.830 ms 104.250
ms 106.447 ms
18 UC-Berkeley.demarc.cogentco.com (66.250.4.74) 36 bytes to 192.168.1.20 105.714 ms 106.126 ms 106.267 ms
19 66.28.250.125 (66.28.250.125) 46 bytes to 192.168.1.20 107.200 ms 107.813 ms 109.157 ms

---

This supports the idea presented by Celtic Wolf that Windows and/or the BONIC software does not always see the error 500 response (what ever it actually is {NACK}?) when received, and after a three minute timeout the BONIC software "notices" the error response setting in the receive buffer.

From some of the sniffer traces I saw I am still of the mind we have 1000's of zombie sockets hanging around. I saw several instances were a FIN was sent but no FIN-ACK or the packet had a checksum error. Solaris leaves these zombie sockets open for 4 hours by default. There is a finite number of TCP sockets available. As they expire and SOlaris finally frees them up some lucky soul gets a WU uploaded.

I have suggested to them to decrease the keep_alive time and the close wait interval down to two minutes each. I also suggested that they increase the listen queue to 2048 or 4096 instead of the default 128. Even told them how..

I am still waiting on their answer.

...

I upgraded to version 5.2.13 on December 4 and use an optimized client. I have had successful uploads/downloads since the upgrade with no processing errors and am attached only to SETI.

hope this helps

First, sorry for del parts of your message,
second, I have done also an upgrade to version 5.2.13 on December 4th, but I use the normal client.
During this update I wonder, because I hit the link "upgrade to 5.2.12" and I got the version 5.2.13 ....
First this version works fine, but then: error 500 ... system I/O...
But then I saw in Transfers : 124% done /// 12.4/10.8 KB (this is not good I think)
And here is my question: Causes this version 5.2.13 (downloaded from the BOINC site) a behavior on Computers to act as Zombies ?????

---

And here is my question: Causes this version 5.2.13 (downloaded from the BOINC site) a behavior on Computers to act as Zombies ?????

No It is the sheer number of Classic participants switching to BOINC. I suspect the problem has been there for quite sometime, but with the influx of Classic people to BOINC it lept into the forefront.

I am still running 5.2.6 on my laptop. and 4.19 on one of my solaris systems and all my systems are backing up.