Re: [tor-relays] assign_to_cpuworker failed. Ignoring.

[teor <teor2345@xxxxxxxxx>]

> On 19 Oct. 2016, at 16:25, Felix <zwiebel@xxxxxxxxxxxxxxxx> 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
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
------------------------------------------------------------------------------







_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays