#24303 closed defect (user disappeared)

Tor fails to start if %include

Reported by: littlefeather Owned by:
Priority: Medium Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor Version: Tor: 0.3.2.4-alpha
Severity: Major Keywords: config, 033-triage-20180320, 033-removed-20180320
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (7)

comment:1 Changed 18 months ago by nickm

Status: newneeds_information

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?

comment:2 Changed 18 months ago by nickm

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

comment:3 Changed 17 months ago by asn

Milestone: Tor: 0.3.2.x-finalTor: 0.3.3.x-final

Moving to 033 due to lack of info.

comment:4 Changed 14 months ago by nickm

Keywords: 033-triage-20180320 added

Marking all tickets reached by current round of 033 triage.

comment:5 Changed 14 months ago by nickm

Keywords: 033-removed-20180320 added

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

comment:6 Changed 14 months ago by arma

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.

comment:7 Changed 14 months ago by dgoulet

Resolution: user disappeared
Status: needs_informationclosed
Note: See TracTickets for help on using tickets.