**** BEGIN LOGGING AT Sat Feb 16 02:59:57 2019
Feb 16 06:35:58 <Vajb> sicelo: First it was missing sim all the time, but now that is rare. It just loses whole network for few seconds and it comes back. Syslog show a lot of "unexpected cmt-restart".
Feb 16 06:37:14 <Vajb> by losing network I mean that that pile of bars disappears completely and also 3G text under it disappears.
Feb 16 06:38:22 <Vajb> I can provide syslog later if anyone is interested to take a look.
Feb 16 06:39:53 <Vajb> in my mind this does not seem like bad antenna connection because I usually have full stack of bars.
Feb 16 07:17:04 <KotCzarny> where do you get that cmt log?
Feb 16 07:17:14 <KotCzarny> some command or its saved somewhere?
Feb 16 07:18:52 <sicelo> syslog, i think :-)
Feb 16 07:19:03 <sicelo> ah, yes, he also said so
Feb 16 07:21:05 <KotCzarny> does it need to be installed?
Feb 16 07:21:53 <KotCzarny> i mean installed and configured in some special way
Feb 16 07:22:06 <sicelo> no.
Feb 16 07:30:00 <Vajb> yes, syslog
Feb 16 07:46:33 <KotCzarny> i guess it would eat some battery
Feb 16 07:47:05 <KotCzarny> also, would be interresting to write some popup when cmd errors are detected
Feb 16 07:59:40 <Maxdamantus> I have syslogd start on boot.
Feb 16 07:59:50 <Maxdamantus> All you have to do is run `syslogd` as root.
Feb 16 08:15:27 <Vajb> same here. It grows pretty fast lately.
Feb 16 08:16:00 <Maxdamantus> Seems to get rotated and deleted by default though.
Feb 16 08:16:35 <KotCzarny> only if you have logrotate, i guess
Feb 16 08:17:01 <Maxdamantus> I didn't do anything to get it to happen.
Feb 16 08:17:47 <Maxdamantus> Doesn't seem to be running logrotate. I suspect it's probably syslogd itself that removes them.
Feb 16 08:19:33 <KotCzarny> normal syslogd just logs
Feb 16 08:19:37 <Vajb> Maxdamantus: how big does your file get?
Feb 16 08:19:43 <KotCzarny> might be some syslog-ng or something
Feb 16 08:20:05 <Vajb> Mine grows to several Mb and then I just stop syslog remove file and start syslog again
Feb 16 08:35:58 <Maxdamantus> Vajb: the previous file is 200 KiB
Feb 16 08:36:35 <Maxdamantus> Vajb: not sure if it splits based on size or based on date, but it just has "messages", which is what it's currently appending to, and "messages.0" which was the previous file.
Feb 16 08:36:48 <Maxdamantus> and it's actually just busybox's syslogd.
Feb 16 08:37:25 <KotCzarny> did you configure it for some log rotation?
Feb 16 08:37:25 <Maxdamantus> The --help indicates that it is indeed busybox's syslogd that does the rotation.
Feb 16 08:37:41 <KotCzarny> i dont remember it having such feature by default
Feb 16 08:37:47 <Maxdamantus> No. I just run the command "syslogd" in my boot script.
Feb 16 08:38:21 <Maxdamantus> The --help seems to indicate that that's the default behaviour.
Feb 16 08:38:29 <KotCzarny> nice to know
Feb 16 08:38:30 <KotCzarny> thanks
Feb 16 08:38:53 <Maxdamantus> "N rotated logs to keep (default:1, ..."
Feb 16 08:39:05 <KotCzarny> i might actually implement the logging to find out if mine troubles (which luckily stopped recently) have the same cause
Feb 16 08:39:16 <Maxdamantus> "Max size (KB) before rotation (default:200KB, ..."
Feb 16 08:39:31 <KotCzarny> maxd: is it bb from repo or self compiled?
Feb 16 08:39:39 <Maxdamantus> KotCzarny: just from repo.
Feb 16 08:39:42 <KotCzarny> thx
Feb 16 08:40:49 <Maxdamantus> 3:1.10.2.legal-1osso31+0cssu0
Feb 16 08:41:02 <Maxdamantus> (manually typed, might be inexact)
Feb 16 08:41:32 <Maxdamantus> It's probably just whatever you'd get from the cssu or community repository or whatever it is.
Feb 16 08:41:39 * Maxdamantus can't remember how those worked.
Feb 16 09:45:11 <DocScrutinizer05> sysklogdf or ksyslogd or somesuch
Feb 16 09:45:38 <DocScrutinizer05> pulls in 1 or 2 other dependencies
Feb 16 09:47:07 <DocScrutinizer05> logging to anything other than rootfs gets tricky since logging is started before mounting
Feb 16 09:47:40 <DocScrutinizer05> and iirc it comes with sort of logrotate during reboot
Feb 16 09:50:42 <Maxdamantus> I just have it in init.d/rcS
Feb 16 09:50:59 <Maxdamantus> which is run after everything's mounted.
Feb 16 09:51:38 <Maxdamantus> I don't really care too much about missing messages on boot. Probably better to avoid all that load at that time anyway.
Feb 16 09:51:57 <Maxdamantus> Just useful being able to check the log if I notice the system behaving strangely.
Feb 16 09:57:43 <Vajb> hmm I have default syslogd started at boot time, but it doesn't do any cycling
Feb 16 09:58:11 <Maxdamantus> Is it busybox? ls -l `which syslogd`
Feb 16 09:59:01 <Vajb> Installed: 1.5-5maemo7+0m5
Feb 16 09:59:07 <Vajb> sysklogd
Feb 16 09:59:40 <Vajb> I don't have syslogd
Feb 16 10:00:18 <sixwheeledbeast> upstart is pretty easy to add jobs too
Feb 16 10:00:54 <Vajb> does it come with busybox-power package?
Feb 16 10:01:07 <Maxdamantus> Vajb: try `busybox syslogd --help`
Feb 16 10:01:24 <Maxdamantus> Vajb: if that works, could just run it like that.
Feb 16 10:01:41 <Maxdamantus> `dpkg -S /sbin/syslogd` shows nothing, so maybe I made the symlink myself.
Feb 16 10:01:57 <Maxdamantus> I have a feeling that dpkg is sometimes weird with these sorts of paths though.
Feb 16 10:02:50 <Maxdamantus> It's not busybox power afaict
Feb 16 10:04:35 <Maxdamantus> Oh, it is busybox-power.
Feb 16 10:04:52 <Maxdamantus> Was confused by the "diversion" messages.
Feb 16 10:05:46 <Vajb> applet not found
Feb 16 10:06:37 <Maxdamantus> Yeah, so I guess it's only in the busybox-power one.
Feb 16 10:06:47 <Vajb> yes I thought so because I did apt-cache search syslogd and busybox-power showed up
Feb 16 10:07:01 <Maxdamantus> and maybe it does some postinstall stuff to make the symlinks
Feb 16 10:07:10 <sixwheeledbeast> syslogd is only provided by busybox-power
Feb 16 10:07:34 <sixwheeledbeast> sysklogd is a package on it's own.
Feb 16 10:07:51 <sixwheeledbeast> ~pkg
Feb 16 10:08:31 <sixwheeledbeast> ~botdown
Feb 16 10:09:03 <buZz> ~lightacandleforlostbot
Feb 16 10:09:37 <Vajb> and you said it splits them at 200kb
Feb 16 10:09:59 <Vajb> I guess my 4Mb syslog is a bit too much.
Feb 16 10:10:05 <Maxdamantus> Yeah, by default.
Feb 16 10:10:27 <Maxdamantus> I suspect sysklogd will also have some options for that.
Feb 16 10:10:44 <Maxdamantus> just happens that busybox has 200 KiB by default.
Feb 16 10:12:15 * Maxdamantus likes that the expectation with the busybox version is that the "configuration" is just specified in the command line.
Feb 16 10:12:36 * Maxdamantus wishes more programs did that. *cough* nbd-server *cough*
Feb 16 12:56:44 <Vajb> huh?
Feb 16 12:57:13 <Vajb> I just found a way instantly lose network and get missing sim icon....
Feb 16 13:22:18 <Vajb> interesting
Feb 16 13:22:47 <Vajb> when ever I try to send group message in pidgin device shows missing sim icon
Feb 16 13:24:31 <Vajb> https://pastebin.com/raw/i4mezm5u
Feb 16 13:24:37 <Vajb> syslog from that
Feb 16 13:42:15 <sixwheeledbeast> cellular: ssc[786]: Unexpected modem reset, waiting for modem reboot
Feb 16 13:42:27 <Vajb> yup
Feb 16 13:44:31 <Vajb> few times it went to modem restart 10 of 10 and then only option is reboot device
Feb 16 14:41:26 <sixwheeledbeast> I can still only think of everything said before to try and fix. Battery, SIM, reflash fiasco, aerial contacts loose.
Feb 16 14:45:48 <sixwheeledbeast> If it's the usual modem hardware issue the only real fix is reballing. Normally in this case you can reproduce the sim error by flexing the device. 
Feb 16 14:46:49 <sixwheeledbeast> Doing a certain action like sitting with it in your pocket will trigger it for example.
Feb 16 15:34:39 <sicelo> and typing (in pidgin) might be a form of flexing ... if the board is perhaps now slightly bent
Feb 16 15:40:01 <KotCzarny> irc would trigger it too then
Feb 16 15:40:02 <KotCzarny> i guess
Feb 16 15:43:48 <sicelo> if he types faster/harder with the gf on FB (pidgin) than he does to us :)
Feb 16 16:13:03 <sixwheeledbeast> o.O
Feb 16 21:49:38 <Vajb> haha good speculation sicelo, but it was group chat what triggered it last time
Feb 16 21:49:48 <Vajb> but happens with irc too.
Feb 16 21:55:05 <sicelo> :)
Feb 16 21:58:37 <Vajb> I consulted the service manual today to see how to remove cellular antenna. It seemed that I have to take whole device apart to remove it.
Feb 16 21:59:10 <Vajb> A bit too much of a hassle.
Feb 16 22:00:17 <sicelo> you actually should be able to take it out without disassembling entire device, although doing so is likely better to avoid breaking anything
Feb 16 22:05:07 <Vajb> well it sure sounds like taking whole device apart is more risky :p
Feb 16 22:05:38 <Vajb> but I can try with my other device and see how it folds out
Feb 16 22:08:31 <sicelo> it's not risky at all. anyone can do it. really
**** ENDING LOGGING AT Sun Feb 17 02:59:57 2019