Hide Forgot
Description of problem: SELinux is preventing (tor) from 'mounton' accesses on the directory /var/lib/tor. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that (tor) should be allowed mounton access on the tor directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c '(tor)' --raw | audit2allow -M my-tor # semodule -X 300 -i my-tor.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:tor_var_lib_t:s0 Target Objects /var/lib/tor [ dir ] Source (tor) Source Path (tor) Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages tor-0.2.8.8-1.fc25.x86_64 Policy RPM selinux-policy-3.13.1-216.fc25.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.8.0-0.rc8.git0.1.fc25.x86_64 #1 SMP Mon Sep 26 17:12:24 UTC 2016 x86_64 x86_64 Alert Count 10 First Seen 2016-10-05 16:03:15 CEST Last Seen 2016-10-05 16:03:22 CEST Local ID e3db9d68-3da5-44d4-85e1-4e08f70b52fa Raw Audit Messages type=AVC msg=audit(1475676202.76:179): avc: denied { mounton } for pid=1080 comm="(tor)" path="/var/lib/tor" dev="dm-0" ino=172986 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:tor_var_lib_t:s0 tclass=dir permissive=0 Hash: (tor),init_t,tor_var_lib_t,dir,mounton Version-Release number of selected component: selinux-policy-3.13.1-216.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.8.0-0.rc8.git0.1.fc25.x86_64 type: libreport Potential duplicate: bug 1374668
Description of problem: "systemctl start tor.service" on a fresh install results in: Oct 12 16:47:22 localhost.localdomain tor[4138]: Oct 12 16:47:22.506 [notice] Tor v0.2.8.8 running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2j-fips and Zlib 1.2.8. Oct 12 16:47:22 localhost.localdomain tor[4138]: Oct 12 16:47:22.506 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Oct 12 16:47:22 localhost.localdomain tor[4138]: Oct 12 16:47:22.506 [notice] Read configuration file "/usr/share/tor/defaults-torrc". Oct 12 16:47:22 localhost.localdomain tor[4138]: Oct 12 16:47:22.506 [notice] Read configuration file "/etc/tor/torrc". Oct 12 16:47:22 localhost.localdomain tor[4138]: Oct 12 16:47:22.509 [notice] Opening Socks listener on 127.0.0.1:9050 Oct 12 16:47:22 localhost.localdomain tor[4138]: Oct 12 16:47:22.509 [warn] Unable to make /var/lib/tor group-readable: Read-only file system Oct 12 16:47:22 localhost.localdomain Tor[4138]: OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000208f: OpenSSL 1.0.2h 3 May 2016; run Oct 12 16:47:22 localhost.localdomain Tor[4138]: Tor v0.2.8.8 running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2j-fips and Zlib 1.2.8. Oct 12 16:47:22 localhost.localdomain Tor[4138]: Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Oct 12 16:47:22 localhost.localdomain Tor[4138]: Read configuration file "/usr/share/tor/defaults-torrc". Oct 12 16:47:22 localhost.localdomain Tor[4138]: Read configuration file "/etc/tor/torrc". Oct 12 16:47:22 localhost.localdomain Tor[4138]: Opening Socks listener on 127.0.0.1:9050 Oct 12 16:47:22 localhost.localdomain Tor[4138]: Unable to make /var/lib/tor group-readable: Read-only file system Oct 12 16:47:22 localhost.localdomain Tor[4138]: Couldn't open "/var/lib/tor/lock" for locking: Read-only file system Oct 12 16:47:22 localhost.localdomain Tor[4138]: set_options(): Bug: Acting on config options left us in a broken state. Dying. (on Tor 0.2.8.8 ) Oct 12 16:47:22 localhost.localdomain systemd[1]: tor.service: Main process exited, code=exited, status=1/FAILURE Oct 12 16:47:22 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=tor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? Oct 12 16:47:22 localhost.localdomain systemd[1]: Failed to start Anonymizing overlay network for TCP. -- Subject: Unit tor.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tor.service has failed. -- -- The result is failed. Oct 12 16:47:22 localhost.localdomain systemd[1]: tor.service: Unit entered failed state. Oct 12 16:47:22 localhost.localdomain systemd[1]: tor.service: Failed with result 'exit-code'. Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.8.1-1.fc25.x86_64 type: libreport
As a data point, this also happens with a new (updated) Fedora 24 x64 install too.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora 'version' of '25'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.