Hi!
Yes, since I set the "Address "line in torrc, this message was gone. But ... I nevertheless get the "clock jumped" warning once a day:
"Jan 21 18:34:53.000 [warn] Your system clock just jumped 398 seconds forward; assuming established circuits no longer work."
3-6 minutes difference is quite much. I also have a ntp daemon running and don't know why this happens. The clock is synced?
Regards,
On 22.01.2017 15:59, Petrusko wrote:
Got it too, Sooo many lines in my log file. [...] Jan 22 06:37:37.000 [warn] assign_to_cpuworker failed. Ignoring. Jan 22 06:37:37.000 [warn] assign_to_cpuworker failed. Ignoring. Jan 22 06:37:37.000 [warn] circuit_mark_for_close_(): Bug: Duplicate call to circuit_mark_for_close at ../src/or/onion.c:238 (first at ../src/or/command.c:579) (on Tor 0.2.9.8 ) Jan 22 06:37:37.000 [warn] circuit_mark_for_close_(): Bug: Duplicate call to circuit_mark_for_close at ../src/or/onion.c:238 (first at ../src/or/command.c:579) (on Tor 0.2.9.8 ) Jan 22 06:37:37.000 [warn] circuit_mark_for_close_(): Bug: Duplicate call to circuit_mark_for_close at ../src/or/onion.c:238 (first at ../src/or/command.c:579) (on Tor 0.2.9.8 ) [...]
Then 1 Tor process has crashed and restarted himself... The other Tor instance has not been this log...
NTP daemon is running too on this node.
I'll keep an eye on this log file...
Hello!
What does this warning mean?
"Jan 13 09:31:49.000 [warn] assign_to_cpuworker failed. Ignoring."
Do I need to reduce the number of connection to the relay or could I ignore this message?
Regards,
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays