[Expired for mariadb-10.1 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: mariadb-10.1 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@theo, the ProtectHome directive of systemd is a sandboxing feature that
permits to protect home directory and if you put your datadir (normally
/var/lib/mysql) into the /home directory, then you should disable this
sandboxing feature to allow mariadb to start.
But @Mathieu is right and I don't
Hi Mathieu,
thank you for your report and for your help making Ubuntu better.
It is difficult to understand your problem because you do not provide
the steps that would permit me to try to reproduce it.
But I can see in the 'Dmesg.txt' log the following lines:
[594512.788195] audit: type=1400
A database server living exclusively in /var has no business touching
anything in /home, and has even less business umounting it. But I can't
confirm this from just running the dpkg command, as all it tells me is
"127" even when I run it with option "-D7". /var/log/apt/history.log
is even
I had exactly the same problem. Changing "ProtectHome=true" to
"ProtectHome=false" in the Unit-File fixed it for me. systemd was trying
to unmount /home, which was not possible because of a lot of bind mounts
on /home.
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840055
Title:
package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to
install/upgrade: installed
