[weewx-user] Re: WeeWX Watchdog, latest improvements
My fresh install is working well. I'm very happy with the operation. Now all that remains is correcting line 30 of the script to "weewx_status" I'm unable to contact the author, if someone else can it would be appreciated On Monday, October 19, 2020 at 8:16:44 PM UTC-5 Bill Arthur wrote: > I'm setting up remote weather sites so this is an essential for me. > Unfortunately I can't get it to work yet. > But I believe I've found an error: > In the lines below, the sixth line should say weewx_status rather than > weewx_start > > # weewx stop, start commands -- these depend on your setup > weewx_stop="/etc/init.d/weewx stop" > #weewx_stop="sudo systemctl stop weewx" > weewx_start="/etc/init.d/weewx start" > #weewx_start="sudo systemctl start weewx" > weewx_start="/etc/init.d/weewx status" > #weewx_status="systemctl status weewx" > #host restart command > host_restart="shutdown -r now" > #host_restart="sudo shutdown -r now" > > I'm going to start a fresh install tonight. In all my troubleshooting I've > probably honked up something. I went from it having no response to now > rebooting every 20 minutes. > > On Monday, May 6, 2019 at 6:02:57 PM UTC-5 le...@isylum.org wrote: > >> Hey, WeeWX'ers! =D >> >> Lots of improvements made to my watchdog script(s). >> >> 1) wunderfixer is now decoupled, except in conjunction with an outage. >> >> It means that even if dowufixer=1 (enabled), it will only run if it is >> within a certain time-frame after an outage (watchdogsecs * repeatwufixer). >> With the defaults, wunderfixer runs every 10 minutes, six times, i.e. >> spread over an hour after an outage. >> >> 2) A separate weewx_wunderfixer wrapper is provided to run separately >> twice a day. >> See readme for recommendations. This change and #1 above is in the >> spirit of lowering the amount of "gratuitous" calls to WU infrastructure, >> while still attempting to keep WU up-to-date a soon as possible after an >> outage. The main purpose of the weewx_wunderfixer is to compute today's >> and yesterday's dates and run against both, just to be extra sure that >> there are no gaps on the WU side. Decoupling now means those actions only >> occur twice a day, instead of every watchdogsecs (e.g. every 10 minutes by >> default), plus a default of 6 more times after an outage. >> >> 3) The running status of weewx is now explicitly checked, which is in >> part to catch an outage sooner, in case weewx crashed very recently after a >> cron interval. >> A similar check is now added after a weewx restart attempt, which avoids >> a double watchdogsecs wait (allows back to back weewx restart and host >> reboot remediations, which is especially nice in the case of a USB / >> firmware hang). >> >> 4) Improved and more consistent logging with a running history of status >> and remediation steps the beginning of the current pass of weewx_watchdog. >> >> That one proved more challenging than expected due to a 1024 line-length >> limitation somewhere in the middle between the host and my inbox. A simple >> "fmt -s -w 1024" did the trick. I woulda had this update out sooner, were >> it not for that one! LOL >> >> The latest 1.1.0 version is over here: >> >> https://github.com/UberEclectic/weewx/tree/watchdog/examples/watchdog >> >> Regards, >> \Leon >> -- >> Leon Shaner :: Dearborn, Michigan (iPad Pro) >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/140157eb-5feb-4429-9c14-f2000e5bff63n%40googlegroups.com.
[weewx-user] Re: WeeWX Watchdog, latest improvements
I'm setting up remote weather sites so this is an essential for me. Unfortunately I can't get it to work yet. But I believe I've found an error: In the lines below, the sixth line should say weewx_status rather than weewx_start # weewx stop, start commands -- these depend on your setup weewx_stop="/etc/init.d/weewx stop" #weewx_stop="sudo systemctl stop weewx" weewx_start="/etc/init.d/weewx start" #weewx_start="sudo systemctl start weewx" weewx_start="/etc/init.d/weewx status" #weewx_status="systemctl status weewx" #host restart command host_restart="shutdown -r now" #host_restart="sudo shutdown -r now" I'm going to start a fresh install tonight. In all my troubleshooting I've probably honked up something. I went from it having no response to now rebooting every 20 minutes. On Monday, May 6, 2019 at 6:02:57 PM UTC-5 le...@isylum.org wrote: > Hey, WeeWX'ers! =D > > Lots of improvements made to my watchdog script(s). > > 1) wunderfixer is now decoupled, except in conjunction with an outage. > > It means that even if dowufixer=1 (enabled), it will only run if it is > within a certain time-frame after an outage (watchdogsecs * repeatwufixer). > With the defaults, wunderfixer runs every 10 minutes, six times, i.e. > spread over an hour after an outage. > > 2) A separate weewx_wunderfixer wrapper is provided to run separately > twice a day. > See readme for recommendations. This change and #1 above is in the spirit > of lowering the amount of "gratuitous" calls to WU infrastructure, while > still attempting to keep WU up-to-date a soon as possible after an outage. > The main purpose of the weewx_wunderfixer is to compute today's and > yesterday's dates and run against both, just to be extra sure that there > are no gaps on the WU side. Decoupling now means those actions only occur > twice a day, instead of every watchdogsecs (e.g. every 10 minutes by > default), plus a default of 6 more times after an outage. > > 3) The running status of weewx is now explicitly checked, which is in > part to catch an outage sooner, in case weewx crashed very recently after a > cron interval. > A similar check is now added after a weewx restart attempt, which avoids a > double watchdogsecs wait (allows back to back weewx restart and host reboot > remediations, which is especially nice in the case of a USB / firmware > hang). > > 4) Improved and more consistent logging with a running history of status > and remediation steps the beginning of the current pass of weewx_watchdog. > > That one proved more challenging than expected due to a 1024 line-length > limitation somewhere in the middle between the host and my inbox. A simple > "fmt -s -w 1024" did the trick. I woulda had this update out sooner, were > it not for that one! LOL > > The latest 1.1.0 version is over here: > > https://github.com/UberEclectic/weewx/tree/watchdog/examples/watchdog > > Regards, > \Leon > -- > Leon Shaner :: Dearborn, Michigan (iPad Pro) > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/22b57057-5a00-45b1-8d3f-276f582f4775n%40googlegroups.com.
[weewx-user] Re: WeeWX Watchdog, latest improvements
Having the hardest time posting attachments -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9e2c7fd4-a988-4344-a26e-0874e9785c64n%40googlegroups.com. Oct 18 00:00:57 OpiQ-4 rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="370" x-info="https://www.rsyslog.com;] rsyslogd was HUPed Oct 18 00:00:57 OpiQ-4 rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="370" x-info="https://www.rsyslog.com;] rsyslogd was HUPed Oct 18 00:00:57 OpiQ-4 systemd[1]: logrotate.service: Succeeded. Oct 18 00:00:57 OpiQ-4 systemd[1]: Started Rotate log files. Oct 18 00:00:58 OpiQ-4 systemd[1]: man-db.service: Succeeded. Oct 18 00:00:58 OpiQ-4 systemd[1]: Started Daily man-db regeneration. Oct 18 00:02:01 OpiQ-4 CRON[1365]: (root) CMD (/usr/local/sbin/weewx_watchdog) Oct 18 00:02:01 OpiQ-4 root[1375]: WeeWX: Watchdog WeeWX is NOT running!!! Oct 18 00:02:01 OpiQ-4 root[1379]: WeeWX: Watchdog Restart was NOT attempted (last restart was too recent). Oct 18 00:02:01 OpiQ-4 root[1383]: WeeWX: Watchdog REBOOT was NOT attempted (last REBOOT was too recent). Oct 18 00:05:19 OpiQ-4 weewx[757] INFO weewx.manager: Added record 2020-10-18 00:05:00 CDT (1602997500) to database 'weewx.sdb' Oct 18 00:05:19 OpiQ-4 weewx[757] INFO weewx.manager: Added record 2020-10-18 00:05:00 CDT (1602997500) to daily summary in 'weewx.sdb' Oct 18 00:05:21 OpiQ-4 weewx[757] INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 2.02 seconds Oct 18 00:05:22 OpiQ-4 weewx[757] INFO weewx.imagegenerator: Generated 15 images for report SeasonsReport in 1.07 seconds Oct 18 00:05:22 OpiQ-4 weewx[757] INFO weewx.reportengine: Copied 0 files to /var/www/html/weewx Oct 18 00:07:37 OpiQ-4 dbus-daemon[819]: [session uid=1000 pid=819] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.7' (uid=1000 pid=876 comm="pcmanfm --desktop --profile LXDE-pi ") Oct 18 00:07:37 OpiQ-4 systemd[766]: Starting Virtual filesystem metadata service... Oct 18 00:07:37 OpiQ-4 dbus-daemon[819]: [session uid=1000 pid=819] Successfully activated service 'org.gtk.vfs.Metadata' Oct 18 00:07:37 OpiQ-4 systemd[766]: Started Virtual filesystem metadata service. Oct 18 00:07:53 OpiQ-4 dbus-daemon[819]: [session uid=1000 pid=819] Activating service name='ca.desrt.dconf' requested by ':1.21' (uid=1000 pid=1450 comm="mousepad /var/log/weewx.log ") Oct 18 00:07:53 OpiQ-4 dbus-daemon[819]: [session uid=1000 pid=819] Successfully activated service 'ca.desrt.dconf' Oct 18 00:10:16 OpiQ-4 systemd[1]: Starting Cleanup of Temporary Directories... Oct 18 00:10:16 OpiQ-4 systemd[1]: systemd-tmpfiles-clean.service: Succeeded. Oct 18 00:10:16 OpiQ-4 systemd[1]: Started Cleanup of Temporary Directories. Oct 18 00:10:30 OpiQ-4 weewx[757] INFO weewx.manager: Added record 2020-10-18 00:10:00 CDT (1602997800) to database 'weewx.sdb' Oct 18 00:10:30 OpiQ-4 weewx[757] INFO weewx.manager: Added record 2020-10-18 00:10:00 CDT (1602997800) to daily summary in 'weewx.sdb' Oct 18 00:10:32 OpiQ-4 weewx[757] INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 1.96 seconds Oct 18 00:10:33 OpiQ-4 weewx[757] INFO weewx.imagegenerator: Generated 15 images for report SeasonsReport in 1.08 seconds Oct 18 00:10:33 OpiQ-4 weewx[757] INFO weewx.reportengine: Copied 0 files to /var/www/html/weewx Oct 18 00:12:01 OpiQ-4 CRON[1505]: (root) CMD (/usr/local/sbin/weewx_watchdog) Oct 18 00:12:01 OpiQ-4 root[1515]: WeeWX: Watchdog WeeWX is NOT running!!! Oct 18 00:12:01 OpiQ-4 root[1520]: WeeWX: Watchdog Restart was NOT attempted (last restart was too recent). Oct 18 00:12:01 OpiQ-4 root[1524]: WeeWX: Watchdog REBOOT was NOT attempted (last REBOOT was too recent). Oct 18 00:15:20 OpiQ-4 weewx[757] INFO weewx.manager: Added record 2020-10-18 00:15:00 CDT (1602998100) to database 'weewx.sdb' Oct 18 00:15:20 OpiQ-4 weewx[757] INFO weewx.manager: Added record 2020-10-18 00:15:00 CDT (1602998100) to daily summary in 'weewx.sdb' Oct 18 00:15:23 OpiQ-4 weewx[757] INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 2.00 seconds Oct 18 00:15:24 OpiQ-4 weewx[757] INFO weewx.imagegenerator: Generated 15 images for report SeasonsReport in 1.13 seconds Oct 18 00:15:24 OpiQ-4 weewx[757] INFO weewx.reportengine: Copied 0 files to /var/www/html/weewx Oct 18 00:17:01 OpiQ-4 CRON[1544]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 18 00:20:28 OpiQ-4 weewx[757] INFO weewx.manager: Added record 2020-10-18 00:20:00 CDT (1602998400) to database 'weewx.sdb' Oct 18 00:20:28 OpiQ-4 weewx[757] INFO weewx.manager: Added record 2020-10-18 00:20:00 CDT (1602998400) to daily summary in 'weewx.sdb' Oct 18 00:20:31
[weewx-user] Re: WeeWX Watchdog, latest improvements
On Sunday, October 18, 2020 at 12:58:13 AM UTC-5 Bill Arthur wrote: > I love this watchdog, but can't get it to work. > > As in the log, it runs but doesn't see WeeWx running. This time it ran > about 20 minutes then WeeWx exited. I restarted it shortly thereafter. > > My application is remote, without internet so I commented out the email. > > Any idea what I am missing here? > > (not a good night for me, keep getting errors when posting) > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/c7186fd3-1f05-407e-af20-088c6028d33fn%40googlegroups.com. weewx_watchdog Description: application/shellscript
[weewx-user] Re: WeeWX Watchdog, latest improvements
I love this watchdog, but can't get it to work. As in the log, it runs but doesn't see WeeWx running. This time it ran about 20 minutes then WeeWx exited. I restarted it shortly thereafter. My application is remote, without internet so I commented out the email. Any idea what I am missing here? (not a good night for me, keep getting errors when posting) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/543bddca-305f-4117-b5ab-4bcac529c7f2n%40googlegroups.com.
