Opened 11 months ago

Closed 10 months ago

Last modified 3 months ago

#22356 closed defect (fixed)

[warn] assign_to_cpuworker failed. Ignoring.

Reported by: arma Owned by: nickm
Priority: Medium Milestone: Tor: 0.3.1.x-final
Component: Core Tor/Tor Version: Tor: 0.3.1.1-alpha
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

On my guard relay running (a few commits before) 0.3.1.1-alpha, I have these log lines:

May 22 06:04:15.536 [warn] assign_to_cpuworker failed. Ignoring.
May 22 12:10:11.926 [warn] assign_to_cpuworker failed. Ignoring.

I don't have any more verbose logging for this one, but I'll try to get it.

I wonder what is causing it? If it's a bug, we should fix it. If it's really something to ignore, we should downgrade it.

Child Tickets

Change History (6)

comment:1 Changed 10 months ago by nickm

Owner: set to nickm
Status: newaccepted

comment:2 Changed 10 months ago by nickm

Status: acceptedneeds_review

Downgrade in bug22356_029. The only tricky part was reviewing all the paths and making sure they already had better log messages.

This branch is based on maint-0.2.9, but I vote "no backport."

comment:3 Changed 10 months ago by catalyst

Status: needs_reviewmerge_ready

Looks good to me.

comment:4 Changed 10 months ago by nickm

Resolution: fixed
Status: merge_readyclosed

Merged to maint-0.3.1; not considering for backport.

comment:5 Changed 3 months ago by crivit1955

I've just starting having this problem with the Tor relay I am running Tor 0.2.9.14 on Linux. Shame on you that can't be bothered to backport this fix. This means I have to shut down my Tor relay which has been in continuous operation since September 2014.

comment:6 in reply to:  5 Changed 3 months ago by teor

Replying to crivit1955:

I've just starting having this problem with the Tor relay I am running Tor 0.2.9.14 on Linux. Shame on you that can't be bothered to backport this fix. This means I have to shut down my Tor relay which has been in continuous operation since September 2014.

You could just ignore the warning message. That's all the patch does.

Note: See TracTickets for help on using tickets.