Susan, No systemd expert by a long shot but I can't say I have ever seen anything like
Dec 11 20:02:08 weather systemd[1]: weewx.service holdoff time over, scheduling restart. before. As for weeWX changing from genStartupRecords to genLoopPackets, as far as I am aware there is no interaction with systemd. When the weeWX engine starts up one of the things it does is have the StdArchive service attempt to do a catchup which involves a call to genStartupRecords. If there are any records to catchup they are downloaded and processed, no notification to anything outside of weeWX. WeeWX then moves on and when the main packet loop is started genLoopPackets takes over. Tom or Matthew may be able to add more, but I am fairly certain weeWX is not dealing with systemd other than the normal daemon start/stop/load/status activities. Gary On Tuesday, 11 December 2018 19:19:53 UTC+10, vk3...@gmail.com wrote: > > (Note: Probably off topic but weewx related) > > I am running weewx (on a raspberry Pi Zero) and I'm seeing something that > I can't explain > > Using my HP1000 driver to access my WS1001, weewx and the driver seem to > be doing what they should in that the driver is reading the old records > that it missed while it was stopped as shown in the following log: > > Dec 11 20:02:02 weather weewx[1181]: manager: added record 2018-12-11 19: > 47:51 AEDT (1544518071) to daily summary in 'weewx.sdb' > > Dec 11 20:02:02 weather weewx[1181]: manager: added record 2018-12-11 19: > 52:51 AEDT (1544518371) to database 'weewx.sdb' > > Dec 11 20:02:02 weather weewx[1181]: manager: added record 2018-12-11 19: > 52:51 AEDT (1544518371) to daily summary in 'weewx.sdb' > > Dec 11 20:02:02 weather weewx[1181]: restx: Meteotemplate: Published > record 2018-12-11 19:47:51 AEDT (1544518071) > > Dec 11 20:02:02 weather weewx[1181]: restx: WOW: Published record 2018-12- > 11 15:37:51 AEDT (1544503071) > > Dec 11 20:02:08 weather systemd[1]: weewx.service holdoff time over, > scheduling restart. > > Dec 11 20:02:08 weather systemd[1]: Stopping weewx weather system... > > Dec 11 20:02:08 weather systemd[1]: Starting weewx weather system... > > Dec 11 20:02:08 weather systemd[1]: Started weewx weather system. > > Dec 11 20:02:09 weather weewx[1274]: engine: Initializing weewx version > 3.6.2 > > Dec 11 20:02:09 weather weewx[1274]: engine: Using Python 2.7.9 (default, > Sep 26 2018, 05:58:52) > > [GCC 4.9.2] > > Dec 11 20:02:09 weather weewx[1274]: engine: Platform Linux-4.9.35+-armv6l > -with-debian-8.0 > > Dec 11 20:02:09 weather weewx[1274]: engine: pid file is /var/run/weewx. > pid > > Dec 11 20:02:09 weather systemd[1]: weewx.service: Supervising process > 1278 which is not our child. We'll most likely not notice when it exits. > > Dec 11 20:02:09 weather weewx[1278]: engine: Using configuration file > /home/weewx/weewx.conf > > Dec 11 20:02:09 weather weewx[1278]: engine: Loading station type HP1000 > (user.HP1000) > > Then after about 2 minutes of weewx running, I get the message from > systemctl that the holdoff time is over and it restarts the service. > > However, when all of the historic records have been read and weewx starts > its main loop, then the service is not restarted by systemctl: > > Dec 11 20:02:10 weather weewx[1278]: engine: Starting up weewx version 3.6 > .2 > > Dec 11 20:02:11 weather weewx[1278]: HP1000: Connected to address ( > '10.1.1.97', 53495) > > Dec 11 20:02:12 weather weewx[1278]: HP1000: Established contact at 11/12/ > 18 20:02:12 > > Dec 11 20:02:12 weather weewx[1278]: HP1000: Retrieving startup records > > Dec 11 20:02:30 weather weewx[1278]: engine: Starting main packet loop. > > Dec 11 20:03:22 weather wpa_supplicant[453]: wlan0: WPA: Group rekeying > completed with b8:8d:12:5f:bf:7b [GTK=CCMP] > > Dec 11 20:04:00 weather python[705]: INFO:apscheduler.executors.default: > Running job "bomIRJob (trigger: cron[minute='4-55/10'], next run at: > 2018-12-11 20:04:00 AEDT)" (scheduled at 2018-12-11 20:04:00+11:00) > > Dec 11 20:04:00 weather animatedgif.py[705]: Running BoM IR Satellite at > 11/12/2018 20:04:00 > > Dec 11 20:04:00 weather python[705]: INFO:apscheduler.executors.default: > Running job "bomRadarJob (trigger: cron[minute='4-58/6'], next run at: > 2018-12-11 20:04:00 AEDT)" (scheduled at 2018-12-11 20:04:00+11:00) > > Dec 11 20:04:00 weather animatedgif.py[705]: Running BoM Radar at 11/12/ > 2018 20:04:00 > > Dec 11 20:04:05 weather python[705]: INFO:apscheduler.executors.default: > Job "bomRadarJob (trigger: cron[minute='4-58/6'], next run at: 2018-12-11 > 20:10:00 AEDT)" executed successfully > > Dec 11 20:05:01 weather CRON[1284]: pam_unix(cron:session): session > opened for user root by (uid=0) > > Dec 11 20:05:01 weather CRON[1288]: (root) CMD (command -v debian-sa1 > > /dev/null && debian-sa1 1 1) > > Dec 11 20:05:01 weather CRON[1284]: pam_unix(cron:session): session > closed for user root > > Dec 11 20:05:24 weather weewx[1278]: manager: added record 2018-12-11 20: > 05:00 AEDT (1544519100) to database 'weewx.sdb' > > Dec 11 20:05:24 weather weewx[1278]: manager: added record 2018-12-11 20: > 05:00 AEDT (1544519100) to daily summary in 'weewx.sdb' > > You can see by the timestamps that the service is allowed to run. > > Does anyone know what weewx does when in the main packet loop that tells > systemctl that the service is running in the 'genLoopPackets' area that it > does not do in the 'genStartuprecords' space? > > Susan > > > -- 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.
