Your message dated Thu, 26 Jan 2017 17:41:02 +0000
with message-id <[email protected]>
and subject line Re: Bug#820223: tor: Tor doesn't start at start-up
has caused the Debian Bug report #820223,
regarding Tor will not start on boot when an interface it is configured to bind 
to is not yet available
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
820223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820223
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tor
Version: 0.2.7.6-1
Severity: important

Dear Maintainer,

Tor doesn't start up at system boot. I've done "systemctl enable tor"
and it still doesn't start up. I have to manually do this via
"systemctl start tor" or "service tor start". This could be related to
apparmor: "systemctl list-units" shows that apparmor failed. This
system is a stock debian testing system, no special kernels or systemd
configuration.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tor depends on:
ii  adduser              3.114
ii  init-system-helpers  1.29
ii  libc6                2.22-5
ii  libevent-2.0-5       2.0.21-stable-2+b1
ii  libseccomp2          2.2.3-3
ii  libssl1.0.2          1.0.2g-1
ii  libsystemd0          229-3
ii  lsb-base             9.20160110
ii  zlib1g               1:1.2.8.dfsg-2+b1

Versions of packages tor recommends:
ii  logrotate    3.8.7-2
ii  tor-geoipdb  0.2.7.6-1
ii  torsocks     2.1.0-2

Versions of packages tor suggests:
pn  apparmor-utils       <none>
pn  mixmaster            <none>
pn  obfs4proxy           <none>
pn  obfsproxy            <none>
pn  socat                <none>
pn  tor-arm              <none>
pn  torbrowser-launcher  <none>

-- Configuration Files:
/etc/tor/torrc changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message ---
On Thu, 26 Jan 2017, segfault wrote:

> Package: tor
> Version: 0.2.9.8-2
> Severity: normal
> 
> Dear Maintainer,
> 
> I encountered the same problem reported here. On my system, 
> I configured Tor to automatically start on boot via
> `systemctl enable tor@default`.

Not sure why you think that would be necessary.  Tor starts by default.

>                                 But during boot, the start of the
> service fails repeatedly with these log messages:
> 
>   [notice] Tor 0.2.9.8 (git-a0df013ea241b026) running on Linux with Libevent 
> 2.0.21-stable, OpenSSL 1.1.0c and Zlib 1.2.8.
>   [notice] Tor can't help you if you use it wrong! Learn how to be safe at 
> https://www.torproject.org/download/download#warning
>   [notice] Read configuration file 
> "/usr/share/tor/tor-service-defaults-torrc".
>   [notice] Read configuration file "/etc/tor/torrc".
>   [warn] Unparseable address in hidden service port configuration.
>   [warn] Failed to parse/validate config: Failed to configure rendezvous 
> options. See logs for details.
>   [err] Reading config failed--see warnings above.
> 
> When starting the service manually with `systemctl start tor@default`,
> the service starts fine.
> 
> I took a look at the systemd unit files and added
> `network-online.target` to the `After=` line of 
> `/lib/systemd/system/[email protected]`.
> This fixed the problem for me, after rebooting Tor started 
> without errors.

The network-online.target doesn't really do anything in almost all
configurations.

> -- Configuration Files:
> /etc/tor/torrc changed:
> HiddenServiceDir /var/lib/tor/ssh/
> HiddenServicePort 22 127.0.0.1:22
> HiddenServiceDir /var/lib/tor/xmpp/
> HiddenServicePort 5222 jabber.[redacted]:5222

If you use DNS names then tor can't start before you can resolve them.
But we have no reliable means to wait for that in Debian.  It's a shame,
but there's nothing the package can do for you here.

-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/

--- End Message ---

Reply via email to