Opened 4 years ago

Closed 4 years ago

#13862 closed enhancement (invalid)

No error message when fatally failing to open files in DataDirectory

Reported by: sqrt2 Owned by:
Priority: Low Milestone: Tor: 0.2.6.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: datadirectory permissions error-reporting easy 026-deferrable
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Due to installing packages from conflicting sources, I ended up with a Tor installation where the tor daemon (with User toranon) could access the DataDirectory, but not open the files in it for lack of permissions.

In this situation, tor exits quickly with only the following messages:

Nov 30 00:07:12.878 [notice] Tor v0.2.5.10 (git-42b42605f8d8eac2) running on Linux with Libevent 2.0.18-stable, OpenSSL 1.0.1e-fips and Zlib 1.2.7.
Nov 30 00:07:12.878 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Nov 30 00:07:12.878 [notice] Read configuration file "/usr/share/tor/defaults-torrc".
Nov 30 00:07:12.878 [notice] Read configuration file "/etc/tor/torrc".
Nov 30 00:07:12.881 [notice] Opening Socks listener on 127.0.0.1:9050
Nov 30 00:07:12.881 [notice] Opening Control listener on 127.0.0.1:9151
Nov 30 00:07:12.881 [notice] Caching new entry toranon for toranon
Nov 30 00:07:12.881 [notice] Caching new entry toranon for toranon

There are no explicit Log directives in torrc.

Except for exit status 1, there is no indication to the user that something has gone wrong, and what the problem could be. We should print a helpful error message.

Child Tickets

Change History (2)

comment:1 Changed 4 years ago by nickm

Keywords: easy 026-deferrable added
Milestone: Tor: 0.2.6.x-final
Priority: normalminor

Would be nice to have a patch for this, but not critical for 0.2.6.

comment:2 Changed 4 years ago by sqrt2

Resolution: invalid
Status: newclosed

It turns out there was in fact a Log directive (loaded via --defaults-torrc) and directing the error messages to syslog, where they do appear. Sorry for the confusion.

Note: See TracTickets for help on using tickets.