Linux system log shows Tor 0.4.5.8 log lines like:
Tor: Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query. Tor: Closing stream for '[scrubbed].onion': hidden service is unavailable (try again later). Tor: Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
You can see these HSDir log lines being added quite quickly (update each 5 seconds):
while true; do sleep 5 && journalctl -u tor|grep "No more HSDir available to query" -c; done 2777 2778 2779 2781 2783 2784 2784 2785 2787 2789
which may be normal for my usage case - third party app to connect .onion peers & trackers and it is normal for this app to face various offline peers/trackers.
I have found following comments to mentioned kind of log lines:
“Likely your Guard is the issue making all HSDir and Intro attempt to fail.”
“can happen because of a misconfigured entry or guard node. Try making a new circuit, or disconnecting and reconnecting, and if that doesn’t work, using a bridge”
Can be something done to fix Tor (the best) or its client (app)?
Same, unanswered question here.