Weewx and alarm.py

104 views
Skip to first unread message

meteo219

unread,
Oct 28, 2022, 8:22:57 PM10/28/22
to weewx-user
Hello Weewx Users,

Is anyone out there using alarm.py to send an email during a weewx shutdown or a weewx crash?  For example, I had the following weewx crash: 

INFO user.sdr: shutdown process /usr/local/bin/rtl_433 -M utc -F json -R 40
INFO user.sdr: shutdown complete
CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is not running
CRITICAL __main__:     ****  Waiting 60 seconds then retrying...
usb 1-1.4: new high-speed USB device number 8 using xhci_hcd
Device not responding to setup address.
usb 1-1.4: Device not responding to setup address.
[460827.904059] usb 1-1.4: device not accepting address 8, error -71

I am currently troubleshooting the USB port / SDR extension cable connecting to my rpi, but I went a few days without data because I didn't know weewx crashed.

In other words, is there something we can use in the expression = " " statement to send an email during a weewx shutdown?

Thanks in advance!

Jeff

Tom Keffer

unread,
Oct 28, 2022, 8:35:18 PM10/28/22
to weewx...@googlegroups.com
Unfortunately, no, you can't do that. The expression can only involve the current packet or archive record.

If a shutdown is a possibility, some sort of process monitoring strategy is probably a better bet. However, I would much rather get to the root cause of the shutdown. There have been instances of weewxd going literally years without a failure.

Can we see farther up in the log?

-tk

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/996ca78d-1613-44c4-8460-98de3a74adf5n%40googlegroups.com.

gjr80

unread,
Oct 28, 2022, 8:35:20 PM10/28/22
to weewx-user
I think using something like alarm.py that is tied to WeeWX to monitor/report on WeeWX operation will be somewhat limiting. I use a bash script that checks the age of one or more files generated by WeeWX. It's run as a cron job every 15 minutes and if the file(s) is/are stale an email is sent.

Gary

Jeff Chabot

unread,
Oct 28, 2022, 10:27:18 PM10/28/22
to weewx...@googlegroups.com
Here is more of the log:

Oct 24 14:16:38 raspberrypi kernel: [460825.316698] usb 1-1.4: USB disconnect, device number 4
Oct 24 14:16:38 raspberrypi kernel: [460825.552037] usb 1-1.4: new high-speed USB device number 5 using xhci_hcd
Oct 24 14:16:38 raspberrypi kernel: [460825.632254] usb 1-1.4: device descriptor read/64, error -71
Oct 24 14:16:39 raspberrypi kernel: [460825.820244] usb 1-1.4: device descriptor read/64, error -71
Oct 24 14:16:39 raspberrypi kernel: [460826.008038] usb 1-1.4: new high-speed USB device number 6 using xhci_hcd
Oct 24 14:16:39 raspberrypi kernel: [460826.088245] usb 1-1.4: device descriptor read/64, error -71
Oct 24 14:16:39 raspberrypi ntpd[3389609]: Soliciting pool server 204.2.134.163
Oct 24 14:16:39 raspberrypi kernel: [460826.276252] usb 1-1.4: device descriptor read/64, error -71
Oct 24 14:16:39 raspberrypi kernel: [460826.384463] usb 1-1-port4: attempt power cycle
Oct 24 14:16:40 raspberrypi kernel: [460826.992057] usb 1-1.4: new high-speed USB device number 7 using xhci_hcd
Oct 24 14:16:40 raspberrypi kernel: [460826.992339] usb 1-1.4: Device not responding to setup address.
Oct 24 14:16:40 raspberrypi ntpd[3389609]: Soliciting pool server 64.62.194.188
Oct 24 14:16:40 raspberrypi kernel: [460827.200296] usb 1-1.4: Device not responding to setup address.
Oct 24 14:16:40 raspberrypi ntpd[3389609]: Soliciting pool server 108.59.2.24
Oct 24 14:16:40 raspberrypi kernel: [460827.408053] usb 1-1.4: device not accepting address 7, error -71
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: rtl_433 version 21.12-155-g73f5a846 branch master at 202209201115 inputs file rtl_tcp RTL-SDR
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Use -h for usage help and see https://triq.org/ for documentation.
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Trying conf file at "rtl_433.conf"...
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Trying conf file at "/root/.config/rtl_433/rtl_433.conf"...
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Trying conf file at "/usr/local/etc/rtl_433/rtl_433.conf"...
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Trying conf file at "/etc/rtl_433/rtl_433.conf"...
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Registered 1 out of 223 device decoding protocols [ 40 ]
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Found Rafael Micro R820T tuner
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Exact sample rate is: 250000.000414 Hz
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: [R82XX] PLL not locked!
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Sample rate set to 250000 S/s.
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Tuner gain set to Auto.
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Tuned to 433.920MHz.
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: cb transfer status: 1, canceling...
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr:
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: LIBUSB_ERROR_NOT_FOUND: Entity not found!
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Check your RTL-SDR dongle, USB cables, and power supply.
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr:
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: WARNING: async read failed (-5).
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr:
Oct 24 14:16:40 raspberrypi weewx[1016677] ERROR user.sdr: Library error -5, exiting...
Oct 24 14:16:40 raspberrypi weewx[1016677] INFO weewx.engine: Main loop exiting. Shutting engine down.
Oct 24 14:16:40 raspberrypi weewx[1016677] INFO weewx.engine: Shutting down StdReport thread
Oct 24 14:16:40 raspberrypi weewx[1016677] INFO user.sdr: shutdown process /usr/local/bin/rtl_433 -M utc -F json -R 40
Oct 24 14:16:40 raspberrypi weewx[1016677] INFO user.sdr: shutdown complete
Oct 24 14:16:40 raspberrypi weewx[1016677] CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is not running
Oct 24 14:16:40 raspberrypi weewx[1016677] CRITICAL __main__:     ****  Waiting 60 seconds then retrying...
Oct 24 14:16:40 raspberrypi kernel: [460827.488068] usb 1-1.4: new high-speed USB device number 8 using xhci_hcd
Oct 24 14:16:40 raspberrypi kernel: [460827.488440] usb 1-1.4: Device not responding to setup address.
Oct 24 14:16:40 raspberrypi kernel: [460827.696296] usb 1-1.4: Device not responding to setup address.
Oct 24 14:16:41 raspberrypi kernel: [460827.904059] usb 1-1.4: device not accepting address 8, error -71
Oct 24 14:16:41 raspberrypi kernel: [460827.904445] usb 1-1-port4: unable to enumerate USB device

It is pretty clear that the rpi lost connection with the SDR dongle which was connected using a USB extender that came with the Nooelec NESDR so it would only cover up one USB port.  The above errors happened twice in one week and each time a reboot of the rpi resolved the issue without unplugging / plugging in the device.  That said, I removed the USB extender to see if that may be the cause.  Right now, the SDR dongle is plugged directly into my rpi and I haven't seen the above usb error since.

You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/NVxxp0ozSPk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEDztfFvyatALYOx7gE07-mx%2BNVD-tjz_szUBP3nap5grw%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages