Weewx stopped working after power outage

113 views
Skip to first unread message

K1IW

unread,
Feb 4, 2023, 11:42:29 AM2/4/23
to weewx-user
We had a brief power interruption yesterday, after which there were no more updates to our weewx web pages.

There are no entries in the system log at all, but the weewx process is running.

I found that if I replace my station type in weewx.conf with "Simulator", then I see the normal activity in the system log and the pages update.  But, when I switch it back to our hardware (WMR9x8), again there is nothing in the system log - even with debug=1.

The equipment is located at a remote site, so I don't have immediate access to it.  I would think if the hardware was down and thus the serial interface wasn't working that I would at least see messages about the connection timing out, but I see nothing.

Does anyone have any suggestions?

Thanks,
Bob

Tom Keffer

unread,
Feb 4, 2023, 3:30:13 PM2/4/23
to weewx...@googlegroups.com
Is there literally no log entries? Or, are there no entries indicating an error? If the latter, post them anyway --- there's almost always some clues. Restart weewx, post the log through the first reporting cycle.

If there is literally nothing in the log, you're going to have to fix that first. It's nearly impossible to debug without it.

-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/0ec9cb20-4aed-453f-a549-1238b1dd0055n%40googlegroups.com.

Bob DeMattia

unread,
Feb 4, 2023, 5:35:15 PM2/4/23
to weewx...@googlegroups.com
When I start it, there are the normal things that you see in the log.  After that, there is nothing.
I just grep'd for "weewx" in my system log file.  Below is everything since the restart at 11:25AM this morning.

I should add that after this problem began, I completely uninstalled weewx and installed it again.  The reinstall did not help.
With one change (changing station_type to "Simulator") it will report normally at the archive interval.

Below the log is the result from a service status command.

-Bob


Feb  4 11:25:59 w1mra systemd: Starting SYSV: start and stop the weewx weather system...
Feb  4 11:25:59 w1mra journal: weewx[16809] INFO __main__: Initializing weewx version 4.10.1
Feb  4 11:25:59 w1mra journal: weewx[16809] INFO __main__: Using Python 2.7.5 (default, Oct 30 2018, 23:45:53) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
Feb  4 11:25:59 w1mra journal: weewx[16809] INFO __main__: Located at /bin/python2
Feb  4 11:25:59 w1mra journal: weewx[16809] INFO __main__: Platform Linux-3.10.0-957.1.3.el7.x86_64-x86_64-with-centos-7.6.1810-Core
Feb  4 11:25:59 w1mra journal: weewx[16809] INFO __main__: Locale is 'en_US.UTF-8'
Feb  4 11:25:59 w1mra journal: weewx[16809] INFO __main__: Using configuration file /etc/weewx/weewx.conf
Feb  4 11:25:59 w1mra journal: weewx[16809] INFO __main__: Debug is 1
Feb  4 11:25:59 w1mra journal: weewx[16809] INFO __main__: PID file is /var/run/weewx.pid
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.engine: Loading station type WMR9x8 (weewx.drivers.wmr9x8)
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.drivers.wmr9x8: driver version is 3.4.1
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.drivers.wmr9x8: sensor map is {'yesterdayRain': 'rain_yesterday', 'extraTemp8': 'temperature_8', 'outHumidity': 'humidity_out', 'extraHumid1': 'humidity_1', 'inTempBatteryStatus': 'battery_status_in', 'rainBatteryStatus': 'battery_status_rain', 'extraTemp5': 'temperature_5', 'extraTemp2': 'temperature_2', 'outTempBatteryStatus': 'battery_status_out', 'inDewpoint': 'dewpoint_in', 'hourRain': 'rain_hour', 'inTemp': 'temperature_in', 'barometer': 'barometer', 'windchill': 'windchill', 'dewpoint': 'dewpoint_out', 'extraTemp7': 'temperature_7', 'rain': 'rain', 'extraHumid6': 'humidity_6', 'extraHumid7': 'humidity_7', 'extraHumid4': 'humidity_4', 'extraHumid5': 'humidity_5', 'extraHumid2': 'humidity_2', 'extraHumid3': 'humidity_3', 'dewpoint5': 'dewpoint_5', 'dewpoint4': 'dewpoint_4', 'extraTemp6': 'temperature_6', 'rainTotal': 'rain_total', 'extraTemp4': 'temperature_4', 'dewpoint8': 'dewpoint_8', 'rainRate': 'rain_rate', 'extraTemp3': 'temperature_3', 'extraHumid8': 'humidity_8', 'extraTemp1': 'temperature_1', 'dewpoint1': 'dewpoint_1', 'dewpoint3': 'dewpoint_3', 'extraBatteryStatus8': 'battery_status_8', 'dewpoint2': 'dewpoint_2', 'extraBatteryStatus2': 'battery_status_2', 'extraBatteryStatus3': 'battery_status_3', 'windBatteryStatus': 'battery_status_wind', 'extraBatteryStatus1': 'battery_status_1', 'extraBatteryStatus6': 'battery_status_6', 'extraBatteryStatus7': 'battery_status_7', 'extraBatteryStatus4': 'battery_status_4', 'extraBatteryStatus5': 'battery_status_5', 'windDir': 'wind_dir', 'outTemp': 'temperature_out', 'windSpeed': 'wind_speed', 'dewpoint0': 'dewpoint_0', 'inHumidity': 'humidity_in', 'rain24': 'rain_24', 'windGust': 'wind_gust', 'dewpoint7': 'dewpoint_7', 'pressure': 'pressure', 'windGustDir': 'wind_gust_dir', 'dewpoint6': 'dewpoint_6'}
Feb  4 11:25:59 w1mra weewx: Starting weewx: [  OK  ]
Feb  4 11:25:59 w1mra systemd: Started SYSV: start and stop the weewx weather system.
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.engine: StdConvert target unit is 0x1
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.wxservices: StdWXCalculate will use data binding wx_binding
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.engine: Archive will use data binding wx_binding
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.engine: Record generation will be attempted in 'hardware'
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.engine: Using archive interval of 120 seconds (specified in weewx configuration)
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.restx: StationRegistry: Station will be registered.
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.restx: Wunderground: Posting not enabled.
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.restx: PWSweather: Posting not enabled.
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.restx: CWOP: Posting not enabled.
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.restx: WOW: Posting not enabled.
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.restx: AWEKAS: Posting not enabled.
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.engine: 'pyephem' not detected, extended almanac data is not available
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO __main__: Starting up weewx version 4.10.1
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.manager: Starting backfill of daily summaries
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.manager: Daily summaries up to date
Feb  4 11:25:59 w1mra journal: weewx[16813] INFO weewx.engine: Starting main packet loop.


