Tor fails to start if %include

If %include is present in torrc then tor service will fail to start. The directive I aded to torrc was %include /etc/torrc.d/

Folder exist and perms are valid, but tor service will not start and tor will not write the reason why to log.

Trac:
Username: littlefeather

changed milestone to %Tor: 0.3.3.x-final

added 033-removed-20180320 033-triage-20180320 component::core tor/tor config milestone::Tor: 0.3.3.x-final priority::medium reporter::littlefeather resolution::user disappeared severity::major status::closed type::defect version::tor 0.3.2.4-alpha labels

I've just tried this, and it worked for me. Can you say more about what platform you're using, and how Tor is installed?

Trac:
Status: new to needs_information

Are you running Tor inside Apparmor, or something else that might restrict which files it's allowed to read?

Moving to 033 due to lack of info.

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.3.x-final

Marking all tickets reached by current round of 033 triage.

Trac:
Keywords: N/A deleted, 033-triage-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

Trac:
Keywords: N/A deleted, 033-removed-20180320 added

Four months are passed and no new info. The apparmor guess is a plausible one -- meaning that whoever writes the apparmor rules for whatever Tor package this was is going to have to think about how the %include directive works. I think it's getting to be time to close this one as user-disappeared though.

Trac:
Resolution: N/A to user disappeared
Status: needs_information to closed

closed

moved to tpo/core/tor#24303 (closed)