| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: BOINC manager does not resume after running benchmarks |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
zxcvbob
Cruncher United States Joined: Jan 12, 2006 Post Count: 35 Status: Offline Project Badges: 
|
I have a new (to me) computer that I bought with no OS and I've been trying out different ones. Will probably settle down to dual-boot Win XPP 32-bit and Debian 64-bit Linux. I've been installing World Community Grid on each one and comparing it to the results on my old computer.
I have a GPU card but haven't installed it yet; I want to get the system stable first. The latest install was Windows XP Pro SP3, and I downloaded the BOINC client from WCG. It took off without a hitch, but I checked on it after a few hours and none of the tasks were running. Messages tab said they were suspended while running the benchmarks, but the benchmarks had finished a long time ago. I rebooted the computer and restarted the WCG... and the tasks ran for a few minutes and then stopped. Benchmarks again. I had no problems with the Linux 32-bit nor 64-bit clients. The 64bit ran for about a week and the 32 for a couple of days with no errors or stalls. Should I go to the Berkley site and download the latest client? I think they are at version 7.something and the one I just got here was version 6. Thanks, Bob |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7844 Status: Recently Active Project Badges: 
|
Please post the message log from the XP BOINC attempt. It may shed some light on your problem.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
zxcvbob
Cruncher United States Joined: Jan 12, 2006 Post Count: 35 Status: Offline Project Badges:
|
I uninstalled WCG and downloaded/installed the client from boinc.berkeley.edu It seems to be doing OK. I don't have the WCG message log, but if the version 7 client stalls I will post the messages here.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Been on the devs over clock adjusting backwards and no amount of effort getting things to resume until restarting the core client, or wait until the clock reaches the original time.
2 visible things happen: 1) the system clock reverse line is logged, resetting counters. 2) Logging stops, but maybe for benchmarking and preempting tasks. The dev believed only the logging stopped in the BOINC Manager, but found that actually the core client stops generating them and recording them to the stdoutdae.txt file. The dev believed that computing continued since the BM only shows Elapsed time, *not* CPU time. Well CPU cycle use stopped too i.e. the core client is in semi stasis, which then leads to nothing being logged :O. Remedy, if setting *system* clock back: Restart the core client [boinc.exe], by using the BM exit, stop client option [do not tick the "remember...". Benchmarks are run when time has changed at least 5 days under client 7 or client version changed. The scheduled 5 day benchmark is no longer run under v7 unless the client is restarted after a 5 day interval. But this is just a preemptive warning. Could be something entirely different. The message log posted from the noted stdoutdae.txt file could tell us more. |
||
|
|
zxcvbob
Cruncher United States Joined: Jan 12, 2006 Post Count: 35 Status: Offline Project Badges:
|
Rob hit it on the head. I was coming back here to report that I think I got it all figured out and saw his post. I have a couple of clock-related problems:
I found a program on the 'Net that syncs the Windows clock to the hardware RTC every 5 minutes to take care of the missed interrupts -- it assumes the RTC is accurate. When had that agent running, every 5 minutes the clock would jump backwards and Boinc hates that. Until this I thought the RTC was just running slow, but it's not running at all. Oh well. I got rid of that pgm. I changed the windows registry key* that sets the NTP client interval to resync the Windows clock to a time server every 60 minutes (instead of every week!) Now all seems well. I didn't have any of these troubles running Linux on the same hardware, but the bad RTC gave me problems on the first boot after an install (of the OS) because the file system timestamp would be in the future relative to the hardware clock. This may cause a problem every time I boot Linux when it has been more than 24 hours since I set the clock in the BIOS, I don't know. I replaced the 2032 lithium battery with a new one and that didn't help. Now I have to figure out if the bad RTC is a real problem and I should send the computer back, (I didn't pay much for it) or if it's just a nuisance. I'm leaning toward nuisance but should probably see a replacement motherboard costs if I ever have to replace it. *HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient->SpecialPollInterval = 3600 |
||
|
|
|