Problem solved - your hint was extremely helpful. Really, the Engine part
was corrupt. My previous post of Engine was an excerpt from my BACKUP copy
of weewx.conf (taken before uninstall). Due to my uninstall the entry
archive_services was completely corrupt into
archive_services = w,
That looks fine. I'm having trouble seeing how such an an error will
truncate a log entry. Nor do I see uninstalling the forecast extension
would cause such a problem. Keeping debug = 1 can you restart WeeWX and
post the WeeWX log from the WeeWX startup through until the error occurs.
One
[Engine]
# The following section specifies which services should be run and in
what order.
[[Services]]
prep_services = weewx.engine.StdTimeSynch
data_services = ,
process_services = weewx.engine.StdConvert,
weewx.engine.StdCalibrate, weewx.engine.StdQC,
Please post a copy of the [Engine] stanza from weewx.conf.
Gary
On Wednesday, 9 March 2022 at 18:19:36 UTC+10 miwa...@googlemail.com wrote:
> Setting debug=1 within weewx.conf enhances the amount of messages, but
> still a crash:
>
> Mär 09 09:14:43 imurr9 python3[859]: weewx[859] INFO
Setting debug=1 within weewx.conf enhances the amount of messages, but
still a crash:
Mär 09 09:14:43 imurr9 python3[859]: weewx[859] INFO weewx.wxservices:
StdWXCalculate will use data binding wx_binding
Mär 09 09:14:43 imurr9 python3[859]: weewx[859] DEBUG weewx.engine:
Finished loading
I've now compared the log messages from the successful start of weewx 4.5.1
with the current one - the difference occures with data binding wx_binding:
Feb 13 09:08:36 imurr9 python3[500]: weewx[500] INFO weewx.engine:
StdConvert target unit is 0x1
Feb 13 09:08:36 imurr9 python3[500]:
