Skip to content
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

tennu appears to be closing IRC socket for no reason #47

Closed
alienth opened this issue Mar 17, 2015 · 4 comments
Closed

tennu appears to be closing IRC socket for no reason #47

alienth opened this issue Mar 17, 2015 · 4 comments

Comments

@alienth
Copy link

alienth commented Mar 17, 2015

I have a fairly simple IRC bot which uses tennu. It is persistently connected to freenode. Once or twice a day it becomes disconnected from freenode. I have full debug logs enabled and there is nothing indicating why the disconnection occurred. I've also tcpdumped the traffic, and the client appears to cleanly close the socket, with no other activity immediately preceding the close (nor is there an unusual cessation of activity prior to the close).

I have a feeling I'm missing something. How might I go about debugging this further?

@Havvy
Copy link
Member

Havvy commented Mar 17, 2015

I'm not sure why that would happen unless you're using one of the versions of irc-socket with poor timeout handling. Actually, it's still somewhat poor (though you say there's no unusual cessation of activity, so the current poor handling won't close in that case).

What version of irc-socket are you using? Check with npm ls. If it's not v.2.3.2, you need to update.

If you want to catch timeouts when they happen, try adding this line somewhere.

client.socket.on("timeout", function () { client.error("Socket timed out."); });

@alienth
Copy link
Author

alienth commented Mar 17, 2015

I'm on 2.3.2. Will try catching the timeout and will letcha know. Thanks!

@Havvy
Copy link
Member

Havvy commented May 2, 2015

Did you ever find anything?

@alienth
Copy link
Author

alienth commented May 2, 2015

It was indeed a socket timeout. Sorry for not updating the ticket! I'm guessing that irc-socket simply isn't retrying properly.

@Havvy Havvy closed this as completed Jan 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants