Panic Mode On (77) Server Problems? |
![]() |
| log in |
Message boards : Number crunching : Panic Mode On (77) Server Problems?
Previous · 1 . . . 15 · 16 · 17 · 18 · 19 · 20 · 21 . . . 23 · Next
| Author | Message |
|---|---|
Batten the hatches folks. Smooth sailing is over. AP's are being split again. Expect lots of complaints about slow downloads, no new tasks, can't report, slow uploads, no more coffee, bad times in general. :-) Dunno...if few were asking for AP work, I would expect the server status page to show some AP ready to send being built up and I don't see that happening yet either. ____________ ****** "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: 1295644 · | |
Batten the hatches folks. Smooth sailing is over. AP's are being split again. Expect lots of complaints about slow downloads, no new tasks, can't report, slow uploads, no more coffee, bad times in general. :-) Hmm, AP's disappeared from splitting again. Better just wait and see what happens. ____________ /The grumpy old Swede. "I'm so old, that 98% of all trees in the forest, are younger than I am" | |
| ID: 1295646 · | |
Batten the hatches folks. Smooth sailing is over. AP's are being split again. Expect lots of complaints about slow downloads, no new tasks, can't report, slow uploads, no more coffee, bad times in general. :-) Something odd there. Usually AP datasets take a long time to split and send. I suspect little AP work was generated from these few. ____________ ****** "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: 1295649 · | |
I reckon if anyone doesn't have enough work then the problem is on their end. Gah! Finally realised that my disk usage was 1.5 GB, hitting the limit; upped it to 10 GB and jobs started flowing... Turns out that when I was playing with BOINC versions in August I'd screwed up and "lost" 3000 WUs, which were reported as errors but not deleted from my project area! ____________ | |
| ID: 1295675 · | |
|
I just spotted that all the multibeam splitter`s are disabled | |
| ID: 1296340 · | |
|
Still ~ 19,000 MB WUs available for D/L .. ;-) | |
| ID: 1296351 · | |
|
Zero WU RTS | |
| ID: 1296360 · | |
|
Eric was dealing with the problem that led to new WU numbering scheme | |
| ID: 1296371 · | |
Eric was dealing with the problem that led to new WU numbering scheme Does that mean that we have to redo 2 weeks of WU's? If that's the case I'll consider the first run to be just a test run. Either that, or I'll have to start crying :-) ____________ /The grumpy old Swede. "I'm so old, that 98% of all trees in the forest, are younger than I am" | |
| ID: 1296381 · | |
|
Not complaining nor panic.. but my RAC has dropped in half due to no APs. Might be a good thing though. I knew when I stole my PSU from another machine that the squealing/chirping that was intermittently coming from the capacitors meant that it wouldn't have too terribly long to live. It is still alive, but my board has been beeping some error alert for 30 seconds every 6-8 hours and I'm not sure why, but it probably has something to do with some voltage being below a threshold. | |
| ID: 1296423 · | |
|
Excerpts from another thread: ...I noticed a number of new units I am receiving have unusually long names, as in: Now Eric is "dealing with the problem that led to new WU numbering scheme" that came from a "compiler bug, messing up the splitter code". Based on all the above, I wonder if it would help Eric to send a BOINC Notice asking those of us who feel comfortable with manual manipulation of our caches to suspend until further notice all cached WUs with the apparently erroneous "longnames"? | |
| ID: 1296448 · | |
Now Eric is "dealing with the problem that led to new WU numbering scheme" that came from a "compiler bug, messing up the splitter code". No, no need to do anything like that. Eric dealt with the long names in passing, while working on testing for the new v7 application at SETI Beta. Here's what he said: That huge number is supposed to be the ID of the receiver we used, which is obtained from a library routine. I'm guessing that at some point the library was compiled with a version of g++ that doesn't have the same storage format for the data type used. (my emphasis) The technically minded can read the gory details from beta message 44104 onwards. | |
| ID: 1296471 · | |
|
| |
| ID: 1296480 · | |
|
Why is it there are 6 AP splitters and only 5 MB splitters? AP gets split faster than MB anyway, so it seems to me it would make more sense to have more MB splitters than APs. Could lando run a couple more MBs, especially since he's not running his APs right now? | |
| ID: 1296526 · | |
Why is it there are 6 AP splitters and only 5 MB splitters? AP gets split faster than MB anyway, so it seems to me it would make more sense to have more MB splitters than APs. Could lando run a couple more MBs, especially since he's not running his APs right now? Sometimes it's every 10 minutes and sometimes every 20... Last update 15:00. ____________ ****** "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: 1296543 · | |
|
| |
| ID: 1296997 · | |
|
| |
| ID: 1297343 · | |
|
Hay man what happend. | |
| ID: 1298419 · | |
|
Project is temporarily shut down for maintenance .. and then .. Scheduler request failed: Couldn't connect to server
Scheduler request failed: HTTP internal server error
Scheduler request failed: Timeout was reached * Best regards! :-) * Sutaru Tsureku, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. * ____________ >Das Deutsche Cafe. The German Cafe.< | |
| ID: 1298424 · | |
|
Things have been working well here since the servers come back online (approx. 90mins now). | |
| ID: 1298435 · | |
Message boards : Number crunching : Panic Mode On (77) Server Problems?
| Copyright © 2013 University of California |