I'd see if it runs better without the checkwifi script. My first suspect is a memory leak caused by the script. Why do you need to keep checking wifi anyway?
On Tuesday, 7 August 2018 01:47:19 UTC+3, Glenn McKechnie wrote: > > Hi Steve, > > Last file to be ftp'd... > Aug 6 07:56:22 raspi2 weewx[2463]: ftpgenerator: ftp'd 41 files in 9.45 > seconds > > weewx is still running... > Aug 6 07:58:01 raspi2 weewx[2463]: restx: PWSWeather: Published record > 2018-08-06 07:58:00 EDT (1533556680) > > It's all downhill from here. > What does this script do? It would help to see its contents as > it seems to be actioned often and the kernel returns an error > message in the next log entry, and in fact kills weewx... > Aug 6 08:00:03 raspi2 /USR/SBIN/CRON[22069]: (pi) CMD (/usr/bin/sudo -H > /usr/local/bin/checkwifi.sh >> /dev/null 2>&1) > [...] > Aug 6 08:01:44 raspi2 ifplugd(wlan0)[1762]: Executing > '/etc/ifplugd/ifplugd.action wlan0 down'. > Aug 6 08:01:54 raspi2 ifplugd(wlan0)[1762]: Program executed successfully. > Aug 6 08:05:48 raspi2 kernel: [1005647.481952] INFO: task > kworker/2:0:21602 blocked for more than 120 seconds. > Aug 6 08:05:50 raspi2 kernel: [1005647.481967] Not tainted > 4.9.33-v7+ #1012 > > And here's the killer. Out of memory error. Weewx gets booted by the > kernel... > Aug 6 08:05:54 raspi2 kernel: [1005653.613593] [26541] 33 26541 > 56956 9 35 0 490 0 apache2 > Aug 6 08:05:54 raspi2 kernel: [1005653.613608] [22228] 0 22228 > 1067 141 6 0 10 0 cron > Aug 6 08:05:54 raspi2 kernel: [1005653.613615] Out of memory: Kill > process 2463 (weewxd) score 899 or sacrifice child > Aug 6 08:05:54 raspi2 kernel: [1005653.613677] Killed process 2463 > (weewxd) total-vm:1059160kB, anon-rss:873956kB, file-rss:1224kB, > shmem-rss:0kB > Aug 6 08:05:54 raspi2 /USR/SBIN/CRON[22232]: (pi) CMD (/usr/bin/sudo -H > /usr/local/bin/checkwifi.sh >> /dev/null 2>&1) > > weewx is never restarted aftre this shutdown, the system seems to be > working as before though. (checkwifi is still doing it's thing!) > > I'd setup pmon (in the weewx examples directory) and see if weewx memory > usage is indeed running away on you. (it will also show general memory > usage) > > > > > Cheers > Glenn > > rorpi - read only raspberry pi & various weewx addons > https://github.com/glennmckechnie > > On 7 August 2018 at 06:51, Steve2Q <ste...@gmail.com <javascript:>> wrote: > >> Hello. I had a crash 11 days 15 hours ago. At that time, I rebooted the >> system and all appeared OK (I posted a log at that time). It just crashed >> again after 11 days 15 hours, which makes me a bit suspicious that >> something more than a bad card is responsible. Attached is a log from >> today. The last file ftp'd was was at 7:56:22. Then at 15:35:42, the date >> changed to Dec 31. I then rebooted the system 15:36:30. >> >> Attached is the log. >> >> Thanks, Steve >> >> -- >> You received this message because you are subscribed to the Google Groups >> "weewx-user" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to weewx-user+...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
