I was able to reproduce this on a VM running Leap 15.1. I'm not sure
exactly what's going on (and I am by no means an expert!), but I think the
problem may be the presence of a --daemon flag in the systemd service file.
How it got in there, I don't have a clue.

To fix, stop weewx

*sudo systemctl stop weewx*


Then go into /etc/systemd/system/weewx.service and change this

ExecStart=/usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid
/etc/weewx/weewx.conf

to this

ExecStart=/usr/bin/weewxd --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

Then reload systemd, and restart weewx:

*sudo systemctl daemon-reload*
*sudo systemctl start weewx*


Let me know what happens.

-tk


On Fri, Apr 22, 2022 at 3:44 PM Bernhard R. <[email protected]> wrote:

> Hi guys,
> First of all: Thank you guys for your great work, weewx does a very
> decent job here for more than 2 years already.
>
> Since the last update however weewx won't start anymore (using systemd).
> I'm on opensuse Leap 15.3, the update to weewx v.4.8.0 also brought a new
> service file to /etc/systemd/system/weewx.service
> With this new service-file, weewx will not start.
> If I put the old service file from 4.7.0 back in place, weewx 4.8.0
> starts fine.
>
> Here is, what my log shows, when using the new service file:
>
>
> Apr 23 00:17:17 nas systemd[1]: Started weewx weather system.
> Apr 23 00:17:17 nas python3[4841]: weewx[4841] INFO __main__: Initializing
> weewx version 4.8.0
> Apr 23 00:17:17 nas python3[4841]: weewx[4841] INFO __main__: Using Python
> 3.6.15 (default, Sep 23 2021, 15:41:43) [GCC]
> Apr 23 00:17:17 nas python3[4841]: weewx[4841] INFO __main__: Platform
> Linux-5.3.18-150300.59.63-default-x86_64-with-glibc2.3.4
> Apr 23 00:17:17 nas python3[4841]: weewx[4841] INFO __main__: Locale is
> 'LC_CTYPE=de_DE.UTF-8;LC_NUMERIC=C;LC_TIME=C;LC_COLLATE=C;LC_MONETARY=C;LC_MESSAGES=C;LC_PAPER=C;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=C;LC_IDENTIFICATION=C'
>
> Apr 23 00:17:17 nas python3[4841]: weewx[4841] INFO __main__: Using
> configuration file /etc/weewx/weewx.conf
> Apr 23 00:17:17 nas python3[4841]: weewx[4841] INFO __main__: Debug is 0
> Apr 23 00:17:17 nas python3[4841]: weewx[4841] INFO __main__: PID file is
> /var/run/weewx.pid
> Apr 23 00:17:17 nas python3[4849]: weewx[4849] INFO weewx.engine: Loading
> station type WH4000SE (user.WH4000SE)
> Apr 23 00:17:17 nas python3[4849]: weewx[4849] INFO user.WH4000SE:
> WH4000SE Starting
> Apr 23 00:17:17 nas python3[4849]: weewx[4849] INFO user.WH4000SE: Using
> user-defined station IP - 192.168.0.41
> Apr 23 00:17:17 nas python3[4849]: weewx[4849] INFO weewx.engine:
> StdConvert target unit is 0x11
> Apr 23 00:17:17 nas python3[4849]: weewx[4849] INFO weewx.wxservices:
> StdWXCalculate will use data binding wx_binding
> Apr 23 00:17:17 nas python3[4849]: weewx[4849] INFO __main__: Received
> signal TERM (15).
> Apr 23 00:17:17 nas python3[4849]: weewx[4849] INFO __main__: Terminating
> weewx version 4.8.0
> Apr 23 00:17:17 nas systemd[1]: weewx.service: Succeeded.
>
> Guess that's something to do with this one:
> Do not fork if using systemd. PR #767.
>
> Anything I can provide to trace this one?
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-development/5e234c55-56a5-41a2-949a-2ad3038c82d6n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-development/5e234c55-56a5-41a2-949a-2ad3038c82d6n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/CAPq0zECR_tVLnA8eZq_trLMPsap8WJSg5QNhncz-g%3D-v8p6baQ%40mail.gmail.com.

Reply via email to