My Uploads to Seti Beta are failing, No problem with the Main project:

26/02/2013 22:19:22 | SETI@home Beta Test | Started upload of 12mr10ac.28308.1703.206158430212.14.224_0_0
26/02/2013 22:19:22 | SETI@home Beta Test | Started upload of 12mr10ac.28308.1703.206158430212.14.157_1_0
26/02/2013 22:19:22 | SETI@home Beta Test | Started upload of 12mr10ac.28308.1703.206158430212.14.64_0_0
26/02/2013 22:19:22 | SETI@home Beta Test | Started upload of 12mr10ac.28308.1703.206158430212.14.191_1_0
26/02/2013 22:19:22 | SETI@home Beta Test | Started upload of 12mr10ac.28308.1703.206158430212.14.172_1_0
26/02/2013 22:19:27 | SETI@home Beta Test | Temporarily failed upload of 12mr10ac.28308.1703.206158430212.14.224_0_0: transient HTTP error
26/02/2013 22:19:27 | SETI@home Beta Test | Backing off 5 hr 9 min 33 sec on upload of 12mr10ac.28308.1703.206158430212.14.224_0_0
26/02/2013 22:19:28 | SETI@home Beta Test | Temporarily failed upload of 12mr10ac.28308.1703.206158430212.14.64_0_0: transient HTTP error
26/02/2013 22:19:28 | SETI@home Beta Test | Backing off 3 hr 55 min 56 sec on upload of 12mr10ac.28308.1703.206158430212.14.64_0_0
26/02/2013 22:19:28 | SETI@home Beta Test | Temporarily failed upload of 12mr10ac.28308.1703.206158430212.14.191_1_0: transient HTTP error
26/02/2013 22:19:28 | SETI@home Beta Test | Backing off 5 hr 57 min 37 sec on upload of 12mr10ac.28308.1703.206158430212.14.191_1_0
26/02/2013 22:19:28 | SETI@home Beta Test | Temporarily failed upload of 12mr10ac.28308.1703.206158430212.14.172_1_0: transient HTTP error
26/02/2013 22:19:28 | SETI@home Beta Test | Backing off 4 hr 44 min 1 sec on upload of 12mr10ac.28308.1703.206158430212.14.172_1_0
26/02/2013 22:19:31 | SETI@home Beta Test | Temporarily failed upload of 12mr10ac.28308.1703.206158430212.14.157_1_0: transient HTTP error
26/02/2013 22:19:31 | SETI@home Beta Test | Backing off 3 hr 3 min 31 sec on upload of 12mr10ac.28308.1703.206158430212.14.157_1_0

Claggy

Mine too:

