| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: New system time < old system time clearing timeouts |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
i007008
Cruncher Joined: Sep 16, 2005 Post Count: 21 Status: Offline Project Badges: 
|
I have the message:
New system time (nnnnn) < old system time (nnnn) clearing timeouts and it would appear the BOINC agent is not doing anything i.e. not consuming CPU cycles, not moving tasks forward. This message was repeated at 12:36 and 13:36 so nothing has been happening for the last hour. Win 8, dual core laptop, rebooted this morning everything working normally until this message appeared. Any ideas or thoughts, please? Thanks Chris |
||
|
|
i007008
Cruncher Joined: Sep 16, 2005 Post Count: 21 Status: Offline Project Badges:
|
Should have said that this message appeared inthe event log. Also, everything has now returned to normal and tasks are moving forward so all that's left would be some thoughts about what the message was about.
Thanks |
||
|
|
jonnieb-uk
Ace Cruncher England Joined: Nov 30, 2011 Post Count: 6105 Status: Offline Project Badges: 
|
See the comments in this thread
----------------------------------------Hint: If you looking for explanation of an error or message that appears in the Event Log use Search and enter some or all of the message with individual words seperated by '+' and no spaces. So in this case entering 'old+system+time' was sufficient to bring up previous instances of this problem being reported. |
||
|
|
i007008
Cruncher Joined: Sep 16, 2005 Post Count: 21 Status: Offline Project Badges:
|
Thanks for the quick reply, JonnieB. Apparently a 10 second time difference between my system clock and the time according to the MSF time signal is enough to cock it up. I think the problem occurred because I rebooted this morning, and Windows hadn't completed a regular time synchronisation.
Spooky that I haven't encountered this before in the 10 years I've been running BOINC, on several different computers. Crunch on. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Think the reset is when adjustment is > 30 seconds, this being the maximum interval the science applications talk to the client/daemon, else as deemed to have gone AWOL for a little. It happens most often when dealing with the Windows calendar, looking at some past date and then erroneous saves this as the new date, instead of escaping out. The newer clients such as v7 handle the issue better [courtesy of some back and forth of undersigned with developer].
----------------------------------------This topic in Start Here "Zero Status" & "If this happens repeatedly..." is very closely related. I'll add a clock reset paragraph to this when I have time. (Puts a knot in the handkerchief ;) Edit: Maybe you can do a copy / paste of the full Event log series, so I can use that as an FAQ example. What client version was this? Edit 2: Don't bother, as the thread referred to in top post has the exchange documented: 4/22/2015 8:59:38 AM | | New system time (1429707481) < old system time (1429707579); clearing timeouts 4/22/2015 8:59:39 AM | World Community Grid | Task E230162_338_S.300.C41H54.UROJIVMZKFPVKZ-UHFFFAOYSA-N.5_s1_14_0 exited with zero status but no 'finished' file 4/22/2015 8:59:39 AM | World Community Grid | If this happens repeatedly you may need to reset the project. [Edit 2 times, last edit by Former Member at Jun 16, 2015 4:49:29 PM] |
||
|
|
i007008
Cruncher Joined: Sep 16, 2005 Post Count: 21 Status: Offline Project Badges:
|
Thanks SekeRob that's much appreciated. FYI details from Event Log are:
16/06/2015 11:38:15 | World Community Grid | Sending scheduler request: To fetch work. 16/06/2015 11:38:15 | World Community Grid | Requesting new tasks for Intel GPU 16/06/2015 11:38:18 | World Community Grid | Scheduler request completed: got 0 new tasks 16/06/2015 12:36:45 | | New system time (1420066798) < old system time (1434454606); clearing timeouts 16/06/2015 13:36:51 | World Community Grid | Sending scheduler request: Requested by project. 16/06/2015 13:36:51 | World Community Grid | Requesting new tasks for Intel GPU 16/06/2015 13:36:52 | | New system time (1434454611) < old system time (1434458212); clearing timeouts 16/06/2015 13:21:00 | World Community Grid | update requested by user 16/06/2015 13:36:52 | World Community Grid | Computation for task MCM1_0014576_5280_1 finished 16/06/2015 13:36:52 | World Community Grid | Starting task MCM1_0014583_0571_1 BOINC Manager version is 7.4.42 (x64) Thanks again. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
First adjustment: New system time (1420066798) < old system time (1434454606); clearing timeouts
----------------------------------------Second Adjustment: New system time (1434454611) < old system time (1434458212); clearing timeouts The BOINC clock count seconds from 1.1.1970 at 00:00 hours [A Unix thing]. First there was a "back in time" adjustment of 14387808 seconds, or 166 days, then the system internet clock aligning wised up and put the correct date/time in, with an extra 10 seconds to with. Looking at the butler, he's the usual suspect ;? In past the old clients would get seriously upset, nowadays they can't care less what actual date it is. A counter would start running which would stop work fetching until the current date was reached again, which is why there's now the timeout clearings in such events. [Edit 1 times, last edit by Former Member at Jun 16, 2015 5:39:39 PM] |
||
|
|
|