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 (and every five minutes thereafter), but did not. Same thing starting at 11:27. At that point, I reboot so I can mount a USB drive onto the system, which involves disconnecting the weather-station since I only have one USB port I can use! After that reboot, the system ran normally.
Anyway, if I am using the correct commands, I'm fine. I may try running more tests using the 'systemctl' on the command line when starting the daemon. On Monday, August 3, 2020 at 8:37:33 AM UTC-7, vince wrote: > > 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 >> file and started directly. Then stopped that and tried to start the daemon. >> You will see a reboot eventually after that, at which point everything >> works. At some point, I also changed the conf debug setting from zero to 1. >> >> > I guess I'm missing what you see in the log that leads you to think it > didn't shut down. > > Try a test.....do a 'sudo systemctl stop weewx' and see what it > says....then do 'sudo systemctl status weewx'....then do "ps aux | grep > weewx" and see if there are any processes actually running > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e0464b3f-046f-491f-a00e-34e59f78093bo%40googlegroups.com.