2013-02-26 17:47:53		[http_debug] [ID#200] Info:  About to connect() to setiboincdata.ssl.berkeley.edu port 80 (#0)
2013-02-26 17:47:53		[http_debug] [ID#200] Info:    Trying 208.68.240.16... 
2013-02-26 17:47:54		[http_debug] [ID#200] Info:  Connected to setiboincdata.ssl.berkeley.edu (208.68.240.16) port 80 (#0)
2013-02-26 17:47:54		[http_debug] [ID#200] Sent header to server: POST /beta_cgi/file_upload_handler HTTP/1.1
2013-02-26 17:47:54		[http_debug] [ID#200] Sent header to server: User-Agent: BOINC client (windows_intelx86 6.10.58)
2013-02-26 17:47:54		[http_debug] [ID#200] Sent header to server: Host: setiboincdata.ssl.berkeley.edu
2013-02-26 17:47:54		[http_debug] [ID#200] Sent header to server: Accept: */*
2013-02-26 17:47:54		[http_debug] [ID#200] Sent header to server: Accept-Encoding: deflate, gzip
2013-02-26 17:47:54		[http_debug] [ID#200] Sent header to server: Content-Type: application/x-www-form-urlencoded
2013-02-26 17:47:54		[http_debug] [ID#200] Sent header to server: Content-Length: 296
2013-02-26 17:47:54		[http_debug] [ID#200] Sent header to server: 
2013-02-26 17:47:58		[http_debug] [ID#200] Received header from server: HTTP/1.1 500 Internal Server Error

                                                                  Joe

Yes, mine too. There was an hour or so, on Monday when the uploads to Beta failed too, while still working fine on Main. I'll suspend Beta until uploading works again.

Still doesn't work to upload to Beta. No problems on main.

same for everyone. If you look at the server status page everything is disabled... Been so ever since just a few hours after the weekend outage

same for everyone. If you look at the server status page everything is disabled... Been so ever since just a few hours after the weekend outage

On Beta's Server status page, most have been in a disabled state for months, if not years. The only green stuff there usually is the splitters and data-driven web pages. Everything else is usually in a disabled or not running state. No matter if stuff works or not.

Beta's Servers status page, is not in any way as reliable as the SSP on main, and it does almost never reflect the true states of various processes and servers. Just keep looking at it when uploading starts working again, I bet the upload/download server will still be seen as disabled. As it has been for months if not years.

Not sure if this is related but I've run some diagnostics suggested for a previous outage, and I'm unable to trace route to boinc2.ssl.berkeley.edu - 208.68.240.18

>tracert 208.68.240.18

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.18]
over a maximum of 30 hops:

4 5 ms 5 ms 5 ms 194.75.217.221
5 6 ms 7 ms 8 ms core2-gig0-2-0-4.ilford.ukcore.bt.net [194.74.16.111]
6 6 ms 6 ms 6 ms peer1-xe0-1-0.telehouse.ukcore.bt.net [109.159.254.132]
7 6 ms 11 ms 6 ms 10gigabitethernet1-1.core1.lon1.he.net [195.66.224.21]
8 78 ms 75 ms 74 ms 10gigabitethernet7-4.core1.nyc4.he.net [72.52.92.241]
9 92 ms 98 ms 99 ms 10gigabitethernet8-3.core1.chi1.he.net [72.52.92.178]
10 144 ms 145 ms 150 ms 10gigabitethernet9-1.core1.pao1.he.net [184.105.222.173]
11 145 ms 145 ms 145 ms 64.71.140.42
12 187 ms 191 ms * 208.68.243.254
13 * * * Request timed out.
14 * * * Request timed out.

208.68.240.13, 208.68.240.16 and 208.68.240.20 all fine.

208.68.240.18 is - was - a download server, not an upload server.

Matt swapped some servers round last October (Technical News 'Hot Day') - the new alternate 'round robin' download server is 208.68.240.21

208.68.240.18 is - was - a download server, not an upload server.

Matt swapped some servers round last October (Technical News 'Hot Day') - the new alternate 'round robin' download server is 208.68.240.21

But it would be nice to get some news about this issue. If it is intentional, or some problem. I have tons of tasks to upload, and hundreds still to crunch. If the project doesn't want them, I would like to know, so I can abort them, and concentrate my resources on main 100%.

It's been days now, since it was possible to upload anything to Beta.

I've informed Eric in a sidenote of an email concerned with a completely different issue.

I'll notify him more directly if that doesn't get a reaction.

edit: you can post to the tech boards without RAC or credit, but not to the Cafe :D

I think he noted your sitenote. Uploads seem to be working again.

Tom

I've informed Eric in a sidenote of an email concerned with a completely different issue.

I'll notify him more directly if that doesn't get a reaction.

edit: you can post to the tech boards without RAC or credit, but not to the Cafe :D

I think he noted your sitenote. Uploads seem to be working again.

Tom

I've informed Eric in a sidenote of an email concerned with a completely different issue.

I'll notify him more directly if that doesn't get a reaction.

edit: you can post to the tech boards without RAC or credit, but not to the Cafe :D

Well, it's sort of working at least. Lots of dropped connections, so uploading all my tasks will take a long time. Abuse of the "Retry Now" button is a must.

Well, that didn't last long. Uploading in Beta is once again dead in the water.

Always ends with HTTP error.

Ex:

SETI@home Beta Test 2013-02-28 22:01:00 Temporarily failed upload of 12mr10ac.24752.2930.206158430212.14.146_1_0: HTTP error

I'm not having UPLOAD issues, but the downloads are taking an e x t r e a m l y long time, and the bandwidth is very low. I am getting from other projects just fine and streaming video at will....
Are your servers overloaded?

---

Space, the final frontier.
For us at least. If this thing works, then we might be eaten, or get a chance to roam the universe.

I'm not having UPLOAD issues, but the downloads are taking an e x t r e a m l y long time, and the bandwidth is very low. I am getting from other projects just fine and streaming video at will....
Are your servers overloaded?

No, the servers aren't especially overloaded, But the download link is, and has been for several years,

For a improvement in download reliability, go and read and implement the fix reported in the 'Windows TCP Settings - Follow up - Help with server communication' thread on the Main project.

Claggy

I did the TCP follow up a few days ago although downloads still slow at least they are not stalling as often and they do restart. Both laptop 64 bit and this host 32 bit.

thanks to the link.

Michael

I'm not having UPLOAD issues, but the downloads are taking an e x t r e a m l y long time, and the bandwidth is very low. I am getting from other projects just fine and streaming video at will....
Are your servers overloaded?

No, the servers aren't especially overloaded, But the download link is, and has been for several years,

For a improvement in download reliability, go and read and implement the fix reported in the 'Windows TCP Settings - Follow up - Help with server communication' thread on the Main project.

Claggy

made link clickable. I'm wondering if with the fix being deployed over the high impact hosts, the others are being outcompeted.

NB Beta shares the link with SETI Main, so any congestion there will impact here. At least Beta rarely runs out of tasks during active testing :D