[user@w1mra log]$ service weewx status
Checking for weewx: ● weewx.service - SYSV: start and stop the weewx weather system
   Loaded: loaded (/etc/rc.d/init.d/weewx; bad; vendor preset: disabled)
   Active: active (running) since Sat 2023-02-04 11:25:59 EST; 6h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 16792 ExecStop=/etc/rc.d/init.d/weewx stop (code=exited, status=0/SUCCESS)
  Process: 16803 ExecStart=/etc/rc.d/init.d/weewx start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
           └─16813 python2 /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf





Tom Keffer

unread,
Feb 4, 2023, 5:48:23 PM2/4/23
to weewx...@googlegroups.com
If you run weewxd directly from the command line, do you see any LOOP packets? If not, I'd suspect that the console is not emitting anything.

-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.

Bob DeMattia

unread,
Feb 4, 2023, 8:18:41 PM2/4/23
to weewx...@googlegroups.com
No loop packets.  I can visit the site on Monday morning.   This is an old WM918.  I'm guessing the 8 x AAA alkaline batteries didn't do well in the subzero temperatures - but still, the unit also has  AC power.  It probably just glitched when the power was interrupted, and the weak batteries didn't fill in the gap during the glitch.

Thanks for your advice,
Bob


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/iaDBTFbl820/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/CAPq0zEAXW_4-2xLG0peAqZEyZQVPTcpn9srVBt%2Bakb1Zc_%3DLfA%40mail.gmail.com.

Bob DeMattia

unread,
Feb 5, 2023, 6:08:57 PM2/5/23
to weewx...@googlegroups.com
Sure enough, I visited the site today and found piezoelectric sounder in the WM918 continuous on (normally it just beeps when you press buttons).
The screen was frozen.  After a power cycle it resumed normal operation.  I also put a fresh set of batteries in it.

Thanks Tom for pointing me in the right direction.  I always thought there was a timeout message in the log when the serial connection had failed.

-Bob

Reply all
Reply to author
Forward
0 new messages