Upgraded OS and Weewx - fails to start

193 views
Skip to first unread message

Steve Fowler

unread,
Nov 11, 2023, 12:03:33 AM11/11/23
to weewx-user
Just upgraded to Debian 12 and installed the latest version of weewx according to the install steps for Debian.  Everything seemed to go along smoothly until the end and I get this:
Job for weewx.service failed because the control process exited with error code.
See "systemctl status weewx.service" and "journalctl -xeu weewx.service" for details.
invoke-rc.d: initscript weewx, action "start" failed.
× weewx.service - LSB: weewx weather system
     Loaded: loaded (/etc/init.d/weewx; generated)
     Active: failed (Result: exit-code) since Fri 2023-11-10 20:26:25 PST; 22ms ago
       Docs: man:systemd-sysv-generator(8)
    Process: 12332 ExecStart=/etc/init.d/weewx start (code=exited, status=1/FAILURE)
        CPU: 299ms

Nov 10 20:26:25 corv-weewx systemd[1]: Starting weewx.service - LSB: weewx weather system...
Nov 10 20:26:25 corv-weewx weewx[12332]: Starting weewx weather system: weewx
Nov 10 20:26:25 corv-weewx weewx[12343]: Traceback (most recent call last):
Nov 10 20:26:25 corv-weewx weewx[12343]:   File "/usr/share/weewx/weewxd", line 29, in <module>
Nov 10 20:26:25 corv-weewx weewx[12343]:     import user.extensions
Nov 10 20:26:25 corv-weewx weewx[12343]: ModuleNotFoundError: No module named 'user.extensions'
Nov 10 20:26:25 corv-weewx weewx[12332]:  failed!
Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Control process exited, code=exited, status=1/FAILURE
Nov 10 20:26:25 corv-weewx systemd[1]: weewx.service: Failed with result 'exit-code'.
Nov 10 20:26:25 corv-weewx systemd[1]: Failed to start weewx.service - LSB: weewx weather system.
dpkg: error processing package weewx (--configure):
 installed weewx package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Errors were encountered while processing:
 weewx
E: Sub-process /usr/bin/dpkg returned an error code (1)

systemctl and journalctl both point to weewxd not finding module user.extentions.

Any help would be appreciated.
Steve

vince

unread,
Nov 11, 2023, 12:40:12 AM11/11/23
to weewx-user
Which 'latest' ?  v4 or v5 beta ?
Which instructions ?

Steve Fowler

unread,
Nov 11, 2023, 9:44:39 AM11/11/23
to weewx-user
Followed the instructions for Debian install using deb package in the weewx docs for python 3.  It downloaded the latest stable 4.10.2.  I installed using root and not the weewx user if that makes and difference. The system has python 3.11.2. 

Steve Fowler

unread,
Nov 11, 2023, 10:49:36 AM11/11/23
to weewx-user
Looks like I got it running by going back and running setup.py.  Whatever failed in the deb package install was corrected and the service started.

Sylvain M

unread,
Nov 14, 2023, 4:16:20 PM11/14/23
to weewx-user
I had the same problem with OpenSuse Tumbleweed where a big update even blocked python-based system programs such as firewalld (it's not nothing), others and of course weewx.
I was able to check all the programs for errors with the command:

# systemctl list-units --state=failed

I made a link from python3.11 to python3 which is the reference for many programs:

# ln /usr/bin/python3.11 /usr/bin/python3

All programs worked again while avoiding changes in all files.

Steve Fowler

unread,
Nov 14, 2023, 7:43:38 PM11/14/23
to weewx-user
I hadn't posted it, but after installing weewx it failed to create the weewx web folder in /var/www/html directory.  Instead it ended up in weewx home.  So I created a link.

gjr80

unread,
Nov 14, 2023, 8:15:13 PM11/14/23
to weewx-user
Entirely expected behaviour, you indicated you did a setup.py install and by default setup.py installs result in WeeWX generated output going to /home/weewx/public_html. Where to find things in the User's Guide refers. Creating the link was exactly the correct solution.

Gary
Reply all
Reply to author
Forward
0 new messages