Petrusko:
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...
On what hardware/OS this relay is running? It seems to be due to hitting resource limits. { src/or/onion.c:238 + "assign_to_cpuworker failed" error } Though neither circuit_mark_for_close() should be called twice nor tor process should crash. Do you see other warnings? Messages about the reason of tor termination?
btw, there is a ticket for this very issue: https://trac.torproject.org/projects/tor/ticket/20059 As long as it happens at the same lines of code I guess all this has common reason. "assign_to_cpuworker" error is a kinda consequence of hitting rate-limits (likely RAM usage).
Probably there is a memory leakage somewhere that makes everything fail and get process eventually killed by OS. -- Ivan Markin