Out of the fire and into the pit of sulfuric acid. (Feb 19, 2010) |
![]() |
| log in |
Message boards : Technical News : Out of the fire and into the pit of sulfuric acid. (Feb 19, 2010)
Previous · 1 . . . 9 · 10 · 11 · 12 · 13 · 14 · 15 · Next
| Author | Message |
|---|---|
|
Yes, I say again, WELL DONE!!! Bet we are really hammering the servers, hope we don't break anything else! :-) | |
| ID: 973302 · | |
|
Have any of the path-pingers retried their packet loss counters | |
| ID: 973304 · | |
Yes, I say again, WELL DONE!!! Bet we are really hammering the servers, hope we don't break anything else! :-) Yes, I agree. I still have 33 WUs, to upload, on my Windoze box. I'm hoping they can get here and get reported before all the "hammering" does indeed break something. ;) Keep on BOINCing...! :) ____________ CMDR Siran d'Vel'nahr XO USS Vre'kasht NCC-33187 Siran's website: [ ONLINE! ] | |
| ID: 973305 · | |
Have any of the path-pingers retried their packet loss counters I wrote and scheduled a script that has been tracking pathping stats every hour since 2010-02-20 16:00 UTC. I may let it run through 2010-03-09 to get a feel for "normal". ____________ | |
| ID: 973308 · | |
|
Poor Upload servers, they are getting a right hammering! | |
| ID: 973315 · | |
|
Interesting. WHile you lot were frozen out I was getting downloads on cue as WUs finished. Just the upload and reporting were a problem. Not now though, all gone :D | |
| ID: 973325 · | |
Have any of the path-pingers retried their packet loss countersOK, from Albuquerque, NM, during peak about four hours after the Cricket graphs rose to 90+ Mbits/sec 16/ 100 = 16% |
12 107ms 18/ 100 = 18% 2/ 100 = 2% 208.68.243.254
0/ 100 = 0% |
13 107ms 16/ 100 = 16% 0/ 100 = 0% setiboincdata.ssl.berkeley.edu [208.68.240.16] looks somewhat higher on this snapshot than during the outage. ____________ | |
| ID: 973351 · | |
Have any of the path-pingers retried their packet loss counters I hope the put off the backup or just cancel it all togather this week. they have postponed a backup a day before, and that was a shorter outage. ____________ | |
| ID: 973416 · | |
Have any of the path-pingers retried their packet loss counters The last time they skipped it things were pretty ugly by the following week. ____________ | |
| ID: 973459 · | |
|
I have two 'zones' running SETI, at home and office | |
| ID: 973474 · | |
I have two 'zones' running SETI, at home and office No - I think you'll find that your home machine hasn't even tested the network to SETI recently. This sounds like one of the recent features in BOINC has kicked in: if network congestion were really to have been the problem, there would be no point in adding to that congestion by continually retrying. The trouble is, no-one has thought of a way of getting the message "It's OK, the congested has cleared, you can retry now" through to a client which isn't retrying.... Just for your own information, have a look at the Messages tab in BOINC Manager to see if the home machine has even tried recently: and then go to the Projects tab, select SETI@home, and click the Properties button. I expect you'll see some high values for backoff times. Just click 'Update' once. That'll start BOINC communicating again: now that the backlog has cleared, your finished tasks should be reported at the first attempt, and you should get new work within a few minutes - there's not much available at the moment, but new work is being created continuously. | |
| ID: 973482 · | |
Have any of the path-pingers retried their packet loss countersOK, from Albuquerque, NM, during peak about four hours after the Cricket graphs rose to 90+ Mbits/sec Measuring again well within the first hour after the cricket graph dropped well down from the long high stable value: 0/ 100 = 0% |
12 54ms 0/ 100 = 0% 0/ 100 = 0% 208.68.243.254
1/ 100 = 1% |
13 53ms 1/ 100 = 1% 0/ 100 = 0% setiboincdata.ssl.berkeley.edu [208.68.240.16] so it may be that in some sense this signature is one of overload--but not of the primary problem of recent times. ____________ | |
| ID: 973508 · | |
|
The Cricket graph shows that Sunday night, 2010-02-21 from 22:00 to 22:30 PST there was very little activity on the network. The Berkeley router was still dropping packets at about 6%. Today, 2010-02-23 at 5:20 PST Cricket shows activity at 30+ yet there was 0% packet loss. | |
| ID: 973578 · | |
|
Did run 2 pathpings, one from my laptop, which showed no difference. | |
| ID: 973583 · | |
The Cricket graph shows that Sunday night, 2010-02-21 from 22:00 to 22:30 PST there was very little activity on the network. The Berkeley router was still dropping packets at about 6%. Today, 2010-02-23 at 5:20 PST Cricket shows activity at 30+ yet there was 0% packet loss. Either that, or the person who administers one router has pings limited, and the person who administers the other does not. ____________ | |
| ID: 973584 · | |
|
Hey, Guess what... | |
| ID: 973856 · | |
Hey, Guess what... You left out the part about staff with 8-5 monday-friday jobs who were clearly working on issues on Saturday and Sunday. ____________ | |
| ID: 973866 · | |
|
Rather than complain out there get up off of a few dollars, euros, pounds or whatever and help these folks out who day in and day out bust their chops for us. We can't be there to help them but our money can. So let's get some green stars up there and show Eric and the others that we are truly in there with them. I can think of little else that could be more help to them. S.E.T.I cannot live by computer power alone...it must have financial help as well. | |
| ID: 973910 · | |
|
Hi Ned, | |
| ID: 973929 · | |
Hi Ned, Thanks for the nice compliment. No matter how much bickering there is, we have to live with what's possible. Short staff, not much funding for new stuff, and the connection is what it is. So, BOINC is designed to tolerate problems -- and where possible, mitigate them. ... and for the most part, it works well. If you can sit back and watch when you're sure it's doing the wrong thing, you might even see that it works well. While we don't see Matt, or Eric, or Jeff saying "we're working on it" at 11:00pm on a Saturday, we can often tell that something is being done. ____________ | |
| ID: 973952 · | |
Message boards : Technical News : Out of the fire and into the pit of sulfuric acid. (Feb 19, 2010)
| Copyright © 2013 University of California |