Panic Mode On (27) Server problems |
![]() |
| log in |
Message boards : Number crunching : Panic Mode On (27) Server problems
1 · 2 · 3 · 4 . . . 11 · Next
| Author | Message |
|---|---|
|
Hopefully this one will not fill up quite so fast. | |
| ID: 951528 · | |
|
Heemmm...I'm downloading 3 wu with very small speed. I check on my internet connection, but everything seems well, no trouble. | |
| ID: 951560 · | |
|
Bandwidth is still maxed after the outage, it will get better in a few hours. | |
| ID: 951564 · | |
|
| |
| ID: 951578 · | |
I removed the edits from my hosts file several hours ago and everything is running hunky-dory. Suggest you do the same Sutaru. F. ____________ | |
| ID: 951602 · | |
All seems well here too...... I never did any hanky-panky with the settings....tried a few reboots and Boinc restarts which worked once in a while, then just set back to wait it out. Nary a hung download on any of the 8 rigs when I got home from work about an hour ago. So it does indeed look like the coast is clear. ____________ ****** "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: 951606 · | |
|
Thank you who fiddled about iwth the download server ( not correct word fiddled) now I have got all my downloads the final few this morning all started with the wrong size then all went down. It will probably be a week until my RAC starts to climb up as I have some WCG to do, these take 10 hours with my switcheing thats 20 hrs per WU and I have 4 to do. Wish the WCG WUS could be optimised however told there was and nothing could be done. | |
| ID: 951609 · | |
Heemmm...I'm downloading 3 wu with very small speed. I check on my internet connection, but everything seems well, no trouble. Did you reboot your computer? If yes and the error still occurs, see this entry at the BOINC FAQ Service. It has another error in the title, but the trick could also help with your problem (it did with mine :-). Gruß, Gundolf ____________ Computer sind nicht alles im Leben. (Kleiner Scherz) SETI@home classic workunits 3,758 SETI@home classic CPU time 66,520 hours | |
| ID: 951624 · | |
|
Postscript to the download problems we discussed at such length in panic (26): thanks largely to all the testing and suggestions in that thread, and thanks in particular to some sleuthing by Ned, a solution has been found. Ned and I have both tested it, and it works: there should be a new version of BOINC - I guess v6.10.22 - later today, and if vader lets go again next weekend we'll be ready for (him?) (her?) (it?). | |
| ID: 951926 · | |
|
Thank you richard, should I then upgrade to the new latest version as I do not have Cuda and using 6.6.36 now? | |
| ID: 951936 · | |
Thank you richard, should I then upgrade to the new latest version as I do not have Cuda and using 6.6.36 now? It isn't out yet, so don't do anything hasty. In fact, I would leave well alone for the time being. There are other issues under investigation as well, so this is unlikely ever to become a 'recommended' release - but the fix should be in all future releases, so it will be worth upgrading to the next 'recommended' one. (But again - don't rush into anything. Wait for idiots like me to test and report back first.) But - if we do get the same failure again - next week, next month or next year - we will have a tool available that we can recommend installing when and if it's needed. | |
| ID: 951938 · | |
|
Thanks for the info Jahn and Richard =) + Master Ned | |
| ID: 951939 · | |
|
Oh no the dreaded.....12/3/2009 6:45:29 AM SETI@home Message from server: (Project has no jobs available) | |
| ID: 951958 · | |
Postscript to the download problems we discussed at such length in panic (26): thanks largely to all the testing and suggestions in that thread, and thanks in particular to some sleuthing by Ned, a solution has been found. Ned and I have both tested it, and it works: there should be a new version of BOINC - I guess v6.10.22 - later today, and if vader lets go again next weekend we'll be ready for (him?) (her?) (it?). Thanks Richard, Ned, and all the others that pitched in with the sleuthing on this one..... Although I am loath to upgrade Boinc when it is working OK, I'll keep this in mind when the next boondoggle arrives. BTW, what was the problem, and what was the fix? ____________ ****** "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: 951992 · | |
|
Just noticed that all the splitters are off both AP and MBs | |
| ID: 951995 · | |
Just noticed that all the splitters are off both AP and MBs Getting towards the end of the datasets that are currently loaded. Hopefully it's just the boyz in the lab twiddling with the knobs to get another batch ready to go. ____________ ****** "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: 951996 · | |
Postscript to the download problems we discussed at such length in panic (26): thanks largely to all the testing and suggestions in that thread, and thanks in particular to some sleuthing by Ned, a solution has been found. Ned and I have both tested it, and it works: there should be a new version of BOINC - I guess v6.10.22 - later today, and if vader lets go again next weekend we'll be ready for (him?) (her?) (it?). I was lucky. I was poking around Google, because if this was a libcurl bug it would affect anything that used libcurl. I stumbled across someone explaining a fix to libcurl that just plain felt right. It described the bug (in libcurl terms) and matched the behaviour (especially the ipconfig /displaydns results). An interesting thing to note: this is actually not a BOINC bug. The fix is in libcurl.dll. As Richard said: big points to those who helped beat through the problem while it existed. Just editing the hosts file and rebooting isn't diagnostic. ____________ | |
| ID: 951997 · | |
BTW, what was the problem, and what was the fix? http://sourceforge.net/tracker/?func=detail&atid=100976&aid=2891595&group_id=976 | |
| ID: 951998 · | |
BTW, what was the problem, and what was the fix? This particular fix is pretty low risk. BOINC tells libcurl "send this file" or "go get this file" and libcurl takes care of the details -- all of them. If there is more than one possible destination, libcurl should try all of them. If libcurl does a lookup, it shouldn't re-use the information too long, in case it changes. Both of these "features" were broken. ____________ | |
| ID: 952018 · | |
BTW, what was the problem, and what was the fix? Very good find there. However, why is that a problem on Windows but seems not to be a problem for any Linux systems? (Well, mine at least that is, some with a mix of most recent to quite old versions of libcurl?) Happy crunchin', Martin ____________ Mandriva Linux A user friendly OS! See new freedom Mageia2 The Future is what We make IT (GPLv3) | |
| ID: 952032 · | |
Message boards : Number crunching : Panic Mode On (27) Server problems
| Copyright © 2013 University of California |