Re: [tor-talk] [warn] assign_to_cpuworker failed. Ignoring.

2017-03-11 Thread Udo van den Heuvel
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 u

Re: [tor-talk] [warn] assign_to_cpuworker failed. Ignoring.

2017-03-10 Thread Petrusko
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 17

Re: [tor-talk] [warn] assign_to_cpuworker failed. Ignoring.

2017-03-09 Thread Udo van den Heuvel
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 wi