On Monday, August 3, 2020 at 11:58:11 AM UTC-7, brisguy foo wrote:
>
> My original complaint was that I could not get the daemon to START without
> rebooting the system. I never mentioned problems with shutting it down. If
> you look at the log starting around 10:47, you'll see messages indicatin
My original complaint was that I could not get the daemon to START without
rebooting the system. I never mentioned problems with shutting it down. If
you look at the log starting around 10:47, you'll see messages indicating
that weewx has started, but it should have posted a new record at 11:50
On Sunday, August 2, 2020 at 8:25:24 PM UTC-7, brisguy foo wrote:
> In the log, the switching between direct a daemon execution starts around
> 10:15 which is when I finally successfully installed version 4.1.1. It
> looks like I killed the daemon around 10:15 and fixed an error in the .conf
>
It's hard for me to unravel what's happening. The only thing i can suggest
is to use systemctl. Seems to work for me:
sudo systemctl start weewx
Sorry, but I don't have any insights.
-tk
On Sun, Aug 2, 2020 at 8:25 PM brisguy foo wrote:
>
> Oh. I just assumed I was starting/stopping things in
Depends on the operating system, but you have the general idea.
You may not think there is anything useful in the log, but please humor me:
post it anyway. And, tell us the operating system.
On Sun, Aug 2, 2020 at 2:03 PM brisguy foo wrote:
> I had to do some debugging og my weewx installation
I had to do some debugging og my weewx installation recently and needed to
swap back and forth between running directly and as a daemon. However, once
I used the direct method, I never seem to be able to get the daemon
launched again without just doing a reboot.
I have been doing the following
