Tor starts before IPv6 is available

Bug #1749309 reported by SJMurdoch on 2018-02-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tor (Ubuntu)
Undecided
Unassigned

Bug Description

On Ubuntu xenial, systemd starts Tor before the IPv6 address is available and so Tor fails to assign an IPv6 address then exits. systemd tries to restart Tor (I think five times) but even by the last time there's still no IPv6 address assigned and hence Tor fails to start.

As a work-around I added RestartSec=10 to the systemd unit file to slow down the restart such that by the second time tor starts, there is an IPv6 address available.

See discussion here for more details https://trac.torproject.org/projects/tor/ticket/25182

Markus Kuhn (markus-kuhn) wrote :

Could not perhaps Tor be fixed to follow the advice for developers at the end of

  https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/#whatdoesthismeanformeadeveloper

such that it can be started up even if the network has not yet been allocated all addresses?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers