> As someone said before you could start WeeWX from the command line as
> described here.
This is 4.9.1, above is for weewx 5. I'm using systemd.
So after investigating further, here's what I ran:
pi@PI4B1:/etc/systemd/system $ sleep 3;sudo /home/weewx/bin/weewxd
(I sleep my command 3 secs so I have time to switch to my syslog window)
And it did not crash, after removing the comment try: except: finally:
lines in the python in extensions.py
So ... question is, why does starting it using systemd crash because
of extensions.py, but running it from the command line does not?
Not sure how much of this is OS, how much is weewx version, how much
is my diminished mental status. Just thought of one thing: I always
use the setup.py method to install weewx; this may be something that
Tom could weigh in on.
Repeatability: I'm going to CtrlC the command window, restart it using
systemctl start weewx, and verify it indeed exits:
And it restarts normally. I did some testing, in extensions.py I put
in some code, calling "IntroduceAnError()", and I get the expected
entries in syslog ("CRITICAL __main__: **** NameError: name
'IntruduceAnError' is not defined)
Removed my intentional python error out of extensions.py.
Then, stopped and restarted weewx, and it started normally.
So it's working as expected. I don't have a clue why it wouldn't start
weewx, then running it once manually, then running it systemd, it
suddenly works normally. I diff'd my two extensions.py and the only
diff was the comment out of the try: except: finally: lines, in case
I'd made a typo.
I'm clueless.
You're all up to date.
And thanks for all your help and suggestions. I wish I'd learned
something here, but it's frustrating that it just started working for
no noticeable reason, just like it failed to work for no apparent
reason.
--- Thanks again ---
On Fri, Apr 18, 2025 at 1:31 PM Karen K <kk4468...@gmail.com> wrote:
>
> messyp...@gmail.com schrieb am Freitag, 18. April 2025 um 14:36:13 UTC+2:
>
> There will be no cycles, because after I issue [sudo systemctl start weewx]
> it **immediately exits**. Therefore no debug=1 output. The only thing in
> syslog is
>
> Apr 15 21:05:48 PI4B1 systemd[1]: weewx.service: Main process exited,
> code=exited, status=1/FAILURE
> Apr 15 21:05:48 PI4B1 systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
>
>
> I have difficulties to believe that there is really nothing before those
> messages.
>
> As someone said before you could start WeeWX from the command line as
> described here.
>
> --
> You received this message because you are subscribed to a topic in the Google
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/cM4T6W4XjdA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/weewx-user/ba2e6dcf-6fc0-432d-89c8-cc1651ab3785n%40googlegroups.com.
--
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 visit
https://groups.google.com/d/msgid/weewx-user/CAB7-S76j4OCBqhrsxr-E5OCPVbcyPgqW7N7%2BDA7DsoVPm_VDtg%40mail.gmail.com.
