John, slow down there, dude. 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 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."
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. Let's keep this constructive. -tk On Sun, Nov 16, 2025 at 5:09 PM John Smith <[email protected]> wrote: > After using weeWX for nearly a decade now, I came across a problem with > weeWX that I can only describe as a time bomb waiting to go off, and it was > finally realised after upgrading to Debian 13 Trixie. > > What ever change was made to SystemD caused weeWX to no longer start after > MariaDB, and error handling in weeWX seems very brittle and not fault > tolerant at all. The outcome of this particular situation is weeWX exits > after failing to connect to MariaDB, no waiting or retrying, it just exits > and then needs to be manually started once you notice no updates happening. > > I proposed a simple change to the SystemD service file to re-introduce the > previous behaviour during boot up, but 2 commentators objected because they > have a SQL DB installed, but aren't using it for weeWX and for whatever > reason assumed the delay would be an inconvenience to them, all without any > actual proof to back their claims. > > Then there was further comments pushing things into the bizarre with all > sorts of incredibly unlikely edge cases. > > In any case, no one seems to have any proof that a slight boot up delay > would be an inconvenience let alone detrimental but since the issue has > been closed with the only resolution being a small documentation change > among the bazillion other things in documentation it will be hard to come > across unless you know what you are looking for. > > I think this is an unacceptable solution for the vast majority of people > with a SQL DB installed specifically for use with weeWX to find one day, > like I did, that weeWX will now require manual intervention after their > system boots. > > I still don't understand how the wants of 2 users with a weird setup > trumps the needs of all the users that will suffer detrimentally without > such a delay. > > The proposed changes will have no effect on systems that don't have a SQL > DB installed such as using weeWX with the default SQLite back end, it will > however have a major positive impact on those running weeWX with a SQL DB > back end. > > You can find my PR here: https://github.com/weewx/weewx/pull/1030 > > I ended up implementing a much saner solution to the problem, and those > now, or in the future running SystemD version 257.8-1~deb13u2 or later > might also be interested in my solution... > > -- > 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/CAGTinV4Kq9SRAWX%3DRxGgqbHYxyT4dLBNtbe3FoUyWGsSD11Vpg%40mail.gmail.com > <https://groups.google.com/d/msgid/weewx-user/CAGTinV4Kq9SRAWX%3DRxGgqbHYxyT4dLBNtbe3FoUyWGsSD11Vpg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAPq0zEDqubTmkWe9Hf_cN1M1Qo2or8cKSEGPXY_-2O0kGTZ5dA%40mail.gmail.com.
