Am 01.11.2016 um 13:19 schrieb VinÃcius Zavam:
2016-10-31 20:22 GMT-03:00, Felix zwiebel@quantentunnel.de:
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 ?
-- Cheers, Felix
thanks for pointing out the ticket. how long should we wait to see the warning?
# git branch maint-0.2.9 master
- release-0.2.8
# tor --version Tor version 0.2.8.9-dev (git-badc444f7adce748).
# head /var/log/tor/notice.log_r0289 Oct 31 22:48:44.000 [notice] Tor 0.2.8.9-dev (git-badc444f7adce748) opening new log file. Oct 31 22:48:44.632 [notice] Tor v0.2.8.9-dev (git-badc444f7adce748) running on FreeBSD with Libevent 2.0.22-stable, OpenSSL LibreSSL 2.5.0 and Zlib 1.2.8. Oct 31 22:48:44.633 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Oct 31 22:48:44.633 [notice] Read configuration file "/usr/local/etc/tor/torrc". Oct 31 22:48:44.742 [notice] Opening OR listener on [xxxx:xxxy:xxxz::abcd]:9021 Oct 31 22:48:44.752 [notice] Opening OR listener on a.b.c.d:9021 Oct 31 22:48:44.752 [notice] Opening Extended OR listener on 127.0.0.1:0 Oct 31 22:48:44.752 [notice] Extended OR listener listening on port 29790. Oct 31 22:48:44.752 [notice] Opening Directory listener on a.b.c.d:9000 Oct 31 22:48:44.000 [notice] Parsing GEOIP IPv4 file /usr/local/share/tor/geoip.
# 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
# tail -n3 /var/log/tor/notice.log_r0289 Nov 01 08:51:24.000 [notice] Heartbeat: Tor's uptime is 10:00 hours, with 19 circuits open. I've sent 167.56 MB and received 175.42 MB. Nov 01 08:51:24.000 [notice] Circuit handshake stats since last time: 44/44 TAP, 187/187 NTor. Nov 01 08:51:24.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 1357 v4 connections; and received 0 v1 connections, 59 v2 connections, 52 v3 connections, an
# grep -i jump /var/log/tor/notice.log_r0289 | wc -l 0
I see warnings with about more than 500 circuits.
My log says: Oct 19 01:04:52.527 [notice] Read configuration file "/usr/local/etc/tor/torrc". Oct 19 01:04:52.566 [notice] Opening OR listener on 0.0.0.0:1234 for ORPort 443 NoListen ORPort 1234 NoAdvertise My Tor finds 0.0.0.0 and looks further out ...
I see yours telling: Oct 31 22:48:44.752 [notice] Opening OR listener on a.b.c.d:9021
Hm. Can you please share your torrc line for the "ORPort [address:]PORT|auto [flags]" directive? Can you give an example which is your a.b.c.d, is it the external or a local (lo#) and how do you set NoListen/NoAdvertise ? I want to avoid Tor guessing the ip.