[Issue] A recurrent issue causes a break of the network requester + socks5 client operation #4109
Assignees
Labels
bug
Something isn't working
bug-needs-triage
A bug that needs discussing and triage
needs-triage
qa
Quality Assurance
Comments
twofaktor
added
bug
|
How often are you restarting your NR service? And is the flow here that you:
The error messages are interesting. |
lately, almost every day
Correct, and if I consult the NR logs and socks5 client, I can see these logs E.g, consulted a moment ago: NR: Socks5 client: Also, socks5 applications attached (telegram, keybase, etc) stop working to be able to connect to the socks5 client (socks5 client stops working if NR stops working)
PS: Today I decided to stop using NYM, I stopped my network requester and the socks5 client, as well as the applications connected to it. When this problem is solved I will use NYM again, these nodes were never very stable for me, but recently with the latest releases, now it is unfeasible to operate them if I have to restart them every day. I hope this will fixed soon |
|
I'm very sorry to hear that but understand. Once the nodes are combined in the coming months then this problem should disappear hopefully, although its something to be looking into. Thanks for the update. One final question re: "but recently with the latest releases, now it is unfeasible to operate them" - is this something that has become worse recently? Can you pinpoint (or have a rough idea) of the version that this became worse at? |
Uhm... I'm sorry I don't remember exactly but I think since 2 releases before to current maybe |
|
BTW: To discard possible error triggers, I'm testing running NR and socks5 client, but not connecting any persistent app to the socks5 let's see if it continues to fail or not. I will bring back conclusions Attach here some socks5 client logs that appear to me since I'm testing that: |
|
Interesting. We've had a few timeout issues crop up in channels recently - this should be sorted once we have the |
|
More logs about nym-socks5-client without to request connections to it during 2 days: It makes me think that there is also a problem with the nym-socks5 client, when I restart the nym-socks5 client the problem connecting to it is resolved |
twofaktor
changed the title
|
@twofaktor have you ran into this since, there's been a lot of releases since this event happened, i will close the ticket, but if you comment and re-open it we can investigate. |
Sometimes (randomly and not so frequently) socks5 + requester stop working, and restarting the requester is fixed, i think it's a requester issue, but I can't find the reason in the logs anymore. If I find the reason ever, I would open an issue again with the new report. Thanks for your attention |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
After starting nym-network-request randomly, it stops working after the next logs, after that, nym-socks5-client and the apps attached to it stop working too:
WARN nym_socks5_proxy_helpers::proxy_runner::outbound didn't get anything from the client on 13960325690217133581 mixnet in 300s. Shutting down the proxy.It is solved by restarting the network request, but it happens very often, constantly requiring the intervention of the administrator.
Expected behaviour
Stability and reliability of the service
Stack Traces
Network requester:
Socks5-client after network requester fails:
Steps to Reproduce
Screenshots
Network requester:
Socks5-client after network requester fails:
Which area of Nym were you using?
Issue related: #3719
The text was updated successfully, but these errors were encountered: