[tor-talk] [warn] assign_to_cpuworker failed. Ignoring.
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 unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] [warn] assign_to_cpuworker failed. Ignoring.
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 uses 600MB or so max. (MaxMemInQueues 612 MB) But I will check again when the issue reoccurs. Kind regards, Udo -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] [warn] assign_to_cpuworker failed. Ignoring.
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:15:17.000 [warn] assign_to_cpuworker failed. Ignoring. -- Petrusko C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5 signature.asc Description: OpenPGP digital signature -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] [warn] assign_to_cpuworker failed. Ignoring.
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 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, with 484 circuits open. I've sent 45.53 GB and received 45.21 GB. > Feb 28 15:54:27.000 [notice] Heartbeat: Accounting enabled. Sent: 941.20 > MB, Received: 931.36 MB, Used: 957.53 MB / 99.00 GB, Rule: max. The > current accounting interval ends on 2017-03-01 12:21:00, in 20:26 > hours. > Feb 28 15:54:27.000 [notice] Circuit handshake stats since last time: > 3643/3643 TAP, 36324/36324 NTor. > Feb 28 15:54:27.000 [notice] Since startup, we have initiated 0 v1 > connections, 0 v2 connections, 1 v3 connections, and 70514 v4 > connections; and received 382 v1 connections, 4159 v2 connections, 5961 > v3 con > nections, and 182525 v4 connections. > Feb 28 15:55:06.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:00:04.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:05:05.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:10:05.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:15:04.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:20:05.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:25:08.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:30:07.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:35:05.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:40:05.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:45:05.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:50:11.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 16:55:05.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 17:00:05.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 17:05:08.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 17:10:10.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 17:15:17.000 [notice] New control connection opened from 127.0.0.1. > Feb 28 17:15:17.000 [warn] assign_to_cpuworker failed. Ignoring. > Feb 28 17:15:17.000 [warn] assign_to_cpuworker failed. Ignoring. > Feb 28 17:15:17.000 [warn] assign_to_cpuworker failed. Ignoring. > Feb 28 17:15:17.000 [warn] assign_to_cpuworker failed. Ignoring. > Feb 28 17:15:18.000 [warn] assign_to_cpuworker failed. Ignoring. > (etc, many many more) > -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
[tor-talk] [warn] assign_to_cpuworker failed. Ignoring.
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, with 484 circuits open. I've sent 45.53 GB and received 45.21 GB. Feb 28 15:54:27.000 [notice] Heartbeat: Accounting enabled. Sent: 941.20 MB, Received: 931.36 MB, Used: 957.53 MB / 99.00 GB, Rule: max. The current accounting interval ends on 2017-03-01 12:21:00, in 20:26 hours. Feb 28 15:54:27.000 [notice] Circuit handshake stats since last time: 3643/3643 TAP, 36324/36324 NTor. Feb 28 15:54:27.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 1 v3 connections, and 70514 v4 connections; and received 382 v1 connections, 4159 v2 connections, 5961 v3 con nections, and 182525 v4 connections. Feb 28 15:55:06.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:00:04.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:05:05.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:10:05.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:15:04.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:20:05.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:25:08.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:30:07.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:35:05.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:40:05.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:45:05.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:50:11.000 [notice] New control connection opened from 127.0.0.1. Feb 28 16:55:05.000 [notice] New control connection opened from 127.0.0.1. Feb 28 17:00:05.000 [notice] New control connection opened from 127.0.0.1. Feb 28 17:05:08.000 [notice] New control connection opened from 127.0.0.1. Feb 28 17:10:10.000 [notice] New control connection opened from 127.0.0.1. Feb 28 17:15:17.000 [notice] New control connection opened from 127.0.0.1. Feb 28 17:15:17.000 [warn] assign_to_cpuworker failed. Ignoring. Feb 28 17:15:17.000 [warn] assign_to_cpuworker failed. Ignoring. Feb 28 17:15:17.000 [warn] assign_to_cpuworker failed. Ignoring. Feb 28 17:15:17.000 [warn] assign_to_cpuworker failed. Ignoring. Feb 28 17:15:18.000 [warn] assign_to_cpuworker failed. Ignoring. (etc, many many more) -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
