Opened 6 years ago

Closed 18 months ago

#9250 closed defect (user disappeared)

strange TERM signal

Reported by: Envite Owned by: erinn
Priority: Medium Milestone:
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


User on ticket #11560 experiences a TERM signal:

jul 05 09:12:59.619 [Notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on Windows 7.
jul 05 09:12:59.619 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at
jul 05 09:12:59.619 [Notice] Read configuration file "C:\Users\Jordi\Downloads\Tor Browser\Data\Tor\torrc".
jul 05 09:12:59.619 [Notice] Initialized libevent version 2.0.21-stable using method win32. Good.
jul 05 09:12:59.619 [Notice] Opening Socks listener on
jul 05 09:12:59.619 [Notice] Opening Control listener on
jul 05 09:12:59.833 [Notice] Parsing GEOIP file .\Data\Tor\geoip.
jul 05 09:13:01.536 [Notice] No AES engine found; using AES_* functions.
jul 05 09:13:01.536 [Notice] This OpenSSL has a good implementation of counter mode; using it.
jul 05 09:13:01.536 [Notice] OpenSSL OpenSSL 1.0.0k 5 Feb 2013 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
jul 05 09:13:01.536 [Notice] Reloaded microdescriptor cache. Found 3896 descriptors.
jul 05 09:13:01.536 [Notice] We now have enough directory information to build circuits.
jul 05 09:13:01.536 [Notice] Bootstrapped 80%: Connecting to the Tor network.
jul 05 09:13:01.536 [Notice] New control connection opened.
jul 05 09:13:02.520 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 5 circuits open. I've sent 0 kB and received 0 kB.
jul 05 09:13:02.520 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
jul 05 09:13:03.107 [Notice] Catching signal TERM, exiting cleanly.

Child Tickets

Change History (8)

comment:1 Changed 6 years ago by arma

What's strange about it?

It looks for example like the user hit C if they were running Tor themselves, or like they clicked 'stop Tor' in Vidalia.

comment:2 Changed 6 years ago by Envite

User has confirmed he receives this strange TERM signal without doing anything, each time he starts the program.

comment:3 Changed 6 years ago by rransom

I checked the 'owning controller process' code; that would have produced a notice-level message that doesn't appear in that log.

It can't actually be SIGTERM; Windows doesn't support signals.

That log probably means that Tor's controller sent it a 'SIGNAL TERM' control-port command to shut it down. (It would be helpful to know what version of TBB the user is trying to use.)

comment:4 Changed 5 years ago by erinn

Keywords: needs-triage added

comment:5 Changed 5 years ago by erinn

Component: Tor bundles/installationTor Browser
Status: newneeds_information

comment:6 Changed 4 years ago by TORques

"jul 05 09:13:03.107 [Notice] Catching signal TERM, exiting cleanly."

The [Notice] Catching signal TERM, exiting cleanly. appears if the TOR server got a Signal INT from a controller. Signal.INT = Close listeners and exit TOR gracefully (30 s). Tested on Tor on Windows XP.

Here is an example coded in Python with STEM libs. because Vidalia is deprecated I built my own scripts to run a TOR relay on Windows XP.

import sys
from stem import Signal
from stem.control import Controller
  if sys.argv[1] == "INT":
Last edited 4 years ago by TORques (previous) (diff)

comment:7 Changed 2 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:8 Changed 18 months ago by cypherpunks

Component: Applications/Tor BrowserCore Tor/Tor
Keywords: TERM needs-triage removed
Resolution: user disappeared
Status: needs_informationclosed
Note: See TracTickets for help on using tickets.