[03:15:45] <wm-bot>	 !log tools.stewardbots <anticomposite> ./stewardbots/StewardBot/manage.sh restart # Ping timeout not noticed by bot
[03:15:47] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL
[03:16:33] <wm-bot>	 !log tools.stewardbots <anticomposite> ./stewardbots/StewardBot/manage.sh restart # Ping timeout not noticed by bot
[03:16:34] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL
[03:17:14] <wm-bot>	 !log tools.stewardbots <anticomposite> ./SULWatcher/manage.sh restart # all bots down
[03:17:15] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL
[03:26:38] <AntiComposite>	 really need to figure out how to make these bots restart themselves on ping timeout
[15:42:03] <danilo>	 the problem is the bots don't know they were disconnected from IRC, it seems the connection get muted, they don't even know the connection was closed, that is why they delay to auto restart
[15:47:03] <wm-bot>	 !log tools.bridgebot <lucaswerkmeister> Double IRC messages to other bridges
[15:47:05] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.bridgebot/SAL
[15:52:46] <danilo>	 a way to force the bots to acknowledge the connection was broken is count the time sice the last received PING or PONG message from IRC server, if the time is more than 2 minutes the connection probably got muted, if it is more than 6 minutes the IRC server probably closed the connection by ping timeout
[15:56:31] <danilo>	 I made the second wmopbot connection (wmopbot2) warn when that time is more than 3 minutes, and those warns are always followed by a ping timeout
[22:46:27] <wm-bot>	 !log tools.stewardbots <anticomposite> ./SULWatcher/manage.sh restart # all bots down
[22:46:29] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL