| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: System clock turned backward; clearing timeouts (problem) |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
These messages i find every morning in the BOINC log.
Most of the time i crunch 6 WU at the same time. Every time this happens i loose a lot of processing-time. I canceled all time syncs but ones a week. I have a backup running from 23:00 to 01:00 every day Computer has nothing else to do. How can i create a clear run for WCG? 29-11-2012 5:45:14 | | System clock was turned backwards; clearing timeouts 29-11-2012 5:45:14 | World Community Grid | Task DSFL_00030-32_0000012_0650_0 exited with zero status but no 'finished' file 29-11-2012 5:45:14 | World Community Grid | If this happens repeatedly you may need to reset the project. |
||
|
|
dango
Senior Cruncher Joined: Jul 27, 2009 Post Count: 307 Status: Offline Project Badges: 
|
same problem for me :(
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This issue is resolved in version 7 of the client. Timers are reset without affecting the jobs. There's one new problem that at least shows on Linux, but not on Windows: The jobs stop computing until the time is reached when the clock was set back. Only seen this on my Linux 12.10 USB stick and is a problem related to dual boot and timezone handling.
But, clocks adjusting should really only be twice a year for DST and sparsely... seconds at a time, but not more than 30 seconds, which is the critical threshold. If your clock runs ahead each day, warranting the clock to be set backward each day something else is going on. |
||
|
|
sgoll
Advanced Cruncher Joined: Oct 24, 2006 Post Count: 87 Status: Offline Project Badges: 
|
These messages i find every morning in the BOINC log. Most of the time i crunch 6 WU at the same time. Every time this happens i loose a lot of processing-time. I canceled all time syncs but ones a week. I have a backup running from 23:00 to 01:00 every day Computer has nothing else to do. How can i create a clear run for WCG? 29-11-2012 5:45:14 | | System clock was turned backwards; clearing timeouts 29-11-2012 5:45:14 | World Community Grid | Task DSFL_00030-32_0000012_0650_0 exited with zero status but no 'finished' file 29-11-2012 5:45:14 | World Community Grid | If this happens repeatedly you may need to reset the project. First: I think you are running windows. Is this right? I think your hardware clock may run to fast, this could be a production problem but it also may be a problem with the cmos battery. You may take a look into the cmos setup and look for something like "battery voltage". 3.1 volts are fine, everything below 2.9 volts can be a problem. Second: depending on your windows release there is a registry entry like this one: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\W32Time\Parameters It contains a list of time servers your system is using for synchronising the system time. At the end of the parameters list there is something like: pool.ntp.org,0x1 This "0x1" thing controls how often the synchronisation will occour. Normally the windows systems do this once a week. When setting this value to 0x8 this should happen every 16 minutes or so. More synchronisations should help against remarkeable time jumps. I only have windows XP here ... the registry key name may be different in other releases. If you don't have a HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\W32Time\Parameters key you may add a time server (like pool.ntp.org) in the clock setting and enable "internet time". When searching the registry for the name of the time server you've choosen you should be able to find the right key in the registry. The "0x8" thing should help, but a restart of the w32time service may be needed to activate this setting. Please be carefully when changing values in the registry. Linux users can simply install ntp(d) and all those time problems should be gone.  Stephan  [Edit 7 times, last edit by sgoll at Nov 29, 2012 9:22:18 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for reminding me of this... think you posted this in past.
4 edits to get that tongue in ;>) Yes I know about the Linux bit, but simply fixed it by setting the timezone on the Linux instance to UK(GMT) instead of Rome. Something to do with UTC offset. |
||
|
|
sgoll
Advanced Cruncher Joined: Oct 24, 2006 Post Count: 87 Status: Offline Project Badges:
|
Thanks for reminding me of this... think you posted this in past. 4 edits to get that tongue in ;>) Yes I know about the Linux bit, but simply fixed it by setting the timezone on the Linux instance to UK(GMT) instead of Rome. Something to do with UTC offset. 7 edits ... it's early in the morning, it's cold and my fingers do not what I want. And I'm out of coffee ...  Stephan |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I tried everything I could think off.
I check almost every key in the registry. Cancelled all tasks in the scheduler (planner) I even started without any drivers or other programs. After starting, stopped many services and things I don't need. But still, between 0:00 en 6:00 these messages occur. Why only at night? I see that Boinc gives these messages but doesn't loose really much processing time. So i don't worry about that anymore, but still. I started every possible Log that is available in windows, but still cant find any trigger. only the system log en the boinc log register this event. Last step in this process is renewing the batteries for my bios/cmos Thanks for your insides and help, it is now a personal problem. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
However personal you wish to make is, don't do
 And to help analyze [the BOINC log will show the time reset within about 1 minute], use Process Monitor http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx ... today disabled the "Windows Search" service. It was happy to eat 20-30 percent on 4 cores of a Windows 8 system, for extended periods, time and again, suggesting it's not maintaining indices as files are added and changed, almost as if it starts from scratch each time... on and on, but clocks should not run fast, mostly when there's a faulty component. How much is the backward adjustment anyhow? (you posted the time of the adjusted time logged in the OP, but not the log entry prior to suggest the differential) Is the security software interfering? |
||
|
|
|