11.03.2020, 22:57, "Sean Greenslade" sean@seangreenslade.com:

On March 9, 2020 3:55:38 AM PDT, "Станислав" armik900@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@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)

...

What are the contents of /etc/resolv.conf ?

127.0.0.1 ::1

That's the problem. The format of resolv.conf requires the string "nameserver" before each ip. Try something like this:

# Up to three nameserver lines are allowed. nameserver 127.0.0.1 nameserver ::1 #nameserver <optional backup server>

--Sean

On Fri, 13 Mar 2020 13:17:48 +0300 Станислав armik900@gmail.com wrote:

12.03.2020, 23:36, "Sean Greenslade" sean@seangreenslade.com:

...

...

...

What are the contents of /etc/resolv.conf ?

127.0.0.1 ::1

That's the problem. The format of resolv.conf requires the string "nameserver" before each ip. Try something like this:

# Up to three nameserver lines are allowed. nameserver 127.0.0.1 nameserver ::1 #nameserver <optional backup server>

--Sean

---

tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

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

that’s exactly what it says, I simply shortened and did not write the word nameserver _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Post the entire file without shortening or removing any line. If it complains about parse error, there must be something wrong in it, but you don't notice or don't think it is wrong. People on the mailing list can check if it's ok, but again only if you post the entire file (copy-paste or attach).

Hi,

...

Post the entire file without shortening or removing any line. If it complains about parse error, there must be something wrong in it, but you don't notice or don't think it is wrong. People on the mailing list can check if it's ok, but again only if you post the entire file (copy-paste or attach).

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

<resolv.conf>

There could be a few things wrong here.

Try setting ServerDNSResolvConfFile to /dev/null, or a world-readable empty file, and see if your problem goes away.

If it does, here are some common issues to check:

What are the permissions on /etc.resolv.conf ? Can the tor user read the file?

Is the file a symlink? (macOS does this, not sure if some Linux distros do as well)

Are there any hidden characters in the file? Does it use Unix newlines?

Tor uses libevent's evdns_base_resolv_conf_parse() to parse the file. https://libevent.org/doc/dns_8h.html#a7e3a053e25ae7c045944a5db0947babb

How old is your version of libevent?

T

On Fri, 13 Mar 2020 15:22:49 +0300 Станислав armik900@gmail.com wrote:

13.03.2020, 14:55, "teor" teor@riseup.net: Hi,   Post the entire file without shortening or removing any line. If it complains about parse error, there must be something wrong in it, but you don't noticeor don't think it is wrong. People on the mailing list can check if it's ok,but again only if you post the entire file (copy-paste or attach).  С уважением, Станислав   <resolv.conf>   There could be a few things wrong here.   Try setting ServerDNSResolvConfFile to /dev/null, or a world-readable empty file, and see if your problem goes away.   If it does, here are some common issues to check:   What are the permissions on /etc.resolv.conf ? Can the tor user read the file?   Is the file a symlink? (macOS does this, not sure if some Linux distros do as well)   Are there any hidden characters in the file? Does it use Unix newlines?   Tor uses libevent's evdns_base_resolv_conf_parse() to parse the file. https://libevent.org/doc/dns_8h.html#a7e3a053e25ae7c045944a5db0947babb   How old is your version of libevent?

FYI in a private discussion we figured out that the trailing dot in "search lan." was indeed what caused the issue.