Bug 716220

Summary: Tor service still fails to start with systemd
Product: [Fedora] Fedora Reporter: Matt Kinni <matt>
Component: torAssignee: Enrico Scholz <rh-bugzilla>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 15CC: cassmodiah, lmacken, me, mszafranski, paul.destefano-redhat2, rh-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-26 11:26:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matt Kinni 2011-06-23 16:42:52 UTC 
Description of problem:
Tor service always fails to start; "systemctl start tor.service" reveals no error message, but an excerpt from /var/log/messages reveals:

Jun 23 09:38:55 localhost systemd[1]: tor.service: main process exited, code=exited, status=255
Jun 23 09:38:55 localhost systemd[1]: tor.service holdoff time over, scheduling restart.
Jun 23 09:38:55 localhost kernel: [ 2094.103890] systemd[1]: Unit tor.service entered failed state.
Jun 23 09:38:55 localhost kernel: [ 2094.143697] systemd[1]: tor.service: main process exited, code=exited, status=255
Jun 23 09:38:55 localhost systemd[1]: tor.service holdoff time over, scheduling restart.
Jun 23 09:38:55 localhost kernel: [ 2094.284411] systemd[1]: Unit tor.service entered failed state.

and it does that over and over.  It starts up fine by just issuing the "tor" command.


Version-Release number of selected component (if applicable):
tor-0.2.1.30-1501.fc15.x86_64

How reproducible:
Always

Steps to Reproduce:
1. yum install tor, default everything
2. service tor start / systemctl start tor.service
3. 
  
Actual results:
nothing happens

Expected results:
tor starts

Additional info:
Comment 1 Enrico Scholz 2011-06-23 17:21:48 UTC 
Works here:

# rpm -e tor-core tor-systemd
# rpm -qa ^tor\*
# yum install -y tor-systemd
...
Installiert:
  tor-systemd.noarch 0:0.2.1.30-1501.fc15

Abhängigkeit installiert:
  tor-core.x86_64 0:0.2.1.30-1501.fc15

# rpm -qa ^tor\*
tor-core-0.2.1.30-1501.fc15.x86_64
tor-systemd-0.2.1.30-1501.fc15.noarch

# ls /etc/sysconfig/tor
ls: cannot access /etc/sysconfig/tor: No such file or directory

# rpm -V tor-core tor-systemd


# service tor start
Redirecting to /bin/systemctl  start tor.service

# service tor status
Redirecting to /bin/systemctl  status tor.service
tor.service - Anonymizing overlay network for TCP
          Loaded: loaded (/lib/systemd/system/tor.service)
          Active: active (running) since Thu, 23 Jun 2011 19:06:35 +0200; 9min ago
        Main PID: 30658 (tor)
          CGroup: name=systemd:/system/tor.service
                  └ 30658 /usr/bin/tor --quiet

# service tor stop
Redirecting to /bin/systemctl  stop tor.service

# service tor status
Redirecting to /bin/systemctl  status tor.service
tor.service - Anonymizing overlay network for TCP
          Loaded: loaded (/lib/systemd/system/tor.service)
          Active: inactive (dead) since Thu, 23 Jun 2011 19:18:38 +0200; 4s ago
         Process: 31951 ExecStop=/bin/kill -INT ${MAINPID} (code=exited, status=0/SUCCESS)
        Main PID: 30658 (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/tor.service

# systemctl start tor.service

# systemctl status tor.service
tor.service - Anonymizing overlay network for TCP
          Loaded: loaded (/lib/systemd/system/tor.service)
          Active: active (running) since Thu, 23 Jun 2011 19:18:57 +0200; 13s ago
        Main PID: 31966 (tor)
          CGroup: name=systemd:/system/tor.service
                  └ 31966 /usr/bin/tor --quiet
Comment 2 Matt Kinni 2011-06-26 11:26:39 UTC 
Oops disregard that, I forgot the standard operating procedure of disabling selinux on new Fedora installs.  Now that I've done that, it starts perfectly ;)
Comment 3 Paul DeStefano 2011-07-07 00:37:03 UTC 
Okay, great, glad it will be fixed, but where is the errata?

What was the root cause and what will be changed in the updated release?  As it is, I can't tell if the promised bug fix is going to fix my problem or not.

Maybe you meant CLOSED WORKSFORME or CLOSED NOTABUG ?
Comment 4 Mariusz Szafranski 2011-07-20 02:00:02 UTC 
starts when started by:
systemctl  start tor.service or service tor start

but fails to start with system start !!!
(enabled by "systemctl  enable tor.service")
Comment 5 Paul DeStefano 2011-07-20 15:27:16 UTC 
I opened a new bug for that, actually, because it's not clear this bug is related.  See bug 719476 .  But, thanks, I'm glad it's not just me.
Comment 6 Tobias Florek 2011-10-06 18:04:57 UTC 
see bug 744005 for a new bug :)