Problems with SETI / Boinc Not running two units at once sometimes
Message boards :
Number crunching :
Problems with SETI / Boinc Not running two units at once sometimes
Message board moderation
| Author | Message |
|---|---|
 -= Vyper =-  Send message Joined: 5 Sep 99 Posts: 1652 Credit: 1,065,191,981 RAC: 2,537 
 |
Hi I have a annoying problem with Boinc.. I think i have seen this error before but i can't find it with search function. When Boinc/Seti finishes a WU in a dual/ht core solution it won't start to crunch a new WU and 1 core remains unused. I have changed the number of processors setting but it wont budge.. It doesn't happen all the time but often enough to make me crazy!! Someone.. //Vyper  _________________________________________________________________________ Addicted to SETI crunching! Founder of GPU Users Group ID: 145374 ·  |
|
MikeSW17 Send message Joined: 3 Apr 99 Posts: 1603 Credit: 2,700,523 RAC: 0 
|
Vyper, Can you tell us a bit more? What version of BOINC are you using? What platform? What projects are you attached to? Does it always start two processes on a re-boot? 
ID: 145384 · |
|
-= Vyper =- Send message Joined: 5 Sep 99 Posts: 1652 Credit: 1,065,191,981 RAC: 2,537
|
>Vyper, Can you tell us a bit more? >What version of BOINC are you using? What platform? >What projects are you attached to? >Does it always start two processes on a re-boot? Boinc 4.45, used to have Boinc 4.25 and it was the same. Using optimised clients on both Boinc and Seti. Only SETI@HOME attached And it starts with two processes on reboot.. If i use PAUSE and followed by RESUME it starts up again with Two WU's P.S It just happened again.. It became finished with a WU and didn't start a new one. D.S _________________________________________________________________________ Addicted to SETI crunching! Founder of GPU Users Group ID: 145388 · |
|
-= Vyper =- Send message Joined: 5 Sep 99 Posts: 1652 Credit: 1,065,191,981 RAC: 2,537
|
Hmm I may have found it myself, this time i didn't let Boincmgr to be connected to localhost so it can't monitor the boinc.exe app.. That could've been the trick, i don't know now for sure. //Vyper _________________________________________________________________________ Addicted to SETI crunching! Founder of GPU Users Group ID: 145392 · |
tekwyzrd  Send message Joined: 21 Nov 01 Posts: 767 Credit: 30,009 RAC: 0 
|
I had that happen on a regular basis on my dual p3 when running v4.45 but haven't noticed it happen since installing v4.72 Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws. Douglas Adams (1952 - 2001) ID: 145443 · |
|
belldandy from pleiades Send message Joined: 24 Oct 02 Posts: 4 Credit: 81,580 RAC: 0 
|
Also happened to me occassionaly. Sometimes only one core is working even there are more workunits in the queue. No need to reboot though, restarting the boinc.exe seems to work. CPU: P4 2.8Ghz HT BOINC version: 4.45 Seti client: the optimized one version 4.11 bell-chan ID: 145711 · |
|
-= Vyper =- Send message Joined: 5 Sep 99 Posts: 1652 Credit: 1,065,191,981 RAC: 2,537
|
It seems to work if i install BOINC as a Service and doesn't run boincmgr.exe, That exe seem to take control over boinc.exe that starts as a service and sometimes hinders boinc.exe to run 2 units at the same time. I can be wrong though, but it seem to work for me.. //Vyper _________________________________________________________________________ Addicted to SETI crunching! Founder of GPU Users Group ID: 146129 · |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.