Panic Mode On (46) Server problems |
![]() |
| log in |
Message boards : Number crunching : Panic Mode On (46) Server problems
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 . . . 12 · Next
| Author | Message |
|---|---|
Interesting thanks for the information! ____________ Traveling through space at ~67,000mph! | |
| ID: 1094939 · | |
|
Uploads have dropped to Zero, and downloads are dropping too, scheduler requests also fail, | |
| ID: 1095861 · | |
|
Whatever it was didn't last long. I just got some new work and uploaded and reported a couple. | |
| ID: 1095865 · | |
|
My uploads went through and reported too, | |
| ID: 1095867 · | |
|
Problems with the replica database, ATM its 15,047 seconds behind the master. | |
| ID: 1096722 · | |
Problems with the replica database, ATM its 15,047 seconds behind the master. That is rather normal while the replica catches up after maintenance. Six hours later and it is down to about 2500 seconds. Sometimes you might even observe the time go up for a few hours after everything comes back online. IIRC the replica recovers in about 12-24 hours after everything is brought back up. ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today! | |
| ID: 1096791 · | |
|
Oh, meow. | |
| ID: 1097047 · | |
|
Looks like the Cricket Graph has taken a nose dive. | |
| ID: 1097058 · | |
Looks like the Cricket Graph has taken a nose dive. Quoting from Lunatics: The grapevine says 'Gowron failed a drive and is hung. It will probably be 3-4 days to re-sync the RAID array, so no work until then.' | |
| ID: 1097064 · | |
|
Time to call Dyno Rod. | |
| ID: 1097068 · | |
Looks like the Cricket Graph has taken a nose dive. GRRR....and just as I got my second card back in from eVGA. Hopefully they ole' cache last one more test!....err that should be a period.... ____________ Traveling through space at ~67,000mph! | |
| ID: 1097070 · | |
|
One of my machines at home was mid downloading some tasks when everything went splat about 3:30 UTC. Then it looks like it cleared up about 5:00 UTC as the tasks finished downloading and a few more were requested and downloaded. Then again around 7:00 UTC tasks are no go for d/l. | |
| ID: 1097072 · | |
|
Yeah, I've got four APs that haven't started at all. Logs show HTTP errors starting at 0736UTC. Guess I'll suspend network comms. until it is fixed. | |
| ID: 1097073 · | |
Yeah, I've got four APs that haven't started at all. Logs show HTTP errors starting at 0736UTC. Guess I'll suspend network comms. until it is fixed. As upload/reporting is still working, for now :), you could set NNT to stop the inflow of work if it is going to be a few days to fix. ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today! | |
| ID: 1097084 · | |
Yeah, I've got four APs that haven't started at all. Logs show HTTP errors starting at 0736UTC. Guess I'll suspend network comms. until it is fixed. True, but that doesn't keep the pending downloads from retrying, filling my log up and making unnecessary connection attempts. Just easier to suspend comms. and wait for things to be fixed. ____________ Linux laptop uptime: 1484d 22h 42m Ended due to UPS failure, found 14 hours after the fact | |
| ID: 1097087 · | |
Yeah, I've got four APs that haven't started at all. Logs show HTTP errors starting at 0736UTC. Guess I'll suspend network comms. until it is fixed. Any downloads you already have assigned will quieten down by 'project backoff', and keep the log reasonably clean. For the time being, uploads seem fine (except at Beta, which is stuck on uploads too, but accepting reports). | |
| ID: 1097088 · | |
Yeah, I've got four APs that haven't started at all. Logs show HTTP errors starting at 0736UTC. Guess I'll suspend network comms. until it is fixed. Isn't the backoff only 2 hours max in the 6.10 branch? iirc we went up to 24h max on 6.12 ____________ Carola ------- I'm multilingual - I can misunderstand people in several languages! | |
| ID: 1097092 · | |
Yeah, I've got four APs that haven't started at all. Logs show HTTP errors starting at 0736UTC. Guess I'll suspend network comms. until it is fixed. Even the basic 'per task' backoff and retry always went up to a possible limit of four hours (though randomised within that range). I don't remember 'project backoff' ever being shorter, but I'll try and find when it was introduced. | |
| ID: 1097109 · | |
Looks like the Cricket Graph has taken a nose dive. Ooooohhh. Those be sour grapes. And I should add that I am only referring to the grapes themselves that are sour...LOL. Not any opinions about said grapes. Meow. ____________ ****** "Ask not, what your kitty can do for you. Ask what you can do for your kitty." As it is kitten, so shall it be done. | |
| ID: 1097120 · | |
|
The grapes that are growing on the grapevine, you mean? Yes, they are sour indeed. But don't shoot the messenger, please - only trying to help :-) | |
| ID: 1097130 · | |
Message boards : Number crunching : Panic Mode On (46) Server problems
| Copyright © 2013 University of California |