[tor-relays] torrc, unit files, confusion

Mailing Lists tor-relays
1

Hello together,

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

No matter what I do, I can't get it to enable debug logs when I start tor from the unit file. This is unchanged, but I attached it anyway [3].

Anyway, I start tor as root, then everything works [4]. I have no idea where something should be wrong with the permissions. I have also recursively set the permission of /etc/tor/ to the user debian-tor, but it doesn't help.

When I do the following:

cat rc.d/* >> torrc && sed -i /include/d torrc && systemctl restart tor

Everything works fine again.

My system:
Linux privacy 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux
Tor version 0.4.6.9.
Tor is running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1k, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.33 as libc.
Tor compiled with GCC version 10.2.1

Maybe I'm still too tired to figure it out. But please, can someone give me some advice where to look further? Or at least tell me how to get a debug log when I start tor from the systemd-unit. Then I would surely get further.

Thanks for your attention and help.

···

--
Martin

(Attachment 1-torrc is missing)

(Attachment 2-torrc is missing)

(Attachment 3-tor.service is missing)

(Attachment 4-log is missing)

2

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.

···

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

--
╰_╯ Ciao Marco!

Debian GNU/Linux

It's free software and it gives you freedom!

3

There is no difference between attachment 1-torrc und 2-torrc.

···

On 16.02.22 08:07, Martin Gebhardt wrote:

In the attachment [2] you can find the config with %include.

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

4

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: debian/tor.apparmor-profile.abstraction · debian-main · The Tor Project / Core / debian / tor · GitLab

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: Torrc, unit files, confusion

···

--
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
tor-relays Info Page