Opened 4 years ago

Closed 10 months ago

#17002 closed enhancement (wontfix)

chutney start could tell users how to kill old chutney tors

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords: tor-chutney-usability
Cc: Actual Points:
Parent ID: #16949 Points: .5
Reviewer: Sponsor: SponsorS-can


The most common reason chutney start fails to start all tor processes is port conflicts caused by old chutney tor processes still running.

We could tell users how to kill processes (should we?) using a summary of the following information from

"However, sometimes chutney fails to launch due to a persistent error. The most common issue is having a previous chutney network active. Old chutney networks are typically killed by chutney/tools/ using chutney stop, but sometimes this doesn't happen. The tor processes launched by chutney can be found using a command like ps auxwww | grep chutney | grep tor. Ensure each pid doesn't belong to a process you want, like a system tor or an unrelated process, then kill each chutney tor pid using kill. Alternately, each tor instance's pid files can be found in the chutney/net/nodes directory. (Old nodes directories are renamed using an increasing numeric timestamp as a suffix.)"


  • chutney stop
  • ps auxwww | grep chutney | grep tor and carefull check each pid before using kill on it
  • the tor pid files in the chutney/net/nodes* directories (maybe, these can be very old)

Child Tickets

Change History (6)

comment:1 Changed 3 years ago by nickm

Keywords: tor-chutney-usability added

comment:2 Changed 3 years ago by nickm

Points: .5
Severity: Normal

comment:3 Changed 3 years ago by nickm

Sponsor: SponsorS-can

comment:4 Changed 3 years ago by nickm

Owner: nickm deleted
Status: newassigned

Remove myself as chutney ticket owner. Default owners are trouble.

comment:5 Changed 3 years ago by nickm

Status: assignednew

comment:6 Changed 10 months ago by teor

Resolution: wontfix
Status: newclosed

I haven't seen this error in a long time: I think our OwningControllerProcess changes fixed it.

Note: See TracTickets for help on using tickets.