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.

Le samedi 11 novembre 2023 à 16:49:36 UTC+1, Steve Fowler a écrit :

> 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. 
>
> On Saturday, November 11, 2023 at 6:44:39 AM UTC-8 Steve Fowler wrote:
>
>> 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.  
>>
>> On Friday, November 10, 2023 at 9:40:12 PM UTC-8 vince wrote:
>>
>>> Which 'latest' ?  v4 or v5 beta ?
>>> Which instructions ?
>>>
>>> On Friday, November 10, 2023 at 9:03:33 PM UTC-8 Steve Fowler wrote:
>>>
>>>> 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
>>>>
>>>>

-- 
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/c0d4624d-4c67-4c3d-b1ea-6d537b7e4067n%40googlegroups.com.

Reply via email to