libera/#infobot/ Saturday, 2018-06-09

infobot- Uptime for purl -20:30
infobotNow: 3m 33s running infobot 1.5.4 (SVN) -- linux20:30
infobot1: 59d 8h 41m 19s running infobot 1.5.4 (SVN) -- linux, ended Sun Nov 14 18:39:57 201020:30
infobot2: 57d 3h 9m 23s running infobot 1.5.4 (SVN) -- linux, ended Fri Jun 26 20:39:27 200920:30
infobot3: 53d 8h 24m 4s running infobot 1.5.4 (SVN) -- linux, ended Tue Nov  7 05:34:20 201720:30
Juestobzflag been radied lately as of yesterday20:40
Juestoor so20:40
DocScrutinizer05now if only U had access to sth like iptraf on bot server20:41
Juestoidk if infobot is being affected20:41
Juestowhy, how that could help me?20:41
Juestooh oof20:41
Juestoor you, why do you think you should20:42
DocScrutinizer05bot has connectivity issues, unclear if that's due to (D)DoS or ISP fsckup20:42
DocScrutinizer05en passant I found a bug in  ssh client: doesn't time out when connectivity to server goes down during negotiation20:44
DocScrutinizer05[2018-06-09 Sat 20:02:41] <DocScrutinizer05> where to report a ssh bug? (upstream, also after checking source)  >>client: no timeout in negotiation after server stops responding during negotiation<<
DocScrutinizer05I "fixed" that issue for this one case by using "timeout -s 9 10m ssh" in my keep-alive monitor script20:46
DocScrutinizer05wouldn't like to get a ~30 "zombie" processes per hour, from ssh client hangig forever20:47
DocScrutinizer05this is a bug in ssh client I'm aware of since almost a decade, but today I first time got a ssh -vvv log of it hanging20:48

Generated by 2.17.0 by Marius Gedminas - find it at!