Hello,
This is not the first occurrence of this warning.
Even shortly after restarting it reappeared.
What does `[warn] assign_to_cpuworker failed. Ignoring.` mean?
Why does this happen?
How can we avoid it?
Kind regards,
Udo
--
tor-talk mailing list - tor-talk@lists.torproject.org
To
On 11-03-17 08:52, Petrusko wrote:
> Last time I had this on the log (stable release), it was because the
> system was swaping like hell...
> Some services unloaded, 1 of the 2 Tor instances stopped to eat less RAM...
This box has 1GB of RAM and is not swapping like hell as it runs headless.
Tor
Last time I had this on the log (stable release), it was because the
system was swaping like hell...
Some services unloaded, 1 of the 2 Tor instances stopped to eat less RAM...
Have you check your free RAM, +swap usage ?
"htop" is cool for a live view for example
Udo van den Heuvel :
> Feb 28
Hello,
Also the pre-release 2.9.10 suffer from this issue.
Kind regards,
Udo
On 01-03-17 17:01, Udo van den Heuvel wrote:
> Hello,
>
> The assign_to_cpuworker issue appeared again.
> See below for some logging from notices.log.
> What is causing this?
> I noticed a high CPU load coinciding
Hello,
The assign_to_cpuworker issue appeared again.
See below for some logging from notices.log.
What is causing this?
I noticed a high CPU load coinciding with these messages.
Please let me know how to fix this.
Udo
Feb 28 15:54:27.000 [notice] Heartbeat: Tor's uptime is 4 days 5:59
hours,
