FS#38864 - [tor] does not start with "systemctl start tor"

Attached to Project: Community Packages
Opened by Thomas Preissler (tomtom) - Monday, 10 February 2014, 21:06 GMT
Last edited by Lukas Fleischer (lfleischer) - Thursday, 20 February 2014, 08:18 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After a regular package install tor doesn't start and is always shown as "failed" in systemctl.
Manually starting it as the dedicated user "tor" it runs fine.

Additional info:
* package version(s)
0.2.4.20-1
* config and/or log files etc.
shown as "failed" within systemctl

Steps to reproduce:
1) pacman -S tor
2) configuring it as a relay, bridge, exitnode whatever
3) systemctl start tor
4) is not running


Fix
I am fairly certain that the default config has not "RunAsDaemon 1" commented out - so I have not changed that.
The systemd script /usr/lib/systemd/system/tor.service has "Type=simple", but the correct one should be "Type=forking". Changing that [...] then it starts up fine.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Thursday, 20 February 2014, 08:18 GMT
Reason for closing:  Works for me
Comment by Lukas Fleischer (lfleischer) - Tuesday, 11 February 2014, 09:05 GMT
"RunAsDaemon 1" is commented out in the default config, you could have checked that.
Comment by Daniel Micay (thestinger) - Thursday, 20 February 2014, 04:17 GMT
It works for me with the default configuration. Since `RunAsDaemon` is commented out, `Type=simple` is definitely the correct setting and is preferred over making the daemon fork and using `Type=forking` with systemd.
Comment by Daniel Micay (thestinger) - Thursday, 20 February 2014, 04:19 GMT
Does `grep RunAsDaemon /etc/torrc` really not show any uncommented lines for you?
Comment by Lukas Fleischer (lfleischer) - Thursday, 20 February 2014, 08:18 GMT
I think we can close this. I have three confirmations that it works with the default configuration.

Loading...