Hi,
The problem is solved.
There is a conflict between the recursive function of %include and the AppArmor profile.
This can be traced here in line 27: https://gitlab.torproject.org/tpo/core/debian/tor/-/blob/debian-main/debian/...
Because the list was down for a few days, I opened the topic in the forum. If you are interested, you can see the way to solution here: https://forum.torproject.net/t/torrc-unit-files-confusion/2217
-- Martin
On 2/18/22 15:24, lists@for-privacy.net wrote:
On Wednesday, February 16, 2022 8:07:21 AM CET Martin Gebhardt wrote:
I've gotten myself stuck in a situation that I can't get out of. The following:
I have a working relay. You can find the config for it in the attachment [1].
I want to move parts of the config. So I use %include. I don't do anything else than moving parts of the working config to other files. There are no changes at all. But, tor does not start anymore.In the attachment [2] you can find the config with %include. The folder structure is the following:
├── info.html ├── rc.d │ ├── contact.rc │ ├── family.rc │ └── nickname.rc ├── torrc └── torsocks.conf
Your '/lib/systemd/system/tor@default.service' is default like on all my Debian systems.
Did you specify the whole path in '%include'? I have:
# Include MyFamily & ContactInfo %include /etc/tor/torrc.all # Include Exit Policy %include /etc/tor/torrc.exit
For me it is like this, the instances from the subfolders use the configs above.
/etc/tor (root:root mode=drwxr-xr-x) ├── torrc.all ├── torrc.exit ├── instances ├── 00 ├── torrc ├── 01 ├── torrc ...
To rule out a bug, change 'rc.d' to 'rcd'. Without dot in folder name.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays