Bug 744005
| Summary: | tor does not start with systemd | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tobias Florek <me> |
| Component: | tor | Assignee: | Enrico Scholz <rh-bugzilla> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | lmacken, matt, rh-bugzilla |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-14 01:12:51 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
> tor does not support the option --runasdaemon anymore. you can either change it
> into --option RunAsDaemon 0
# tor --runasdaemon 0
Oct 07 10:18:07.882 [notice] Tor v0.2.2.33 (git-8522652d8e9213d4). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Oct 07 10:18:07.956 [notice] Initialized libevent version 2.0.10-stable using method epoll. Good.
# tor --option runasdaemon 0
Oct 07 10:18:12.466 [notice] Tor v0.2.2.33 (git-8522652d8e9213d4). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Oct 07 10:18:12.468 [warn] Command-line option '0' with no value. Failing.
# tor --option runasdaemon=0
Oct 07 10:18:20.018 [notice] Tor v0.2.2.33 (git-8522652d8e9213d4). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Oct 07 10:18:20.020 [warn] Failed to parse/validate config: Unknown option 'option'. Failing.
hi enrico, thanks for pointing out my mistake. the problem is, that this is not the real error. so maybe you can consider looking into the problem with tor.service not starting with systemctl. thanks. This bug is also present in Fedora 17. I fixed it by editing /lib/systemd/system/tor.service and changed the following to: Type = forking ExecStart = /usr/bin/tor -f /etc/tor/torrc I hope that works for you Tobias; various forms of this bug have been opened and marked errata since forever so I don't have faith the maintainer will fix this I really can not reproduce it. Perhaps you can increase the loglevel and provide more details? This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: tor does not start with systemd. first, it seems, that the ExecStart is wrong, because tor does not support the option --runasdaemon anymore. you can either change it into --option RunAsDaemon 0 or change it in /etc/tor/torrc (RunAsDaemon 0). the next problem is, that it still does not start (using second option above): # systemctl status tor.service tor.service - Anonymizing overlay network for TCP Loaded: loaded (/lib/systemd/system/tor.service; enabled) Active: failed since Thu, 06 Oct 2011 19:15:45 +0200; 46min ago Process: 8170 ExecStop=/bin/kill -INT ${MAINPID} (code=killed, signal=INT) Process: 8168 ExecStart=/usr/bin/tor --quiet (code=exited, status=255) CGroup: name=systemd:/system/tor.service simply starting tor --quiet does work though. i don't know why bugs #716220 and #684094 are closed errata, when they seem not to be fixed and highly related (if not identical) to this bug.