-
Notifications
You must be signed in to change notification settings - Fork 421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect ping timeout #76
Comments
Even worse, if after step 4 you do client.disconnect() and then client.connect() the process dies with the following |
regarding this, a regular irc PING to the server is actually the standard solution for most clients. |
Thanks for the workaround csimi and damianb. I am currently using this to keep my irc web client online after a daily disconnect in the night:
Though I'd rather like node-irc to send a close event if a PING hasn't been received in a specified timeout. For example if a PING usually arrives every 90s then it would be odd if the last PING is 180s or 270s ago. |
@rretzbach from my observations, best to wait 5 minutes for ping timeout - perhaps after making a server ping yourself and waiting a minute. |
Please Close this. Ping timeout support was added from #176 |
Oh okay, thanks, support was lost due to the code reconstruction. #214 should be reopened. |
Done. |
This really needs to be implemented. |
I'm working on this now, should be done by the end of the night. |
Awesome! 👍 |
Fixed in #418. |
I think there's no ping timeout detection in the library right now. I waited for around 5 minutes to see if something happens but nothing did.
Steps to reproduce:
I'm gonna temporarily fix this issue by manually pinging the server every few minutes but this puts (a minimal amount from my single bot) extra stress on the server so you might want to find something more elegant.
15 Dec 21:59:39 - SEND: PING :PONG
15 Dec 21:59:39 - Connection got "close" event
15 Dec 21:59:39 - Disconnected: reconnecting
15 Dec 21:59:39 - Waiting 2000ms before retrying
The text was updated successfully, but these errors were encountered: