Tor denied message /etc/torrc.d/95_whonix.conf after upgrade from Whonix 13 to Whonix 14

Have exactly same problem. How to fix it?

Hi zealot

Did you try rebooting? You can also try restarting Tor.

https://forums.whonix.org/t/error-tor-not-running-tor-pid-message-pid-file-var-run-tor-tor-pid-doest-not-exist-noob-need-help/5785

Nope, I have same result
image
Sorry, looks like virtialbox guest utils broken, so i could not copypaste logs
image
I think it is apparmor issue

Tor config wrong? Please try Configuration Check as per:

Tor - Whonix

Please watch Tor log while restarting Tor as per:

Tor - Whonix

This might give some clues what’s wrong.


There no any tor logs
image
And, i could start tor manually.

Please watch Tor log while restarting Tor as per:

Tor - Whonix

This might give some clues what’s wrong.


Weird openssl issue only.

grep -i error /var/run/tor/log

?

sudo journalctl -f

while doing this, restart Tor. That would show any apparmor related issues.


From Whonix 14 / Debian stretch AppArmor related changes

sudo cat /var/log/audit/audit.log | grep -i DENIED
grep -i error /var/run/tor/log

return no result

sudo journalctl -f


return several identical attempt to start tor

sudo cat /var/log/audit/audit.log | grep -i DENIED


I could see many messages about tor config files

Its completly look like apparmor issue

Does your /etc/apparmor.d/local/system_tor.anondist looks the same like anon-gw-anonymizer-config/system_tor.anondist at master · Whonix/anon-gw-anonymizer-config · GitHub?


Yes, completly same.

1 Like

And /etc/apparmor.d/local/system_tor also looks same?

It’s actually a symlink.

ls -la /etc/apparmor.d/local/system_tor

lrwxrwxrwx 1 root root 19 Jan 23 14:41 /etc/apparmor.d/local/system_tor → system_tor.anondist

I am just trying to figure out why that file is non-effective for you and wondering if that symlink may be broken.

Could you check please if /etc/apparmor.d/system_tor looks like this:

# vim:syntax=apparmor
#include <tunables/global>

profile system_tor flags=(attach_disconnected) {
  #include <abstractions/tor>

  owner /var/lib/tor/** rwk,
  owner /var/lib/tor/ r,
  owner /var/log/tor/* w,

  # During startup, tor (as root) tries to open various things such as
  # directories via check_private_dir().  Let it.
  /var/lib/tor/** r,

  /{,var/}run/tor/ r,
  /{,var/}run/tor/control w,
  /{,var/}run/tor/socks w,
  /{,var/}run/tor/tor.pid w,
  /{,var/}run/tor/control.authcookie w,
  /{,var/}run/tor/control.authcookie.tmp rw,
  /{,var/}run/systemd/notify w,

  # Site-specific additions and overrides. See local/README for details.
  #include <local/system_tor>
}


Looks same

1 Like

I have no idea then. Might have another idea later on but not likely.

Some cruft during upgrade form Whonix 13 to Whonix 14 must be causing this.

Some file must be different that’s relevant here Whonix 13 upgraded vs Whonix 14. Creating a diff of Whonix 13 vs Whonix 14 files (perhaps just in /etc) would be most likely too much work.

So I suggest to start with a fresh Whonix 14 which doesn’t have this issue.

OK, thank you for helping!