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. I moved weewx to systemd before it became part of the basic weewx system - I think precisely because I was seeing that problem whenever there was an upgrade to MariaDB. I have kept using my own modified service files since then and update them manually if I see changes in the shipped version.
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. 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. 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. On Monday, 17 November 2025 at 12:12:27 pm UTC+10 John Smith wrote: > On Mon, 17 Nov 2025 at 13:03, Tom Keffer <[email protected]> wrote: > >> John, slow down there, dude. >> > > You didn't respond to any of my comments\ until I made them more widely > known. > > >> Let me set the record straight. As I stated in the PR, if you want an >> out-of-the-box solution, use SQLite. MySQL was never intended to be that. >> To use it, it must be first installed, then a root password set up then, >> then using the >> > > Then why is it in core code and not in an extension? > > >> mysql client, set up an account to be used with WeeWX, then set proper >> permissions for that account. Modifying the services file is just one more >> step in that process. It's not a "time bomb waiting to go off." >> > > Yes it was a time bomb and it went off for me, hence the PR to restore > previous system behaviour, I don't have some bent to go out of my way > filing frivolous PRs, these take time and effort. > > >> >> Also, weewxd *does* restart if MySQL is not ready. Or, if it doesn't, >> that's a bug. I just checked it on my Mac, and it works as it is supposed >> to. >> > > Not on Debian 13 Trixie running SystemD 257.8-1~deb13u2 hence the PR.... > -- 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/69e3607f-aee5-409f-8228-a5381c216ebfn%40googlegroups.com.
