On Fri, 18 Dec 2015, Michael Meskes wrote: > On a fresh unstable installation tor refuses to do anything. The situation > seems to be different from #802521, hence a new bug report. If it turns out to > be the same bug, feel free to merge. > > Dez 18 13:16:08 feivel tor[1349]: Dec 18 13:16:08.001 [notice] Read > configuration file "/usr/share/tor/tor-service-defaults-torrc". > Dez 18 13:16:08 feivel systemd[1356]: tor@default.service: Failed at step > APPARMOR spawning /usr/bin/tor: No such file or directory > Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Main process exited, > code=exited, status=231/APPARMOR > Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Unit entered failed > state. > Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Failed with result > 'exit-code'. > Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Service hold-off time > over, scheduling restart. > > Manually downgrading to 0.2.5.12-1 solved the problem for now.
Can you tell me more about the system? My guess is, this is an lxc container. Am I right? If not, what's the kernel? Some other kind of virtualization going on? weasel -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `- https://www.debian.org/