Closed icedream closed 8 years ago
Finally able to track back the issue to a socket timeout on the client side. This should be easy to prevent by using a TCP keep-alive, so no command is actually needed.
Here's an example timestamped log (--timestamp
). Timeouts seem to happen after exactly 10 minutes if the bot is left alone.
bot_1 | 2016-02-16T10:41:18.100Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T10:51:18.091Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T10:51:19.095Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T11:01:19.097Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T11:01:20.100Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T11:11:20.039Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T11:11:21.057Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T11:21:21.110Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T11:21:22.140Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T11:31:22.070Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T11:31:23.096Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T11:41:23.128Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T11:41:24.154Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T11:57:27.148Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T11:57:28.173Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T12:10:27.111Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T12:10:28.138Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T12:20:28.203Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T12:20:29.222Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T12:39:37.146Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T12:39:38.150Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T12:49:38.133Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T12:49:39.135Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T12:59:39.117Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T12:59:40.120Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T13:09:40.101Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T13:09:41.103Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T13:19:41.115Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T13:19:42.118Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T13:33:29.007Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T13:33:30.009Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T13:58:56.120Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T13:58:57.123Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T14:08:57.120Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T14:08:58.123Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T14:33:24.077Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T14:33:25.080Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T14:43:25.132Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T14:43:26.135Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T14:54:04.082Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T14:54:05.085Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T15:04:05.102Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T15:04:06.105Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T15:20:43.073Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T15:20:44.075Z - info: [Main] TS3 query now ready.
bot_1 | 2016-02-16T15:32:01.067Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
bot_1 | 2016-02-16T15:32:02.097Z - info: [Main] TS3 query now ready.
Recent commit did not fix the timeouts...
bot_1 | 2016-02-16T16:54:12.666Z - info: [Main] Connected to TeamSpeak server.
bot_1 | 2016-02-16T17:04:12.136Z - warn: [TS3Client] Connection to TS3 client query interface lost, reconnecting...
This issue supersedes part of #33.
Idling the query connection for too long can lead to the TeamSpeak3 client causing the termination of said connection.
Available solutions:
Fix by making a new connection for each command call.We need the connection to be alive since we use events.