[tor-relays] [WARN] Your system clock just jumped 100 seconds forward; assuming established circuits no longer work.

Alexander Makarov ice.turbulent at gmail.com
Wed Feb 19 03:55:43 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yea, maybe you will find something strange or regular

On 19.02.2014 10:59, Zenaan Harkness wrote:
> On 2/19/14, Alexander Makarov <ice.turbulent at gmail.com> wrote:
>> On 18.02.2014 23:39, Zenaan Harkness wrote:
>>> On 2/18/14, Alexander Makarov <ice.turbulent at gmail.com> wrote:
>>>> On 18.02.2014 22:02, Zenaan Harkness wrote:
>>>>> My tor logs (running on Debian) are showing this warning:
>>>>> [WARN] Your system clock just jumped 100 seconds forward; assuming
>>>>> established circuits no longer work.
>>>>>
>>>>> I tried running openntpd as well as ntp packages (debian), and both
>>>>> display the same problem - once or twice a day I get this jump in time
>>>>> of in the order of a couple of minutes.
>>>>>
>>>>> Any idea why?
>>>
>>>> Maybe problem with hardware clocks?
>>>
>>> OK, I just checked that the time is very close to correct local time
>>> (within a couple seconds as best I can tell), and ran
>>> hwclock --systohc
>>>
>>> But, surely the log warning would only happen once? - that's the whole
>>> point of running ntp I thought...
>>>
>>> See how my node goes over the next day or two,
> 
> Well, the time jump still happens, roughly 5hrs apart, 2-3 minute jump.
> 
> 
>> Could you show the log?
> 
> Current and previous tor logs attached. What is also interesting is IP
> address seems to change rather frequently from the ISP (iiNet in this
> case - a home ADSL2 connection, but off-net, so it's a resell of
> Telstra).
> 
> I also note an early morning torrc file read (log.1) - there are no
> changes in the torrc file since the 17th, so except that I run service
> tor reload, I do not expect tor to re-read the torrc file; is this
> normal?:
> Feb 19 07:35:19.000 [notice] Read configuration file "/etc/tor/torrc".
> 
> 
>> Can you rebuild you kernel with debug option and
>> check what kernel events have the same timestamps
> 
> I could install a debug kernel - Debian makes them available. How
> would I "check kernel events" - just check the logs?
> 
> Happy to investigate... might need some hand holding on the process.
> 
> Thanks
> Zenaan
> 
> 
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

- -- 
Best regards,
Alexander Makarov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTBCs/AAoJEBuTDJZeb03Vfs8P/3PKhPayOSwEoT2nUeUMKdo7
GLusU4CS+bPVwYkz0iGOwAG/X/Of+wOMGDseaQh/Ta0Cfex4qzNwvtXaVe/lDpEs
rYq459ibWR3TApeYzS1B7H2uqRqPqDZscofClygpfzRBf44Ge6nIbqRhaq93Dg7Q
+kgMKTd+HAKFgZwJRsl1c1y2ISdRFnyOs8AuBciZuN8UCQhy8iiQhTXMTAW3Dn6J
+RarlCN0FqD1Z0nCdNjMEAqQH6r2z4kX9rnMr3TkXwgKoJjuHn/PhLa6kjBUbnE0
cKHfL0ww8Ur+yG3H42mny0/sgrv+lF9vLzYDzo6LdvXWGXadt5703KsLkhZ0Cw1f
sb8+mJ+uhyCiSNOFcZp1nQ82bXskFYpf1HrpBJaby+r9ZeovMH5RAVw95Ghnp+f9
MvuVMOR6ufp9MFBkHuULmeHA/mT4vXzupQNHSeXR5OwoknR52dbnyb3JDKCFd+sB
sXqVorEobXFtWlft2aEAYC7pSTiKNypaFc0jDwAoGWNGWDfQs1iTz7XjZ2bqoDw0
bhqgGVvOOUPE4G6X14RBcZ1nk4esQyY11eJGPyRsp6r5D9iMNebhkfEo3US9Sx2B
c+OBrWCO0I51A218TV5+wITuzq8gbq8WnwfX3TSSvydd85Gtl0pyTJeQYhalFgJV
M8bVnTpBMSzjNO4eBJJQ
=u1Rp
-----END PGP SIGNATURE-----


More information about the tor-relays mailing list