[MCOL-897] Can't start mariadb.server: Value too large for defined data type Created: 2017-08-29  Updated: 2017-08-29  Resolved: 2017-08-29

Status: Closed
Project: MariaDB ColumnStore
Component/s: MariaDB Server
Affects Version/s: 1.0.10
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Joel Luijmes Assignee: David Hill (Inactive)
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Debian 9



 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



 Comments   
Comment by Joel Luijmes [ 2017-08-29 ]

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

EDIT: indeed using mariadb 10 (by using the jessie sources) I can start the service just fine.

Comment by David Hill (Inactive) [ 2017-08-29 ]

MariaDB Columnstore product doesn't use the mariadb service... Here is the service that is used

/usr/local/mariadb/columnstore/bin/columnstore.service

If you follow the install guide and run post-install then postConfigure, that will setup the service for you also.

https://mariadb.com/kb/en/the-mariadb-library/preparing-for-columnstore-installation/#initial-downloadinstall-of-mariadb-columnstore-binary-package

Comment by Joel Luijmes [ 2017-08-29 ]

My bad, I wasn't aware that I made this ticket on the wrong board. I'll create a new issue at the MDEV board and then this ticket can be closed.

Generated at Thu Feb 08 02:24:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.