[MDEV-13672] Can't start mariadb as service; Value too large for defined data type Created: 2017-08-29  Updated: 2022-01-20

Status: Stalled
Project: MariaDB Server
Component/s: Packaging, Platform Debian
Affects Version/s: 10.1, 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Joel Luijmes Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Debian 9


Issue Links:
Relates
relates to MDEV-15502 debian: systemd, with tmpfiles instal... Open

 Description   

On a pretty much fresh debian 9 install, the service fails to start. However when manually starting the daemon it works.

systemctl status mariadb.service
● mariadb.service - MariaDB database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf
   Active: failed (Result: exit-code) since Tue 2017-08-29 21:37:15 CEST; 4min 6s ago
  Process: 5622 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=226/NAMESPACE)
 
Aug 29 21:37:15 h2721614.stratoserver.net mysqld[5622]: mariadb.service: Failed at step NAMESPACE spawning /usr/bin/install: Value too large for defined data type

While googeling for this problem I found this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870200



 Comments   
Comment by Elena Stepanova [ 2017-08-29 ]

joell, are you installing packages from the Debian repository or from MariaDBs? and If it's from MariaDB repository, which version is it – 10.1 or 10.2?
Are you using lxc?

Comment by Joel Luijmes [ 2017-08-30 ]

I first tried it with the MariaDB sources, which was version 10.2. Then I removed the sources and tried to install it from the Debian repository where I tried it from Stretch (MariaDB 10.1).

Then I installed it from Jessie repository (MariaDB 10.0); which works.

Comment by Ondřej Surý (Inactive) [ 2017-08-30 ]

joell Did you fully cleaned up the system after removing 10.2 from MariaDB repository and installing official Debian 10.1?

And while you mention the Debian bug - are you running an official Debian 9's kernel?

Comment by Joel Luijmes [ 2017-08-30 ]

Uhm I believe so (not to familiair with linux to be honest..) What I've executed:

apt --purge remove "mariadb*"
apt --purge remove "mysql*"
rm -rf /var/mysql
rm -rf /etc/mysql

And if I'm running an official kernel, I'm not sure actually?

# cat /etc/issue
Debian GNU/Linux 9 \n \l
# uname -r
3.16.0-042stab123.9
# cat /proc/version
Linux version 3.16.0-042stab123.9 (root@kbuild-rh6-x64.eng.sw.ru) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Thu Jun 29 13:01:59 MSK 2017

However on Debian's wiki: https://wiki.debian.org/DebianStretch it says kernal version 4.9..

This machine is a vps, which was installed with Debian 8 and I upgraded it to Debian 9.

I also just tried installing MariaDB 10.3 from the MariaDB repository, but that gives the same error.

Edit: since you are asking if I'm using the correct / debian kernal, which I'm apparantly not, I'm going to reinstall my VPS to Debian 8 and see if I have the same problems there. If not its not working because my own stupidity..

I tried upgrading the kernel but it looks like that is blocked by vps host

Comment by Joel Luijmes [ 2017-08-30 ]

Okay update; Now I'm back on Debian 8 and MariaDB 10.2 (from the MariaDB repository) starts just fine. So I suppose the problem was caused by me using the wrong kernel for Debian 9.

Comment by Ondřej Surý (Inactive) [ 2017-08-30 ]

Yup, it's actually the systemd that requires the newer kernel. It's not directly related to MariaDB.

Comment by Ondřej Surý (Inactive) [ 2017-09-11 ]

On a second thought, Debian Jessie is still supported distribution, so this needs to be addressed.

Comment by Daniel Black [ 2018-04-01 ]

MDEV-15502 might be a functional workaround, if tmpfiles where included in Debian.

Generated at Thu Feb 08 08:07:26 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.