[tor-relays] tor relay

[newsletter at unicorncloud.org]

On 12.03.2020 08:14, Станислав wrote:

> 11.03.2020, 22:57, "Sean Greenslade" <sean at seangreenslade.com>: On 
> March 9, 2020 3:55:38 AM PDT, "Станислав" <armik900 at gmail.com> wrote: 
> hi.I start second instance of tor, but for some reason it stopped
> working.after updating the firmware on board pc engines apu2
> 
> Mar 09 13:48:46.000 [notice] Bootstrapped 0% (starting): Starting
> Mar 09 13:49:03.000 [notice] Starting with guard context "default"
> Mar 09 13:49:03.000 [warn] Unable to parse '/etc/resolv.conf', or no
> nameservers in '/etc/resolv.conf' (1)
> Mar 09 13:49:03.000 [warn] Couldn't set up any working nameservers.
> Network not up yet? Will try again soon.
> Mar 09 13:49:03.000 [notice] Self-testing indicates your ORPort is
> reachable from the outside. Excellent.
> Mar 09 13:49:04.000 [notice] Bootstrapped 5% (conn): Connecting to a
> relay
> Mar 09 13:49:04.000 [warn] Unable to parse '/etc/resolv.conf', or no
> nameservers in '/etc/resolv.conf' (1)
> Mar 09 13:49:04.000 [notice] Bootstrapped 10% (conn_done): Connected to
> a relay
> Mar 09 13:49:04.000 [notice] Bootstrapped 14% (handshake): Handshaking
> with a relay
> Mar 09 13:49:05.000 [notice] Bootstrapped 15% (handshake_done):
> Handshake with a relay done
> Mar 09 13:49:05.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded
> enough directory info to build circuits
> Mar 09 13:49:05.000 [notice] Bootstrapped 90% (ap_handshake_done):
> Handshake finished with a relay to build circuits
> Mar 09 13:49:05.000 [notice] Bootstrapped 95% (circuit_create):
> Establishing a Tor circuit
> Mar 09 13:49:06.000 [notice] Bootstrapped 100% (done): Done
> Mar 09 13:50:05.000 [notice] Self-testing indicates your DirPort is
> reachable from the outside. Excellent. Publishing server descriptor.
> Mar 09 13:50:08.000 [notice] Performing bandwidth self-test...done.
> Mar 09 13:51:32.000 [notice] Received reload signal (hup). Reloading
> config and resetting internal state.
> Mar 09 13:51:32.000 [notice] Read configuration file "/etc/tor/torrc1".
> Mar 09 13:51:32.000 [notice] Your ContactInfo config option is not set.
> Please consider setting it, so we can contact you if your server is
> misconfigured or something else goes wrong.
> Mar 09 13:51:32.000 [warn] MyFamily is set but ContactInfo is not
> configured. ContactInfo should always be set when MyFamily option is
> too.
> Mar 09 13:51:32.000 [notice] Tor 0.4.2.5 opening log file.
> Mar 09 13:51:32.000 [warn] Unable to parse '/etc/resolv.conf', or no
> nameservers in '/etc/resolv.conf' (1)
> Mar 09 13:51:32.000 [err] set_options(): Bug: Acting on config options
> left us in a broken state. Dying. (on Tor 0.4.2.5 )
> Mar 09 13:51:32.000 [err] Reading config failed--see warnings above.
> For usage, try -h.
> Mar 09 13:51:32.000 [warn] Restart failed (config error?). Exiting.
> Well, these lines look like a good place to start:
> 
> Mar 09 13:49:03.000 [warn] Unable to parse '/etc/resolv.conf', or no 
> nameservers in '/etc/resolv.conf' (1)
> Mar 09 13:49:03.000 [warn] Couldn't set up any working nameservers. 
> Network not up yet? Will try again soon.
> What are the contents of /etc/resolv.conf ?
> 
> --Sean
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

С уважением,
Станислав

127.0.0.1
::1
but the errors continue.I run of odhcpd+unbound.on a unbound works 
dns-over-tls in log torrc these errors.are what could be the problem?
Mar 09 15:13:37.000 [warn] Unable to parse '/etc/resolv.conf', or no 
nameservers in '/etc/resolv.conf' (1)
Mar 09 15:23:37.000 [warn] Unable to parse '/etc/resolv.conf', or no 
nameservers in '/etc/resolv.conf' (1)
Mar 09 15:33:37.000 [warn] Unable to parse '/etc/resolv.conf', or no 
nameservers in '/etc/resolv.conf' (1)

Hi,
/etc/resolv.conf needs to be formatted like this:
nameserver 1.2.3.4
nameserver 4.3.2.1

All the best
Sebastian