-
Notifications
You must be signed in to change notification settings - Fork 103
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
Hubot instance does not reconnect on restart of Prosody server #87
Comments
No idea, I've never used that xmpp server before. If you want to dig in more, this code handles attempting to reconnect. |
I have the same issue with an OpenFire server whenever the server is shut down or restarted. My debug logs show pings with no responses, but the bot never seems to timeout the connection and attempt a reconnect, even after the server comes back up. [Mon Jul 10 2017 14:27:54 GMT-0400 (EDT)] DEBUG [sending ping] Normally the response will be something like unto The relevant environment variables are: As seen from the above keepalive logs, I use the default of 30000 ms for the keepalive. From the code you linked, it would seem that on line 84, you set @client.connection.socket.setTimeout 0 Could this be the root cause? The lack of response to pings doesn't seem to trigger a reconnect attempt. |
When I restart my XMPP server (Prosody), my hubot instance does not reconnect automatically.
Instead, the hubot instance keeps trying to ping the server, but does not get a response.
I'm using the following package versions:
And Prosody 0.10.
Any thoughts on what could be the issue? My normal clients reconnect fine.
If you need further information I'd be happy to debug this more.
The text was updated successfully, but these errors were encountered: