Panic Mode On (81) Server Problems? |
![]() |
| log in |
Message boards : Number crunching : Panic Mode On (81) Server Problems?
Previous · 1 . . . 6 · 7 · 8 · 9 · 10 · 11 · 12 . . . 21 · Next
| Author | Message |
|---|---|
|
Just got the first connect in about 30 hours and got some gpu tasks. I'm not using a proxy. Think it's just because of the relatively light load at this time of day and not a sign that anything has been fixed. | |
| ID: 1335155 · | |
|
My GPU-only rig has 99 in progress. My i7 has 200 in progress and a bunch of new ghost timeouts. Both made contact within the last half hour. | |
| ID: 1335164 · | |
|
I am able to upload and receive work. I cannot return the WU's though | |
| ID: 1335167 · | |
I am able to upload and receive work. I cannot return the WU's though You are lucky. I can't reach the servers today..... | |
| ID: 1335170 · | |
|
Still struggling to contact the Scheduler. "Couldn't connect to server" is the usual reply. Still. | |
| ID: 1335174 · | |
|
I keep getting: | |
| ID: 1335267 · | |
I keep getting: Looks like an expired proxy. Working OK for me. 7391 SETI@home 06/02/2013 22:06:30 Sending scheduler request: Requested by user. 7392 SETI@home 06/02/2013 22:06:30 Reporting 27 completed tasks, requesting new tasks for CPU and NVIDIA 7393 SETI@home 06/02/2013 22:07:53 Scheduler request completed: got 27 new tasks ____________ | |
| ID: 1335268 · | |
I keep getting: I get that also..then on the next try it will connect.. | |
| ID: 1335270 · | |
I keep getting: I agree that is normaly a proxy error but still nothing here: 06/02/2013 20:22:12 | SETI@home | Sending scheduler request: Requested by user. 06/02/2013 20:22:12 | SETI@home | Reporting 20 completed tasks 06/02/2013 20:22:12 | SETI@home | Requesting new tasks for CPU and NVIDIA 06/02/2013 20:22:36 | SETI@home | Scheduler request failed: Couldn't connect to server 06/02/2013 20:22:50 | | Project communication failed: attempting access to reference site 06/02/2013 20:22:54 | | Internet access OK - project servers may be temporarily down. ____________ | |
| ID: 1335271 · | |
|
2/6/2013 4:06:56 PM | SETI@home | Scheduler request failed: Failure when receiving data from the peer | |
| ID: 1335309 · | |
I suppose it's a question of scale, I run one medium cruncher here on SETI@Home 6851722 And 5 medium to slow on Seti Beta, yet have not had any problems keeping my modest caches filled. Same here for the most part. My old single-core non-GPU machine (4082448) is a "set and forget" machine. I just use BM to see what it's doing about once a week, but other than that, it uploads, reports, and downloads without any intervention and has absolutely zero problems maintaining a modest 2.5-day cache. That usually means 10-15 MBs in total. My current machine (6392429) chews through 6 APs/day and has nearly zero issues maintaining a full 10-day cache, which is 55-65 APs. It probably doesn't need babysitting, but since that is my daily driver, I like to push buttons and move things along. Aside from that, if I leave it to its own devices, it probably would end up running dry due to 18-hour project back-offs and such. ____________ Linux laptop uptime: 1484d 22h 42m Ended due to UPS failure, found 14 hours after the fact | |
| ID: 1335355 · | |
Same here for the most part. Where as for me the Scheduler is still borked. Most requests result in "Couldn't connect to server". If i'm lucky, i do get a connection before the backoffs become ridiculous. Otherwise it's hitting Retry for an hour or so to report & then get more work. ____________ Grant Darwin NT. | |
| ID: 1335382 · | |
Same here for the most part. Well after my post, I had just reported 5 completed tasks and wasn't requesting new work. After the 303-second delay, it started asking for more work on its own. Five "couldn't connect to server" failures in a row followed by getting one single AP to satisfy 83.25 seconds of work request. That AP managed to only stall/time-out twice before completion. That's about the best I've seen it be "set and forget" since I switched to something higher than 6.2.19. Two weeks ago, it took 20+ attempts to get the scheduler to respond, and after a few hours, I had nearly 20 APs trying to download. Hours of button-pushing finally got them through.. even with the assistance of a proxy. So I have definitely seen way worse, but it could still be much better. ____________ Linux laptop uptime: 1484d 22h 42m Ended due to UPS failure, found 14 hours after the fact | |
| ID: 1335405 · | |
|
I've been watching this thread for a couple days, all the while my RAC has been rising and my active machines' 12 cores (16 threads) and 1 small GPU have been busy. However as soft said, most request for work result in: | |
| ID: 1335406 · | |
I have my Boinc set for 4 days and additional .01 There are presently server side limits in place. 100 WUs per CPU & 100WUs per GPU. Which means with a bunch of shorties my GPU can go through them all in a couple of hours. ____________ Grant Darwin NT. | |
| ID: 1335419 · | |
|
None of my machines are able to report back to the servers, all requests are timing out. Is there any news from the seti staff regarding this prolonged issue? | |
| ID: 1335430 · | |
| ID: 1335434 · | |
|
It seems like the only way to get work units and report back is constant baby sitting. Hey I still need to go to work so that's where I get my break. | |
| ID: 1335437 · | |
I've played with Einstein a little, but still highly prefer to crunch exclusively for Seti. Maybe too many people thinking like me. I too am feeling something like that. I crunch exclusively for seti and the lack of information from the staff is highly disheartening. Oh well, I shall just wait. | |
| ID: 1335441 · | |
I've played with Einstein a little, but still highly prefer to crunch exclusively for Seti. Maybe too many people thinking like me. Another voice in the chorus, and another two cents in the SETI@Home swear jar. I have to push it constantly to get anything reported or new tasks, it is practically like a watched pot every time. ____________ | |
| ID: 1335451 · | |
Message boards : Number crunching : Panic Mode On (81) Server Problems?
| Copyright © 2013 University of California |