Weewx 5.2 Not Starting

66 views
Skip to first unread message

Ron Walker

unread,
Nov 11, 2025, 12:59:47 PMNov 11
to weewx-user
Hi All,

After successfully upgrading to weewx 5.2 and running with no issues for a week or so, I had to shut my system down to  relocate it.  When I tried to start the system this morning I got the following error:

weewx.service - WeeWX
     Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2025-11-11 12:50:52 EST; 2s ago
   Duration: 3.480s
 Invocation: 9a42579792ff497bba40fab5879af960
       Docs: https://weewx.com/docs
    Process: 1942 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, status=1/FAILURE)
   Main PID: 1942 (code=exited, status=1/FAILURE)
        CPU: 2.852s

Nov 11 12:50:52 raspberrypi weewxd[1942]:   File "/usr/share/weewx/weewx/accum.py", line 497, in add_value
Nov 11 12:50:52 raspberrypi weewxd[1942]:     self[obs_type].addHiLo(val, record['dateTime'])
Nov 11 12:50:52 raspberrypi weewxd[1942]:     ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
Nov 11 12:50:52 raspberrypi weewxd[1942]:   File "/usr/share/weewx/weewx/accum.py", line 325, in addHiLo
Nov 11 12:50:52 raspberrypi weewxd[1942]:     speed, dirN = val
Nov 11 12:50:52 raspberrypi weewxd[1942]:     ^^^^^^^^^^^
Nov 11 12:50:52 raspberrypi weewxd[1942]: TypeError: cannot unpack non-iterable float object
Nov 11 12:50:52 raspberrypi systemd[1]: weewx.service: Main process exited, code=exited, status=1/FAILURE
Nov 11 12:50:52 raspberrypi systemd[1]: weewx.service: Failed with result 'exit-code'.
Nov 11 12:50:52 raspberrypi systemd[1]: weewx.service: Consumed 2.852s CPU time.

There have been no changes since it ran successfully!  Can someone point me in the right direction to resolve?

Thank you!



vince

unread,
Nov 11, 2025, 1:29:43 PMNov 11
to weewx-user
Not without much more information about your setup and much more complete log entries, but it seems like you are trying to process bad/incomplete data...

Ron Walker

unread,
Nov 18, 2025, 11:52:05 AM (9 days ago) Nov 18
to weewx-user
Sorry for the delayed reply, I've been unable to get back to this until now.

Vince, you are correct!  The issue was caused by corrupted data!  Since this is an experimental upgrade system, I just deleted the database and the data file (I'm using fileparse) and restarted weewx.  I originally should have posted the log with the original request.

Thanks again!

Ron
Reply all
Reply to author
Forward
0 new messages