“sudo journalctl” returns around the time when network connection is not working/is overloaded:
Tor: We’d like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. [159776 similar message(s) suppressed in last 780 seconds]
159776 in 780 is 204 per second. I am using Tor in web browser like for Twitter and also for a P2P app which has 166 network connection when i check now.
Is that log line looking OK, or i should do some particular command to discover more detail?
(bump) - I’m getting the same. Tor is so overloaded that the onion service I am hosting is not reachable (both by missing descriptor and timeout). Is this the DOS attack? Same question as OP: Anyone have ideas of possible configuration changes to mitigate / or commands & tools to investigate what is happening
Do not allow more than NUM circuits to be pending at a time for handling client streams. A circuit is pending if we have begun constructing it, but it has not yet been completely constructed. (Default: 32)
Is there anyone who can explain what it is and where error may be, what to try?