Please see my second message (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031116#10), I later found out the exact commit that introduced this and why.
On Sat, 11 Feb 2023 at 23:28, Paul Gevers <elb...@debian.org> wrote: ... > 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 > """ Not related. This is expected for machine accounts that don't have real home directories. > > # systemctl restart mariadb > > ERROR:systemctl:the ExecStartPre control process exited with error code > > That looks pretty bad and has nothing to do with cacti. This was actually not the root cause. MariaDB failing to start happened on s390x only and for other reasons. Actual root cause that completely breaks cacti autopkgtests is the changed ordering in apt (check my second message).
