Panic Mode On (24) Server problems |
![]() |
| log in |
Message boards : Number crunching : Panic Mode On (24) Server problems
Previous · 1 . . . 5 · 6 · 7 · 8 · 9 · 10 · 11 · Next
| Author | Message |
|---|---|
|
Looking at the server status there's something amiss with the AP splitters, with none running and jobs stalled in progress. MB splitters are working, but ti would be nice to get a few APs coming out..... | |
| ID: 932872 · | |
Is there still problems with the uploads, some goes through however my latest one has not gone through since 19:08 UTC? Will wait until it does when that is the the question. Depends a lot on what you mean by "problem." In my opinion, it is only a problem when work misses the deadline because it couldn't be uploaded in time. ____________ | |
| ID: 932877 · | |
|
My Pending the way to the 600,000 are, I still can not see. | |
| ID: 933049 · | |
My Pending the way to the 600,000 are, I still can not see. The replica database is offline. Gruß, Gundolf | |
| ID: 933055 · | |
|
Replica database now back online. | |
| ID: 933069 · | |
|
Astropulse splitters producing, download bandwidth heading for saturation.... Joe | |
| ID: 933134 · | |
|
replica database retired AGAIN - very short life span, new game of guess your score. | |
| ID: 933162 · | |
|
BOINC replica database jocelyn Running | |
| ID: 933166 · | |
Which one is lying? Probably neither. The replica database is probably running as a database but not as a "replica" according to my Tasks page (i.e. it is not being kept up to date). F. [Edited] ____________ | |
| ID: 933168 · | |
|
| |
| ID: 933238 · | |
Not from this side of the globe: 14/09/2009 07:56:20 SETI@home Started upload of 25au09ab.19058.25016.7.10.249_1_0 14/09/2009 07:56:22 Project communication failed: attempting access to reference site 14/09/2009 07:56:22 SETI@home Temporarily failed upload of 25au09ab.19058.25016.7.10.249_1_0: HTTP error 14/09/2009 07:56:22 SETI@home Backing off 1 min 30 sec on upload of 25au09ab.19058.25016.7.10.249_1_0 14/09/2009 07:56:24 Internet access OK - project servers may be temporarily down. 14/09/2009 07:57:01 SETI@home Started upload of 25au09ab.19058.25016.7.10.249_1_0 14/09/2009 07:57:03 Project communication failed: attempting access to reference site 14/09/2009 07:57:03 SETI@home Temporarily failed upload of 25au09ab.19058.25016.7.10.249_1_0: HTTP error 14/09/2009 07:57:03 SETI@home Backing off 5 min 9 sec on upload of 25au09ab.19058.25016.7.10.249_1_0 F. ____________ | |
| ID: 933242 · | |
My fault. It was working well for a few hours there, untill not long after i commented on how well it had been working. Mutliple attempts at uploading before successfull have resumed here as well. ____________ Grant Darwin NT. | |
| ID: 933252 · | |
|
9/14/2009 8:19:43 AM SETI@home Started upload of 29au09aa.20757.19699.10.10.252_0_0 | |
| ID: 933284 · | |
|
| |
| ID: 933287 · | |
|
The upload problem is getting more severe. | |
| ID: 933450 · | |
|
Yes, something is really wrong. I have hundreds of finished jobs pending upload. Any connection attempt looks like this: 10:42:44.802571 IP my.ip.42902 > setiboincdata.ssl.berkeley.edu.http: S 2647950799:2647950799(0) win 5840 <mss 1460,sackOK,timestamp 47594046 0,nop,wscale 7> 10:42:44.802727 IP my.ip.42903 > setiboincdata.ssl.berkeley.edu.http: S 1789212786:1789212786(0) win 5840 <mss 1460,sackOK,timestamp 47594046 0,nop,wscale 7> 10:42:45.008852 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42902: S 3884893807:3884893807(0) ack 2647950800 win 5696 <mss 1436,sackOK,timestamp 1175400497 47594046,nop,wscale 10> 10:42:45.009103 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42903: S 3888998256:3888998256(0) ack 1789212787 win 5696 <mss 1436,sackOK,timestamp 1175400498 47594046,nop,wscale 10> 10:42:45.011758 IP my.ip.42902 > setiboincdata.ssl.berkeley.edu.http: P 1:255(254) ack 1 win 46 <nop,nop,timestamp 47594109 1175400497> 10:42:45.012778 IP my.ip.42903 > setiboincdata.ssl.berkeley.edu.http: P 1:255(254) ack 1 win 46 <nop,nop,timestamp 47594109 1175400498> 10:42:45.014820 IP my.ip.42902 > setiboincdata.ssl.berkeley.edu.http: . ack 1 win 46 <nop,nop,timestamp 47594109 1175400497> 10:42:45.014823 IP my.ip.42903 > setiboincdata.ssl.berkeley.edu.http: . ack 1 win 46 <nop,nop,timestamp 47594109 1175400498> 10:42:45.218107 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42902: . ack 255 win 7 <nop,nop,timestamp 1175400707 47594109> 10:42:45.218233 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42902: R 1:1(0) ack 255 win 7 <nop,nop,timestamp 1175400707 47594109> 10:42:45.219858 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42903: . ack 255 win 7 <nop,nop,timestamp 1175400708 47594109> 10:42:45.220233 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42903: R 1:1(0) ack 255 win 7 <nop,nop,timestamp 1175400708 47594109> 10:42:45.220731 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42903: R 3888998257:3888998257(0) win 0 10:42:45.220981 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42902: R 3884893808:3884893808(0) win 0 10:42:45.224115 IP my.ip.42902 > setiboincdata.ssl.berkeley.edu.http: P 255:542(287) ack 1 win 46 <nop,nop,timestamp 47594172 1175400707> 10:42:45.226156 IP my.ip.42903 > setiboincdata.ssl.berkeley.edu.http: P 255:542(287) ack 1 win 46 <nop,nop,timestamp 47594172 1175400708> 10:42:45.430738 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42902: R 3884893808:3884893808(0) win 0 10:42:45.432610 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42903: R 3888998257:3888998257(0) win 0 10:42:46.400563 IP my.ip.42904 > setiboincdata.ssl.berkeley.edu.http: S 2087092463:2087092463(0) win 5840 <mss 1460,sackOK,timestamp 47594525 0,nop,wscale 7> 10:42:46.400567 IP my.ip.42905 > setiboincdata.ssl.berkeley.edu.http: S 807197585:807197585(0) win 5840 <mss 1460,sackOK,timestamp 47594525 0,nop,wscale 7> 10:42:46.605942 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42904: S 3925343597:3925343597(0) ack 2087092464 win 5696 <mss 1436,sackOK,timestamp 1175402095 47594525,nop,wscale 10> 10:42:46.606941 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42905: S 3929144410:3929144410(0) ack 807197586 win 5696 <mss 1436,sackOK,timestamp 1175402095 47594525,nop,wscale 10> 10:42:46.610895 IP my.ip.42904 > setiboincdata.ssl.berkeley.edu.http: P 1:255(254) ack 1 win 46 <nop,nop,timestamp 47594588 1175402095> 10:42:46.612937 IP my.ip.42905 > setiboincdata.ssl.berkeley.edu.http: P 1:255(254) ack 1 win 46 <nop,nop,timestamp 47594588 1175402095> 10:42:46.613956 IP my.ip.42904 > setiboincdata.ssl.berkeley.edu.http: . ack 1 win 46 <nop,nop,timestamp 47594588 1175402095> 10:42:46.613960 IP my.ip.42905 > setiboincdata.ssl.berkeley.edu.http: . ack 1 win 46 <nop,nop,timestamp 47594588 1175402095> 10:42:46.817697 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42904: . ack 255 win 7 <nop,nop,timestamp 1175402306 47594588> 10:42:46.817713 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42904: R 1:1(0) ack 255 win 7 <nop,nop,timestamp 1175402306 47594588> 10:42:46.819167 IP my.ip.42904 > setiboincdata.ssl.berkeley.edu.http: P 255:542(287) ack 1 win 46 <nop,nop,timestamp 47594652 1175402306> 10:42:46.820824 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42904: R 3925343598:3925343598(0) win 0 10:42:46.820837 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42905: . ack 255 win 7 <nop,nop,timestamp 1175402308 47594588> 10:42:46.820944 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42905: R 1:1(0) ack 255 win 7 <nop,nop,timestamp 1175402308 47594588> 10:42:46.822070 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42905: R 3929144411:3929144411(0) win 0 10:42:46.834479 IP my.ip.42905 > setiboincdata.ssl.berkeley.edu.http: P 255:538(283) ack 1 win 46 <nop,nop,timestamp 47594652 1175402308> 10:42:47.026203 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42904: R 3925343598:3925343598(0) win 0 10:42:47.041319 IP setiboincdata.ssl.berkeley.edu.http > my.ip.42905: R 3929144411:3929144411(0) win 0 The TCP handshake appears to go well but then the server simply resets the connection. No FIN, no graceful disconnect. I think those Berkeley network guys need the motivation of a well placed blow torch. ;-) ____________ | |
| ID: 933475 · | |
|
Is Astropulse really to blame ?? | |
| ID: 933476 · | |
|
Maybe they forgot to upgrade all of their Cisco routers... :-) | |
| ID: 933477 · | |
Is Astropulse really to blame ?? Nope. It's some sort of issue with the upload server, hopefully just a configuration tweak is all that'll be required. ____________ Grant Darwin NT. | |
| ID: 933478 · | |
Is Astropulse really to blame ?? Or possibly a router problem: PP's information is interesting. Cisco's advisory suggests that a router reboot may be helpful: that should be a relatively easy thing to try during the maintenance outage today. | |
| ID: 933479 · | |
Message boards : Number crunching : Panic Mode On (24) Server problems
| Copyright © 2013 University of California |