| 02:26.47 | *** join/#maemo infobot (ibot@208.53.50.136) |
| 02:26.47 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 02:26.47 | *** mode/#maemo [+v infobot] by ChanServ |
| 02:51.07 | *** join/#maemo Alblasco170223 (~Alblasco1@200.192.212.131) |
| 02:59.00 | *** join/#maemo jbeta6 (~jbeta@y241110.dynamic.ppp.asahi-net.or.jp) |
| 03:09.18 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 03:15.18 | *** join/#maemo Goldman607 (~Goldman60@113.237.227.119) |
| 03:30.05 | *** join/#maemo Sm43 (~Sm4@121-83-6-124f1.hyg2.eonet.ne.jp) |
| 03:37.32 | *** join/#maemo b3nw_ (~b3nw_@211.217.210.44) |
| 03:44.12 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 03:56.12 | *** join/#maemo Kilroo (~Kilroo@98.27.17.253) |
| 05:33.49 | DocScrutinizer05 | folks. a coredump can be done with the process keeping running, right? |
| 05:41.45 | KotCzarny | yes, with gdb |
| 05:42.36 | KotCzarny | (and probably other tools) |
| 05:50.26 | DocScrutinizer05 | yeah, but obviously not with standard signal means |
| 05:50.42 | DocScrutinizer05 | see man 2 signal and man 5 core |
| 05:51.10 | DocScrutinizer05 | both say coredump implies process termination |
| 05:53.08 | DocScrutinizer05 | well, to avoid falling for XY problem: infobot stops for a >2h each night at 00:20 UTC, and neither Tim (owner) nor I have any idea what's causing this. How would you try to tackle this shit? |
| 05:53.46 | KotCzarny | it's not sigcore, but just a type of signals |
| 05:53.52 | KotCzarny | ie. sigquit is core too |
| 05:54.05 | DocScrutinizer05 | I know |
| 05:54.31 | KotCzarny | as for the bot, check cron? |
| 05:54.44 | KotCzarny | or scripts the bot is using, might be some log managing |
| 05:54.53 | KotCzarny | or db rehash |
| 05:55.11 | DocScrutinizer05 | I suggested this to Tim a dozen times already. Even suspected logrotate the culprit. No reply by Tim |
| 05:55.24 | KotCzarny | do you have access to the box? |
| 05:55.30 | DocScrutinizer05 | I need a commandline I demand him doing |
| 05:55.38 | DocScrutinizer05 | no |
| 05:55.51 | KotCzarny | some monitoring then? |
| 05:56.20 | DocScrutinizer05 | now we're talking. What exactly= |
| 05:56.23 | DocScrutinizer05 | ? |
| 05:56.29 | KotCzarny | disk/network usage |
| 05:56.36 | DocScrutinizer05 | meh |
| 05:56.44 | KotCzarny | ie. bot uploading something big |
| 05:56.46 | DocScrutinizer05 | nothing too unusual |
| 05:57.16 | KotCzarny | if it's a bot stoppping responding, it might be some script running and blocking everything else |
| 05:57.28 | KotCzarny | which would mean turning that script to run in parallel might help |
| 05:57.32 | DocScrutinizer05 | to start with, I have no clear indication *why* the bot goes offline |
| 05:59.45 | DocScrutinizer05 | I can remote-reboot the bot and already talked Tim into this reboot providing some diagnostic output. Alas I didn't find the one smart command to show what I need to know, about system status |
| 06:01.21 | KotCzarny | it might be as simple as some script blocking the bot |
| 06:01.42 | KotCzarny | which obviously wouldnt show in most diagnostics |
| 06:01.46 | DocScrutinizer05 | ps doesn't show anything suspicious |
| 06:02.02 | KotCzarny | easiest would be adding some debug log showing what funcs are starting and when |
| 06:02.36 | KotCzarny | and popping that single print in most funcs |
| 06:11.03 | DocScrutinizer05 | would seem like the bot goes OOM |
| 06:12.55 | KotCzarny | which would sound as some script trying to run big data |
| 06:14.17 | DocScrutinizer05 | well yeah. I could speculate all day long. I have no clue what to talk Tim into, to *fix* the issue |
| 06:15.07 | DocScrutinizer05 | ~seen rimriker |
| 06:15.09 | infobot | DocScrutinizer05: i haven't seen 'rimriker' |
| 06:15.13 | DocScrutinizer05 | ~seen timriker |
| 06:15.14 | infobot | timriker <~TimRiker@bzflag/projectlead/TimRiker> was last seen on IRC in channel #infobot, 25d 10h 35m 30s ago, saying: 'added a netstat -ntp|grep perl'. |
| 06:15.34 | KotCzarny | clearly he has no time to fix it, and no one else has the access, which basically boils down to nothing is going to be done |
| 06:16.06 | DocScrutinizer05 | that's a pretty useless revelation |
| 06:16.22 | KotCzarny | but clearly directs to the deeper issue |
| 06:16.32 | DocScrutinizer05 | so??? |
| 06:16.38 | KotCzarny | you can speculate all day long, without results |
| 06:16.44 | DocScrutinizer05 | so??? |
| 06:17.42 | DocScrutinizer05 | do you want to tell me you're short of ideas how to tackle this? Noted |
| 06:18.06 | DocScrutinizer05 | I'm too, right now |
| 06:18.09 | KotCzarny | i've already shared few ideas, but without access they are unusable |
| 06:18.50 | *** join/#maemo flyinprogrammer (~flyinprog@p2021091-ipngn16901marunouchi.tokyo.ocn.ne.jp) |
| 06:19.30 | DocScrutinizer05 | I have 'access', just not the type of access you might think of when you hear the term |
| 06:20.47 | DocScrutinizer05 | >>saying: 'added a netstat -ntp|grep perl'<< is what results from my type of "access", I demanded for a netstat to rule out uplink clogging |
| 06:21.21 | KotCzarny | nah, it more sounds as some homecleaning script running in the bot |
| 06:21.35 | DocScrutinizer05 | and I can trigger this and all the other diagnostic rools by doing a bot reboot |
| 06:21.47 | KotCzarny | which takes a while, doesnt hit big cpu/network, but still blocks further execution |
| 06:21.51 | DocScrutinizer05 | tools* |
| 06:27.14 | DocScrutinizer05 | please check this https://pastebin.com/k2eACYn6 it has some errors that might well be worth a closer look and inverstigation. alas the bot is perl and thus I'm totally lost. /join #infobot for sourcecode etc |
| 06:38.31 | DocScrutinizer05 | I gonna provide a reboot log based on operational state now |
| 06:38.40 | DocScrutinizer05 | ~+status |
| 06:38.40 | infobot | Since Sun Sep 30 02:25:36 2018, there have been 0 modifications, 0 questions, 0 dunnos, 0 morons and 0 commands. I have been awake for 4h 13m 4s this session, and currently reference 119769 factoids. I'm using about 80728 kB of memory. With 0 active forks. Process time user/system 12.89/0.57 child 0/0 |
| 06:44.58 | *** join/#maemo infobot (ibot@208.53.50.136) |
| 06:44.58 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 06:44.58 | *** mode/#maemo [+v infobot] by ChanServ |
| 06:46.37 | KotCzarny | chat.freenode.net should be irc.freenode.com ? |
| 06:48.00 | KotCzarny | check shell ulimits |
| 06:48.19 | KotCzarny | ulimit -a |
| 06:50.52 | DocScrutinizer05 | well, when I want to tell Tim "please add a diagnostics line to check ulinit -a", I need a rationale WHY I think this is a relevant info, what we expect it to be, and what we hope to fix by messing with it |
| 06:51.08 | KotCzarny | Out of memory! |
| 06:51.12 | KotCzarny | this maybe |
| 06:51.48 | KotCzarny | would be interesting to find that string exact in scripts |
| 06:51.49 | DocScrutinizer05 | you seen the timestamps of those loglines in ibot's log? |
| 06:52.14 | KotCzarny | could it could pinpoint the place where it does that big job |
| 06:52.42 | KotCzarny | (although it might be generic perl err msg) |
| 06:53.02 | KotCzarny | timestamps or not, it probably has more than one problem |
| 06:53.11 | DocScrutinizer05 | it is |
| 06:55.28 | DocScrutinizer05 | fsckng bot hangs on reboot!!! >:-( |
| 06:55.30 | KotCzarny | perlmonks link to debug things: https://www.perlmonks.org/?node_id=598685 |
| 06:55.46 | KotCzarny | also suggests checking ulimit |
| 06:58.08 | *** join/#maemo infobot (ibot@208.53.50.136) |
| 06:58.08 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 06:58.08 | *** mode/#maemo [+v infobot] by ChanServ |
| 06:58.13 | DocScrutinizer05 | ~wb |
| 06:58.13 | infobot | It's great to be back! |
| 06:58.21 | DocScrutinizer05 | ~+status |
| 06:58.21 | infobot | Since Sun Sep 30 06:56:10 2018, there have been 0 modifications, 1 question, 0 dunnos, 0 morons and 0 commands. I have been awake for 2m 11s this session, and currently reference 119769 factoids. I'm using about 80264 kB of memory. With 0 active forks. Process time user/system 1.29/0.12 child 0/0 |
| 06:58.34 | DocScrutinizer05 | ~+uptime |
| 07:00.23 | KotCzarny | random crap to debug memory in perl: http://perldoc.perl.org/perldebguts.html#Debugging-Perl-memory-usage |
| 07:01.03 | KotCzarny | might actually be useful if you get a coredump and want to step through it |
| 07:02.36 | KotCzarny | http://perldoc.perl.org/perldebguts.html#Debugging-Perl-Memory-Usage (proper link) |
| 07:02.49 | DocScrutinizer05 | http://laforge.gnumonks.org/blog/20180929-fernvale-discount/ |
| 07:03.49 | KotCzarny | 2g is being killed of around the world |
| 07:03.56 | KotCzarny | might be the reason of lack of interest |
| 07:04.02 | KotCzarny | *off |
| 07:23.08 | DocScrutinizer05 | yep, sure |
| 07:25.44 | DocScrutinizer05 | yet there are amazing things going on, like Michaela Spacefalconia trying to re-release a (Openmoko Freerunner) TI Calypso chipset based 2G modem module |
| 07:27.00 | DocScrutinizer05 | I for one think ^^^ this stuff is more rewarding than Calypso |
| 07:36.59 | *** join/#maemo rpav (~rpav@220.72.81.225) |
| 07:44.07 | *** join/#maemo geaaru_ (~geaaru@151.60.34.196) |
| 07:55.38 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 07:59.11 | *** join/#maemo keithzg (~keithzg@198-48-134-113.cpe.pppoe.ca) |
| 08:02.40 | *** join/#maemo geaaru_ (~geaaru@151.60.57.34) |
| 08:07.18 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 08:55.42 | *** join/#maemo dafox (~dafox@ip3e8380c8.speed.planet.nl) |
| 08:56.43 | *** join/#maemo dafox_ (~dafox@ip3e8380c8.speed.planet.nl) |
| 09:39.38 | *** join/#maemo geaaru__ (~geaaru@151.60.52.38) |
| 10:06.06 | *** join/#maemo ScrumpyJack16 (~ScrumpyJa@softbank126084123241.bbtec.net) |
| 10:07.09 | *** join/#maemo damjan1 (~damjan@nttkyo1413202.tkyo.nt.ngn.ppp.infoweb.ne.jp) |
| 10:17.41 | *** join/#maemo shentey (~shentey@x55b52fdd.dyn.telefonica.de) |
| 11:11.53 | *** join/#maemo Kabouik_ (~kabouik@176.67.169.137) |
| 11:18.56 | *** join/#maemo loophole_ (~loophole_@179.106.105.73) |
| 11:29.16 | *** join/#maemo dom9629 (~dom96@175.200.8.191) |
| 11:32.37 | *** join/#maemo werew (~werew@187.109.209.186) |
| 11:53.43 | *** join/#maemo ONDIE (~ONDIE@62.43.150.226.dyn.user.ono.com) |
| 12:01.49 | *** join/#maemo hurrian (~hurrian@unaffiliated/rikanee) |
| 12:04.35 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 12:21.19 | *** join/#maemo hurrian (~hurrian@unaffiliated/rikanee) |
| 12:49.18 | *** join/#maemo IonutVan_0 (~IonutVan_@110.49.168.75) |
| 12:51.17 | *** join/#maemo redarrow (~redarrow@124.195.212.209) |
| 13:14.00 | *** join/#maemo UnfixedSNIPERJ13 (~UnfixedSN@p57B56322.dip0.t-ipconnect.de) |
| 13:23.17 | *** join/#maemo clemens3_8 (~clemens3_@LFbn-LYO-1-919-88.w86-194.abo.wanadoo.fr) |
| 13:37.18 | *** join/#maemo mhayden4 (~mhayden@LFbn-CLE-1-120-135.w2-3.abo.wanadoo.fr) |
| 13:49.36 | *** join/#maemo camfl20 (~camfl@205.217.249.47) |
| 13:50.48 | *** join/#maemo dddddd5 (~dddddd@124.253.128.34) |
| 14:11.13 | *** join/#maemo tgerczei28 (~tgerczei@dhcp01-018.ctb.ne.jp) |
| 14:16.03 | *** join/#maemo azace20 (~azace@183.96.159.29) |
| 14:18.48 | *** join/#maemo wbs19 (~wbs@186-91-103-243.genericrev.cantv.net) |
| 14:28.20 | *** join/#maemo Cr4zi313 (~Cr4zi3@196.64.116.240) |
| 15:01.06 | *** join/#maemo danshtr|work2 (~danshtr|w@171.35.161.111) |
| 15:04.19 | *** join/#maemo sivik_ (~sivik_@mx-ll-27.130.164-240.dynamic.3bb.co.th) |
| 15:18.05 | *** join/#maemo Kabouik- (~kabouik@176.67.168.147) |
| 15:31.37 | *** join/#maemo Slade29 (~Slade@p5188-ipngn1101kokuryo.gunma.ocn.ne.jp) |
| 15:40.29 | *** join/#maemo geaaru_ (~geaaru@151.60.38.251) |
| 15:46.52 | *** join/#maemo nonzen9 (~nonzen@187.111.220.208) |
| 15:53.55 | *** join/#maemo sterns15 (~sterns@ADijon-652-1-137-122.w90-56.abo.wanadoo.fr) |
| 15:58.40 | *** join/#maemo s0lar1s12 (~s0lar1s@93.183.231.175) |
| 16:11.37 | *** join/#maemo ibrightly2 (~ibrightly@ADijon-652-1-137-122.w90-56.abo.wanadoo.fr) |
| 16:29.48 | *** join/#maemo Adluc15 (~Adluc@softbank126227233014.bbtec.net) |
| 16:33.25 | *** join/#maemo Bent0 (~Bent0@125.161.4.178) |
| 16:53.58 | *** join/#maemo luxifer13 (~luxifer@190.200.248.62) |
| 16:58.11 | *** join/#maemo Kilroo (~Kilroo@98.27.17.253) |
| 17:08.07 | *** join/#maemo Plan_IX16 (~Plan_IX@136.32.94.32) |
| 17:12.28 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 17:36.58 | *** join/#maemo magnuse10 (~magnuse@i121-117-5-119.s41.a020.ap.plala.or.jp) |
| 17:46.04 | *** join/#maemo elder_ (~elder_@host109-150-90-233.range109-150.btcentralplus.com) |
| 18:02.47 | *** join/#maemo geaaru_ (~geaaru@151.60.59.107) |
| 18:27.16 | *** join/#maemo debdrup19 (~debdrup@222.236.150.128) |
| 18:36.36 | *** join/#maemo jumbers5 (~jumbers@186-90-150-203.genericrev.cantv.net) |
| 18:41.47 | *** join/#maemo Eramdam18 (~Eramdam@p2512016-ipngn200610tokaisakaetozai.aichi.ocn.ne.jp) |
| 18:52.37 | *** join/#maemo weebot25 (~weebot@178.43.199.188.ipv4.supernova.orange.pl) |
| 19:31.35 | *** join/#maemo cyp3d8 (~cyp3d@95.182.2.80) |
| 19:31.58 | sicelo | stupid question - but i must ask nonethelese - the telco in my country uses overhead lines, and our area is also prone to lightning strikes in summer. what is the best way (besides disconnecting, of course) to protect the adsl modem/router from this? |
| 19:33.29 | KotCzarny | nothing protects you from direct (or even in neighbourhood) lightning hit |
| 19:33.44 | KotCzarny | my friend had such incident few years ago |
| 19:33.58 | KotCzarny | lightning hit the house 2-3 buildings away |
| 19:34.19 | KotCzarny | his modem way flying across the room leaving sparks and burns trail |
| 19:35.03 | KotCzarny | s/way/was |
| 19:37.46 | sicelo | gosh |
| 19:38.02 | sicelo | at least no one's reported such here |
| 19:38.59 | KotCzarny | i have heard few stories about ethernet networks hung around the neighbourhoods too, those tend to burn routers/switches first |
| 19:39.18 | KotCzarny | so just dont worry and keep your data safe |
| 19:39.44 | KotCzarny | ie. store backups in different locations |
| 19:42.56 | *** join/#maemo wizonesolutions9 (~wizonesol@186.114.124.140) |
| 19:44.36 | sicelo | well our modems dead now. no idea when isp will provide replacement. |
| 19:45.21 | KotCzarny | there are some telephone line isolators, but as i've said, nothing protects from close hit |
| 19:45.47 | KotCzarny | some power strips provide filtering for modem lines |
| 19:46.11 | *** join/#maemo kelkoobenoitr17 (~kelkooben@188.92.189.22) |
| 19:46.12 | sicelo | isp doesn't like those. :) |
| 19:46.36 | KotCzarny | they just have to pass high freqs, while still protecting from voltage spikes |
| 19:46.42 | sicelo | they complained that it causes the signal to be 'sent back' to their more expensive equipment :D |
| 19:46.48 | KotCzarny | rrrright |
| 19:47.07 | sicelo | i never got time to study how they really work to see if their claim was correct (i doubt) |
| 19:50.06 | KotCzarny | that might be true for some cheapo ones |
| 20:04.07 | sicelo | guess we must be sure to disconnect then, assuming storm happens when we're around |
| 20:21.17 | *** join/#maemo blu3r4d0n (~blu3r4d0n@182.149.156.21) |
| 20:24.58 | *** join/#maemo daw14 (~daw@ntaich209061.aich.nt.ngn.ppp.infoweb.ne.jp) |
| 20:28.04 | *** join/#maemo bryceml21 (~bryceml@217santiagord22.codetel.net.do) |
| 20:46.47 | *** join/#maemo fasdfd (~fasdfd@105.108.138.232) |
| 20:46.57 | *** join/#maemo bear`26 (~bear`@i220-109-26-220.s41.a001.ap.plala.or.jp) |
| 20:50.51 | *** join/#maemo dafox_ (~dafox@2a02:a448:c25a:1::1) |
| 21:16.40 | *** join/#maemo buzo9 (~buzo@156.222.160.36) |
| 21:20.20 | *** join/#maemo shentey (~shentey@x4e33f952.dyn.telefonica.de) |
| 21:32.15 | *** join/#maemo synx50820 (~synx508@138.97.145-212.gtidns.com.br) |
| 21:36.45 | *** join/#maemo Janusz8 (~Janusz@148.255.23.217) |
| 21:37.44 | *** join/#maemo pythoneye2 (4db4f4a0@gateway/web/freenode/ip.77.180.244.160) |
| 21:42.02 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 21:50.53 | *** join/#maemo Hat0r17 (~Hat0r@200.84.159.23) |
| 22:41.08 | *** join/#maemo czer00 (~czer00@stespq3502w-lp130-01-67-68-98-114.dsl.bell.ca) |
| 23:00.02 | *** join/#maemo Langoor (~Langoor@152.172.124.38) |
| 23:03.08 | *** join/#maemo rm13 (~rm@138-204-71-14.wantel.net.br) |
| 23:08.05 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 23:16.52 | *** join/#maemo abates_ (~abates_@190-198-13-15.dyn.dsl.cantv.net) |
| 23:26.41 | *** join/#maemo zwiep`21 (~zwiep`@200.192.212.216) |