| 21:56.17 | *** join/#infobot infobot (~infobot@rikers.org) |
| 21:56.17 | *** topic/#infobot is Welcome to the infobot channel || Latest version: 1.5.3 @ https://sourceforge.net/project/showfiles.php?group_id=2241 || SVN: 1.5.4 http://infobot.svn.sourceforge.net/svnroot/infobot/ || Blootbot merged into infobot || apt/ibot/infobot/purl run by TimRiker |
| 21:56.17 | *** mode/#infobot [+o infobot] by ChanServ |
| 21:56.43 | DocScrutinizer05 | wow, and even fast as usual at joining channels |
| 21:57.02 | TimRiker | dunno what was up. the infobot connection was not going through. I restarted again and it seems to be working. |
| 21:57.50 | TimRiker | ~chaninfo |
| 21:57.50 | infobot | 121/121 channels, 4615 users, 3559 unique: #debian/1678, #kde/501, #gsoc/281, #devuan/223, #asterisk/184, #maemo/152, #oe/142, #wowuidev/135, #wowace/89, #neo900/80, #arm-netbook/56, #utah/55, #cubieboard/52, #harmattan/51, #bzflag/48, #qi-hardware/45, #meego/43, #wowhead/42, #asterisk-dev/41, #elinux/39, #curseforge/39, #openmoko/37, #maemo-ssu/36, #webos-internals/32, #openmoko-cdevel/29, #brlcad/25, #slug/22, #uphpu/22, #gllug/19, ... |
| 21:58.05 | DocScrutinizer05 | [2017-07-18 Tue 18:11:18] <infobot> 27/119 channels, 2418 users, 2261 unique: #debian/1708, #kde/510, #curseforge/38, #openmoko/37, #debianppc/16, ##lds/13, |
| 21:58.06 | DocScrutinizer05 | [2017-07-18 Tue 18:13:52] <DocScrutinizer05> ~+chaninfo |
| 21:58.08 | DocScrutinizer05 | [2017-07-18 Tue 18:14:26] <DocScrutinizer05> ~+chaninfo |
| 21:58.09 | DocScrutinizer05 | [2017-07-18 Tue 18:14:36] <infobot> 121/121 channels, 4648 users, 3603 unique: #debian/1706, #kde/510, #gsoc/288, #devuan/219, #asterisk/191, #maemo/153, #oe/140, |
| 21:59.06 | DocScrutinizer05 | ooh that was actually not the slow one. Slow ones took >10 min to join all channels |
| 21:59.26 | TimRiker | /whois infobot should show all the public channels joined. |
| 21:59.43 | DocScrutinizer05 | however note <infobot> 27/119 channels -- the 119 in there |
| 22:00.20 | TimRiker | yeah. I'm not sure what causes the extra channel count. I tried to track it down once, but didn't find it. |
| 22:02.05 | DocScrutinizer05 | except yesterday (where it failed pretty much instantly), the last week or two it took maybe an hour and then one after another the instances went offline, after reboot |
| 22:02.28 | DocScrutinizer05 | obviously something ate RAM successively |
| 22:03.22 | DocScrutinizer05 | since the bot itself had no CPU time as high as the lag in its response, I suspected it might be the SQL db backend that does |
| 22:04.18 | DocScrutinizer05 | ~status |
| 22:04.18 | infobot | Since Wed Jul 19 21:55:28 2017, there have been 0 modifications, 0 questions, 0 dunnos, 0 morons and 0 commands. I have been awake for 8m 50s this session, and currently reference 119689 factoids. I'm using about 79108 kB of memory. With 0 active forks. Process time user/system 2.17/0.07 child 0/0 |
| 22:04.25 | TimRiker | 0714.bz2:01:53.56 time taken to join all chans: 8m 14s; rate: 49.4 sec/join |
| 22:04.39 | TimRiker | 0718.bz2:18:23.41 time taken to join all chans: 1m 25s; rate: 8.5 sec/join |
| 22:05.00 | TimRiker | 22:04.39 <TimRiker/#infobot> 0718.bz2:18:23.41 time taken to join all chans: 1m 25s; rate: 8.5 sec/join |
| 22:05.09 | TimRiker | lol |
| 22:05.21 | TimRiker | 21:55.52 time taken to join all chans: 17s; rate: 1.7 sec/join |
| 22:05.25 | DocScrutinizer05 | yeah, that |
| 22:05.38 | TimRiker | sorry, grepping my own comment there... |
| 22:05.38 | DocScrutinizer05 | weird |
| 22:06.17 | TimRiker | most of the log entries show 20-30s for all joins. |
| 22:06.34 | DocScrutinizer05 | join all chans: 17s; rate: 1.7 sec/join ??? that's only 10 chan |
| 22:07.41 | TimRiker | http://infobot.rikers.org/joins.txt |
| 22:07.44 | DocScrutinizer05 | chaninfo seems doesn't really show the channels the bot joined successfully |
| 22:08.47 | DocScrutinizer05 | it's always all = perchan * 10 |
| 22:08.59 | DocScrutinizer05 | in http://infobot.rikers.org/joins.txt |
| 22:09.21 | TimRiker | yep. would be nice to log the count. even the count per nick. |
| 22:09.55 | DocScrutinizer05 | as if the bot had only 10 channels it needs to join |
| 22:10.28 | DocScrutinizer05 | ~status |
| 22:10.28 | infobot | Since Wed Jul 19 21:55:28 2017, there have been 0 modifications, 0 questions, 0 dunnos, 0 morons and 0 commands. I have been awake for 15m this session, and currently reference 119689 factoids. I'm using about 79208 kB of memory. With 0 active forks. Process time user/system 2.83/0.08 child 0/0 |
| 22:10.50 | DocScrutinizer05 | 2.17/0.07 -> 2.83/0.08 |
| 22:11.11 | DocScrutinizer05 | that's ok I think |
| 22:12.50 | DocScrutinizer05 | when it lagged those values were not much higher |
| 22:13.10 | DocScrutinizer05 | <PROTECTED> |
| 22:13.11 | DocScrutinizer05 | [2017-07-18 Tue 18:21:26] <DocScrutinizer05> ~+status |
| 22:13.13 | DocScrutinizer05 | [2017-07-18 Tue 18:21:30] <-- infobot (~infobot@rikers.org) has left this server (Ping timeout: 240 seconds). |
| 22:17.06 | DocScrutinizer05 | btw the maemo infra issues with a million php oobjects eating a billion bytes of RAM was triggered by update to a new php version, iirc |
| 22:18.41 | DocScrutinizer05 | does the bot have throttling in /queries ? If not, I could think of fools running scripts against the bot |
| 22:28.13 | TimRiker | yes. as op, my access bypasses that. |
| 23:09.59 | DocScrutinizer05 | ~status |
| 23:09.59 | infobot | Since Wed Jul 19 21:55:28 2017, there have been 0 modifications, 2 questions, 0 dunnos, 0 morons and 1 command. I have been awake for 1h 14m 31s this session, and currently reference 119689 factoids. I'm using about 79216 kB of memory. With 0 active forks. Process time user/system 7.75/0.18 child 0/0 |
| 23:10.37 | DocScrutinizer05 | TimRiker: what means 'lobotomize'? |
| 23:11.32 | DocScrutinizer05 | err 'lobotomy' |
| 23:12.18 | DocScrutinizer05 | does it start a new 'child' process or somesuch? |
| 23:12.21 | TimRiker | ~dict lobotomize |
| 23:12.29 | TimRiker | ~dict lobotomy |
| 23:12.37 | DocScrutinizer05 | or is it a thing about the database |
| 23:12.58 | DocScrutinizer05 | ~+help lobotomy |
| 23:14.06 | DocScrutinizer05 | never used it since I don't understand what it does |
| 23:14.54 | DocScrutinizer05 | prolly wouldn't use it even if I understood, either ;-) |
| 23:15.55 | DocScrutinizer05 | ooh btw, ~weather is dead |
| 23:16.11 | DocScrutinizer05 | prolly the web "API" changed |
| 23:16.47 | DocScrutinizer05 | ~weather eddn |
| 23:17.49 | DocScrutinizer05 | the links in that 'help' are dead or pointless as well ;-) |
| 23:18.22 | DocScrutinizer05 | ~icao |
| 23:18.22 | infobot | rumour has it, icao is an International Civial Aviation Organization code, often useful in finding weather stations. See http://www.ivao.org/db/ss/ to lookup a code. http://en.wikipedia.org/wiki/ICAO_airport_code |
| 23:19.52 | DocScrutinizer05 | https://en.wikipedia.org/wiki/List_of_airports_by_ICAO_code:_E#ED_.E2.80.93_Civil_airports is the only one I found working |
| 23:22.01 | DocScrutinizer05 | anyway EDDN is valid and worked, so I guess whatever web API that plugin is using has changed |