After a fresh installation syslog is full with entries like this:
Oct 7 23:05:09 pi-hole systemd[1]: tor@default.service: Failed with result 'signal'.
Oct 7 23:05:09 pi-hole systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
Oct 7 23:05:09 pi-hole systemd[1]: Stopped Anonymizing overlay network for TCP.
Oct 7 23:05:09 pi-hole systemd[1]: Starting Anonymizing overlay network for TCP...
Oct 7 23:05:09 pi-hole systemd[1]: tor@default.service: Control process exited, code=killed status=11
Oct 7 23:05:09 pi-hole systemd[1]: Failed to start Anonymizing overlay network for TCP.
Oct 7 23:05:09 pi-hole systemd[1]: tor@default.service: Unit entered failed state.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Failed with result 'signal'.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
Oct 7 23:05:10 pi-hole systemd[1]: Stopped Anonymizing overlay network for TCP.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Start request repeated too quickly.
Oct 7 23:05:10 pi-hole systemd[1]: Failed to start Anonymizing overlay network for TCP.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Unit entered failed state.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Failed with result 'signal'.
Oct 7 23:05:09 pi-hole systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
Oct 7 23:05:09 pi-hole systemd[1]: Stopped Anonymizing overlay network for TCP.
Oct 7 23:05:09 pi-hole systemd[1]: Starting Anonymizing overlay network for TCP...
Oct 7 23:05:09 pi-hole systemd[1]: tor@default.service: Control process exited, code=killed status=11
Oct 7 23:05:09 pi-hole systemd[1]: Failed to start Anonymizing overlay network for TCP.
Oct 7 23:05:09 pi-hole systemd[1]: tor@default.service: Unit entered failed state.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Failed with result 'signal'.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
Oct 7 23:05:10 pi-hole systemd[1]: Stopped Anonymizing overlay network for TCP.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Start request repeated too quickly.
Oct 7 23:05:10 pi-hole systemd[1]: Failed to start Anonymizing overlay network for TCP.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Unit entered failed state.
Oct 7 23:05:10 pi-hole systemd[1]: tor@default.service: Failed with result 'signal'.
Gesendet: Montag, 07. Oktober 2019 um 22:02 Uhr
Von: "Roger Dingledine" <a...@torproject.org>
An: tor-relays@lists.torproject.org
Betreff: Re: [tor-relays] obfs4 bridge stuck at 0% bootstrap
Von: "Roger Dingledine" <a...@torproject.org>
An: tor-relays@lists.torproject.org
Betreff: Re: [tor-relays] obfs4 bridge stuck at 0% bootstrap
On Mon, Oct 07, 2019 at 04:56:32PM +0200, Volker Mink wrote:
> <div>I am running an OBFS4 Bridge at home for a while now.</div>
>
> <div>But everytime im looking in the logs it says
> <div># [notice] Bootstrapped 0%: Starting</div>
Hi Volker,
Three suggestions:
(A) Upgrade to a newer version of Tor. Tor 0.2.9.x is way way old
at this point, and it's missing a bunch of fixes.
https://community.torproject.org/relay/setup/
(B) Try bootstrapping it as a happy bridge without obfs4 first, to
make sure that part works. Then you can add obfs4 back in.
(C) You might want to discard the current bridge identity key, now that
you've sent it to the list. (With knowledge of your identity key, once
the bridge is working, people can go to the bridge directory authority
and fetch your descriptor, learning your IP address.)
Thanks!
--Roger
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> <div>I am running an OBFS4 Bridge at home for a while now.</div>
>
> <div>But everytime im looking in the logs it says
> <div># [notice] Bootstrapped 0%: Starting</div>
Hi Volker,
Three suggestions:
(A) Upgrade to a newer version of Tor. Tor 0.2.9.x is way way old
at this point, and it's missing a bunch of fixes.
https://community.torproject.org/relay/setup/
(B) Try bootstrapping it as a happy bridge without obfs4 first, to
make sure that part works. Then you can add obfs4 back in.
(C) You might want to discard the current bridge identity key, now that
you've sent it to the list. (With knowledge of your identity key, once
the bridge is working, people can go to the bridge directory authority
and fetch your descriptor, learning your IP address.)
Thanks!
--Roger
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays