Just updated to the latest and much hyped version of the new and redesigned bitcoin node. Well it looks like I am hosed due to some networking config? Would love some help to get this back up and running or roll back the update?
snippet from the TS logs:
itcoin_tor_1 | Jun 27 13:03:09.380 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc.
bitcoin_tor_1 | Jun 27 13:03:09.380 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at Am I totally anonymous if I use Tor? | Tor Project | Support
bitcoin_tor_1 | Jun 27 13:03:09.380 [notice] Read configuration file “/etc/tor/torrc”.
bitcoin_tor_1 | Jun 27 13:03:09.384 [warn] You have a ControlPort set to accept connections from a non-local address. This means that programs not running on your computer can reconfigure your Tor. That’s pretty bad, since the controller protocol isn’t encrypted! Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
bitcoin_tor_1 | Jun 27 13:03:09.385 [warn] CookieAuthFileGroupReadable is set, but will have no effect: you must specify an explicit CookieAuthFile to have it group-readable.
bitcoin_tor_1 | Jun 27 13:03:09.389 [warn] You specified a public address ‘0.0.0.0:9050’ for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don’t allow this unless you have a good reason.
bitcoin_tor_1 | Jun 27 13:03:09.389 [warn] You have a ControlPort set to accept connections from a non-local address. This means that programs not running on your computer can reconfigure your Tor. That’s pretty bad, since the controller protocol isn’t encrypted! Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
bitcoin_tor_1 | Jun 27 13:03:09.389 [notice] Opening Socks listener on 0.0.0.0:9050
bitcoin_tor_1 | Jun 27 13:03:09.390 [notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
bitcoin_tor_1 | Jun 27 13:03:09.390 [notice] Opening Control listener on 0.0.0.0:9051
bitcoin_tor_1 | Jun 27 13:03:09.390 [notice] Opened Control listener connection (ready) on 0.0.0.0:9051
bitcoin_tor_1 | Jun 27 13:03:09.705 [warn] Error creating directory /tmp/.tor: No space left on device
bitcoin_tor_1 | Jun 27 13:03:09.705 [notice] Closing partially-constructed Socks listener connection (ready) on 0.0.0.0:9050
bitcoin_tor_1 | Jun 27 13:03:09.705 [notice] Closing partially-constructed Control listener connection (ready) on 0.0.0.0:9051
bitcoin_tor_1 | Jun 27 13:03:09.705 [warn] Failed to parse/validate config: Couldn’t create private data directory “/tmp/.tor”
bitcoin_tor_1 | Jun 27 13:03:09.705 [err] Reading config failed–see warnings above.