Am 31.10.2016 um 23:40 schrieb VinÃcius Zavam:
2016-10-19 2:30 GMT-03:00, teor teor2345@gmail.com:
On 19 Oct. 2016, at 16:25, Felix zwiebel@quantentunnel.de wrote:
Hi everybody
May be someone can help with this warning:
The security update (Tor v0.2.8.9 running on FreeBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.4.3 and Zlib 1.2.8.) shows the following log entry each hour:
Oct 19 02:51:07.000 [warn] Your system clock just jumped 136 seconds forward; assuming established circuits no longer work. Oct 19 02:51:07.000 [warn] assign_to_cpuworker failed. Ignoring. ... Oct 19 02:51:07.000 [warn] assign_to_cpuworker failed. Ignoring. Oct 19 02:51:15.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. ... Oct 19 03:51:10.000 [warn] Your system clock just jumped 138 seconds forward; assuming established circuits no longer work. Oct 19 03:51:11.000 [warn] assign_to_cpuworker failed. Ignoring. ... Oct 19 04:50:37.000 [warn] Your system clock just jumped 105 seconds forward; assuming established circuits no longer work. Oct 19 04:50:37.000 [warn] assign_to_cpuworker failed. Ignoring. ... Oct 19 05:51:14.000 [warn] Your system clock just jumped 142 seconds forward; assuming established circuits no longer work. Oct 19 05:51:15.000 [warn] assign_to_cpuworker failed. Ignoring. ...
The warning first appeared on 2.8.7 after update on September 13th (Tor v0.2.8.7 running on FreeBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.4.2 and Zlib 1.2.8.). That time I switched back (Tor v0.2.7.6 running on FreeBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.4.2 and Zlib 1.2.8.) and the warning disappeared.
What can I do?
The warning is reproted in tor-talk: https:// lists.torproject.org/pipermail/tor-talk/2016-October/042425.html
Thanks for reporting this issue - you could open a bug on our bug tracker under Core Tor/Tor: https://trac.torproject.org/projects/tor/newticket
It would help us to know if it's just FreeBSD, or just LibreSSL.
Maybe mention the bug number on tor-talk, so that poster can provide more details?
Tim
-- Best regards, Felix
T
-- Tim Wilson-Brown (teor)
felix,
that might not be related to Tor, but to your host's clock setup and/or your jail's setup.
# tor --version Tor version 0.2.9.4-alpha (git-8b0755c9bb296ae2). # uname -ai FreeBSD cq110a 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 18:37:29 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 GENERIC # grep -i jump /var/log/tor/notice.log | wc -l 0 # sysctl security.jail.jailed security.jail.jailed: 1 # uptime 7:32PM up 18 days, 4:44, 1 user, load averages: 0.21, 0.21, 0.17
Good to see Tor in a jail runs for you. For me it did until 0.2.8. You want to take a look at https:// trac.torproject.org/projects/tor/ticket/20423 ?