" The weeWX Debian package has pre/post scripts that install the service files during updates... I can't ever remember being prompted to approve/deny SystemD service files..." Because unlike config files, the user-modified unit files should be placed in dirs like /etc/systemd/system where they simply override any unit file that is installed/updated in the default locations assigned to packages. I don't think apt/dpkg does any checks for such situations.
On Monday, 17 November 2025 at 5:10:45 pm UTC+10 John Smith wrote: On Mon, 17 Nov 2025 at 16:58, 'Cameron D' via weewx-user < [email protected]> wrote: The quick response to whether it might be core or extension is that it is the systemD component that is new and is somehow seems to be causing problems. But I don't recall that capability (waiting for Mysql) even being possible in sysv-init code so I think the problem has always been there. That was 1 reason given for SystemD's creation, it starts as much as it can in parallel, SYS-V ordered startup by sorting filenames and launching them one after another... I have kept using my own modified service files since then and update them manually if I see changes in the shipped version. The weeWX Debian package has pre/post scripts that install the service files during updates... I can't ever remember being prompted to approve/deny SystemD service files... My impression was that weewx had become more resilient to the DB server disappearing for a bit, but I also have restart parameters set in my unit file. Maybe it is a difference between failing on initial connection or failing at a later stage. I can't recall weeWX waiting and retrying at all, and I manually had to start it after resolving any issues, the difference now is weeWX is starting before MariaDB during boot up... That's what's new here... My other comment (and the reason I did not reply in support of your PR) is that your changes would only be a partial solution, because it cannot account for a db server running on a different host. If the most common use case is running weeWX using SQLite, and following that would be by people running weeWX with a SQL DB, I don't think such a setup as you described would be used by your average weather hobbyist... At most it'd be 2 docker containers but even that would still be on the same physical system... This is how I was running my system at one stage and the weewx side must rely on some sort of restart/retry process when a remote mysql goes down, whether it is the server itself or the network connectivity. Please don't also stray into weird and wonderful use cases that aren't common, people running those setups usually know what they're doing and can adjust SystemD files to suit, what you described isn't a typical use case by a very long margin, but using a SQL DB on the same system for weeWX would be... -- 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 visit https://groups.google.com/d/msgid/weewx-user/b6cfbde6-8280-4e82-a623-bf9dabdc8ac6n%40googlegroups.com.
