26 Jul
2021
26 Jul
'21
8:54 p.m.
> Op 26 jul. 2021 om 19:27 heeft Reindl Harald <h.reindl@thelounge.net> het volgende geschreven: > > > >> Am 26.07.21 um 17:30 schrieb William Edwards: >> William Edwards schreef op 2021-07-23 19:16: >>> Hello, >>> >>> The weather probably has an effect on me, because I'm not seeing the >>> cause for the issue below right away. Hopefully someone can use the >>> cluebat. Also, I apologize if we're not supposed to paste snippets of >>> this size in email, but I couldn't find a mailing list policy on this. >> Some additional information after further debugging: >> - The upgrade started at 16:06:18, MariaDB shut down gracefully at 16:06:23, but - while the upgrade was still in progress - started again exactly 5 seconds later at 16:06:28. This makes me suspect a watchdog started MariaDB at the wrong time. However, MariaDB shut down gracefully, so systemd's 'Restart=on-abort' shouldn't have done anything. >> - The server starts up fine with a new datadir created by 'mysql_install_db'. This confirms the suspicion that the data was corrupted because of *something* that happened during the upgrade > > that's why we don't use "mysqld_safe" and don't package "mysql_install_db" as well as we don't restart services at updates in our internal packages > > it's simply idiotic doing that within a dist-upgrade and for minor version updates even more Just to be clear: I’m not using mysqld_safe. > > _______________________________________________ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss@lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp >