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

[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 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)
>