Hi Otto, On 12-02-2023 01:29, Otto Kekäläinen wrote:
Did cacti perhaps change how it uses systemd/systemctl?
cacti doesn't use systemd nor systemctl
Probably not, the same version of cacti has been in Debian for a long time. Latest upload of dbconfig-common was on Feb 2nd, and after that MariaDB 10.11.1-3 was still working on Feb 3rd..
Agreed. cacti nor dbconfig-common changed in years on this front. It does expect the MariaDB server to be running and has always done so.
Of course I can accommodate for changes in MariaDB, but I need to understand what changed in MariaDB. From my side it's obviously a delta between the two MariaDB versions.
I'm also seeing this in the (amd64) log (but it's a warning) """ Preparing to unpack .../000-mariadb-server_1%3a10.11.1-4_amd64.deb ...adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory
"""while that's not there in a successful run I inspected. Maybe unrelated but I noticed that the amount of "mysql-common" occurrences in a successful log is different than in a failed log.
> # systemctl restart mariadb > ERROR:systemctl:the ExecStartPre control process exited with error code That looks pretty bad and has nothing to do with cacti. > # dpkg -S /lib/systemd/system/mariadb.service > mariadb-server-10.6: /lib/systemd/system/mariadb.service But that's the version in testing, no? Paul
OpenPGP_signature
Description: OpenPGP digital signature