Opened 13 years ago

Last modified 7 years ago

#242 closed defect (Works for me)

"closing wedged cpuworker"

Reported by: jtesta Owned by: arma
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.1.0.16
Severity: Keywords:
Cc: jtesta Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Jan 16 17:35:42.229 [notice] cull_wedged_cpuworkers(): Bug: closing wedged cpuworker. Can somebody find the bug?

Using libevent-1.1a on a Linux i586 system, the above message appears in my log. Tor server does not seem to crash; service remains viable.

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (4)

comment:1 Changed 13 years ago by arma

Hm. Is this repeatable?

That message only occurs when the cpuworker has been working on the same
public key encryption operation for 60 minutes. Each operation should
take far less than a second.

Perhaps this occurs when your system becomes so slow that Tor doesn't get
any CPU time at all, e.g. because it spends all its time swapping?

Or perhaps it occurs if your clock is bouncing all over the place and it
suddenly skips forward by a few hours?

Let us know if you learn more.

comment:2 Changed 13 years ago by arma

I have increased the timeout to 12 hours, from 1 hour. We haven't heard
from many people who experience this, and perhaps this will help to
narrow down the set even more.

I am guessing that most people who experience this are running on an
extremely underpowered computer and it really is swapping for the whole
hour, thus starving Tor.

comment:3 Changed 13 years ago by arma

flyspray2trac: bug closed.

comment:4 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.