Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T13:58:11Zhttps://gitlab.torproject.org/legacy/trac/-/issues/433Tor 0.1.2.13 - Error initializing dns subsystem2020-06-13T13:58:11ZTracTor 0.1.2.13 - Error initializing dns subsystemI just upgraded to Tor 0.1.2.13 on Solaris 8 (Generic_117350-46) and now the service dies out complaing
it cannot read resolv.conf. I even attempted to set the ServerDNSResolvConfFile to another (new)
resolv.conf using my ISP DNS rathe...I just upgraded to Tor 0.1.2.13 on Solaris 8 (Generic_117350-46) and now the service dies out complaing
it cannot read resolv.conf. I even attempted to set the ServerDNSResolvConfFile to another (new)
resolv.conf using my ISP DNS rather than my internal DNS servers thinking the private net and the loopback
might be causing issues. For some reason, the log output at 00:29:59.165 (below) shows tor adding 127.0.0.l
as a DNS server (which there is) but its not defined in the new resolv conf and I even took it out of the
system resolv.conf for one round of testing.
I've poked around and tried running this as mu tor user and then root to rule out permissions issues with
no change. Googling shows the code changes around this, but I'm no coder and unfortunately cant see any
obvious problems.
Debug log Output (running as root for testing):
> /opt/csw/bin/tor -f /opt/csw/etc/tor/torrc
May 21 00:29:59.123 [notice] Tor v0.1.2.13. This is experimental software. Do not rely on it for strong anonymity.
May 21 00:29:59.137 [notice] Initialized libevent version 1.1a using method devpoll. Good.
May 21 00:29:59.138 [notice] Opening OR listener on 0.0.0.0:49001
May 21 00:29:59.139 [notice] Opening Socks listener on 127.0.0.1:9050
May 21 00:29:59.140 [notice] Opening Socks listener on 10.15.20.10:9100
May 21 00:29:59.140 [notice] Opening Control listener on 127.0.0.1:9051
[root@lapetus:tor, 00:29:59]> May 21 00:29:59.142 [notice] Tor 0.1.2.13 opening log file.
May 21 00:29:59.143 [debug] parse_dir_server_line(): Trusted dirserver at 18.244.0.188:9031 (46DB)
May 21 00:29:59.143 [debug] parse_dir_server_line(): Trusted dirserver at 18.244.0.114:80 (E45D)
May 21 00:29:59.143 [debug] parse_dir_server_line(): Trusted dirserver at 86.59.21.38:80 (1F85)
May 21 00:29:59.144 [debug] parse_dir_server_line(): Trusted dirserver at 140.247.60.64:80 (F5FC)
May 21 00:29:59.144 [debug] parse_dir_server_line(): Trusted dirserver at 194.109.206.212:80 (EAD6)
May 21 00:29:59.145 [info] or_state_load(): Loaded state from "/opt/csw/var/lib/tor/state"
May 21 00:29:59.147 [debug] parse_addr_policy(): Adding new entry 'accept 10.15.20.0/24'
May 21 00:29:59.147 [debug] parse_addr_policy(): Adding new entry 'accept 127.0.0.1'
May 21 00:29:59.147 [debug] parse_addr_policy(): Adding new entry 'reject *'
May 21 00:29:59.147 [warn] You are running Tor as root. You don't need to, and you probably shouldn't.
May 21 00:29:59.162 [info] crypto_seed_rng(): Seeding RNG from "/dev/urandom"
May 21 00:29:59.164 [info] configure_nameservers(): Parsing resolver configuration in '/etc/resolv.conf'
May 21 00:29:59.164 [info] eventdns: Parsing resolv.conf file /etc/resolv.conf
May 21 00:29:59.165 [info] eventdns: Added nameserver 127.0.0.1
May 21 00:29:59.165 [warn] Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf'
May 21 00:29:59.172 [err] Error initializing dns subsystem; exiting
May 21 00:29:59.233 [info] or_state_save(): Saved state to "/opt/csw/var/lib/tor/state"
May 21 00:29:59.234 [debug] _connection_free(): closing fd 5.
May 21 00:29:59.234 [debug] _connection_free(): closing fd 8.
May 21 00:29:59.235 [debug] _connection_free(): closing fd 9.
May 21 00:29:59.235 [debug] _connection_free(): closing fd 10.
[Automatically added by flyspray2trac: Operating System: Solaris]
**Trac**:
**Username**: geekcq