Tor 0.4.5.6 is outputting lots of messages like: Unable to find IPv4 address for ORPort 9001
Havent seen that one before upgrading to 0.4.5.6
$ /home/debian-tor/tor-0.4.5.6/src/app/tor -f /etc/tor/torrc
Feb 16 18:43:19.180 [notice] Tor 0.4.5.6 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0l, Zlib 1.2.8, Liblzma 5.2.2, Libzstd 1.1.2 and Glibc 2.24 as libc.
Feb 16 18:43:19.215 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Feb 16 18:43:19.339 [notice] Read configuration file "/etc/tor/torrc".
Feb 16 18:43:19.455 [warn] Skipping obsolete configuration option "AllowSingleHopExits".
Feb 16 18:43:19.459 [warn] Skipping obsolete configuration option "AllowSingleHopCircuits".
Feb 16 18:43:19.491 [warn] You specified a public address '0.0.0.0:5353' for DNSPort. 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.
Feb 16 18:43:19.495 [warn] Configuration port ORPort 9001 superseded by ORPort [<MY IPV6 ADDRESS>]:9001
Feb 16 18:43:19.514 [notice] Based on detected system memory, MaxMemInQueues is set to 324 MB. You can override this by setting MaxMemInQueues by hand.
Feb 16 18:43:19.524 [warn] Tor is currently configured as a relay and a hidden service. That's not very secure: you should probably run your hidden service in a separate Tor process, at least -- see https://bugs.torproject.org/tpo/core/tor/8742.
Feb 16 18:43:19.650 [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.
Feb 16 18:43:19.655 [warn] You specified a public address '0.0.0.0:5353' for DNSPort. 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.
Feb 16 18:43:19.658 [warn] Configuration port ORPort 9001 superseded by ORPort [<MY IPV6 ADDRESS>]:9001
Feb 16 18:43:19.660 [notice] Opening Socks listener on 0.0.0.0:9050
Feb 16 18:43:19.663 [notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
Feb 16 18:43:19.665 [notice] Opening DNS listener on 0.0.0.0:5353
Feb 16 18:43:19.683 [notice] Opened DNS listener connection (ready) on 0.0.0.0:5353
Feb 16 18:43:19.683 [notice] Opening Control listener on 127.0.0.1:9051
Feb 16 18:43:19.687 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
Feb 16 18:43:19.687 [notice] Opening OR listener on 0.0.0.0:9001
Feb 16 18:43:19.687 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001
Feb 16 18:43:19.687 [notice] Opening OR listener on [<MY IPV6 ADDRESS>]:9001
Feb 16 18:43:19.687 [notice] Opened OR listener connection (ready) on [<MY IPV6 ADDRESS>]:9001
Feb 16 18:45:49.000 [notice] Bootstrapped 0% (starting): Starting
Feb 16 18:51:59.000 [notice] Starting with guard context "default"
Feb 16 18:52:02.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Feb 16 18:52:03.000 [notice] Unable to find IPv4 address for ORPort 9001. You might want to specify IPv4Only to it or set an explicit address or set Address.
Feb 16 18:52:04.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Feb 16 18:52:06.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Feb 16 18:52:07.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Feb 16 18:52:07.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Feb 16 18:52:07.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Feb 16 18:52:07.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Feb 16 18:52:09.000 [notice] External address seen and suggested by a directory authority: <MY IPV4 ADDRESS>
Feb 16 18:52:51.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We're missing descriptors for 1/2 of our primary entry guards (total microdescriptors: 6731/6774). That's ok. We will try to fetch missing descriptors soon.
Feb 16 18:52:51.000 [notice] I learned some more directory information, but not enough to build a circuit: We're missing descriptors for 1/2 of our primary entry guards (total microdescriptors: 6731/6774). That's ok. We will try to fetch missing descriptors soon.
Feb 16 18:52:54.000 [notice] External address seen and suggested by a directory authority: <MY IPV6 ADDRESS>
Feb 16 18:52:54.000 [notice] Bootstrapped 100% (done): Done
Feb 16 18:53:59.000 [notice] Now checking whether IPv4 ORPort <MY IPV4 ADDRESS>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Feb 16 18:54:00.000 [notice] Now checking whether IPv6 ORPort [<MY IPV6 ADDRESS>]:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success
Feb 16 18:56:35.000 [notice] Self-testing indicates your ORPort [<MY IPV6 ADDRESS>]:9001 is reachable from the outside. Excellent.
Feb 16 18:57:07.000 [notice] Self-testing indicates your ORPort <MY IPV4 ADDRESS>:9001 is reachable from the outside. Excellent. Publishing server descriptor.
Feb 16 18:57:11.000 [notice] Performing bandwidth self-test...done.
...
Feb 16 19:52:21.000 [notice] Unable to find IPv4 address for ORPort 9001. You might want to specify IPv4Only to it or set an explicit address or set Address. [59 similar message(s) suppressed in last 3540 seconds]
...