Discussion:
Bug#870200: mariadb-server-10.1: jessie --> stretch: starting mariadb impossible (Failed at step NAMESPACE spawning /usr/bin/install: Value too large for defined data type)
(too old to reply)
o***@gehirnspen.de
2017-07-30 21:20:27 UTC
Permalink
Package: mariadb-server-10.1
Version: 10.1.23-9+deb9u1
Severity: important

Dear Maintainer,

Good evening everyone. I just just upgraded fromJessie to stretch and cannot install/run mariadb at all.
*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation? Updating jessie to stretch
* What exactly did you do (or not do) that was effective (or
ineffective)? apt dist-upgrade, I had mysqlserver 5.5 in use before
* What was the outcome of this action? running sql server
* What outcome did you expect instead? failed to install/start

It fails at installation already. apt install -f gives:
***@h1342773:~# apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
[...]
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up mariadb-server-10.1 (10.1.23-9+deb9u1) ...
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.
* mariadb.service - MariaDB database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2017-07-30 23:09:56 CEST; 14ms ago
Process: 3119 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=226/NAMESPACE)
dpkg: error processing package mariadb-server-10.1 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
mariadb-server-10.1
E: Sub-process /usr/bin/dpkg returned an error code (1)


If I try to start manually, it gives
***@h1342773:~# mysqld
2017-07-30 23:14:23 3056408576 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2017-07-30 23:14:23 3056408576 [Note] mysqld (mysqld 10.1.23-MariaDB-9+deb9u1) starting as process 3171 ...
2017-07-30 23:14:23 3056408576 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-07-30 23:14:24 3056408576 [Note] InnoDB: The InnoDB memory heap is disabled
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-07-30 23:14:24 3056408576 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Using Linux native AIO
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Using generic crc32 instructions
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Completed initialization of buffer pool
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Highest supported file format is Barracuda.
2017-07-30 23:14:24 3056408576 [Note] InnoDB: 128 rollback segment(s) are active.
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Waiting for purge to start
2017-07-30 23:14:24 3056408576 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 4856681904
2017-07-30 23:14:24 3056408576 [Note] Plugin 'FEEDBACK' is disabled.
2017-07-30 23:14:24 1463786304 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-07-30 23:14:24 3056408576 [Note] Server socket created on IP: '127.0.0.1'.
2017-07-30 23:14:24 3056408576 [ERROR] Can't start server : Bind on unix socket: No such file or directory
2017-07-30 23:14:24 3056408576 [ERROR] Do you already have another mysqld server running on socket: /var/run/mysqld/mysqld.sock ?
2017-07-30 23:14:24 3056408576 [ERROR] Aborting

but /var/run/mysqld is not existing. Even when I create it manually it gives:
***@h1342773:~# mkdir /var/run/mysqld
***@h1342773:~# mysqld
2017-07-30 23:16:50 3056605184 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2017-07-30 23:16:50 3056605184 [Note] mysqld (mysqld 10.1.23-MariaDB-9+deb9u1) starting as process 3216 ...
2017-07-30 23:16:50 3056605184 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-07-30 23:16:50 3056605184 [Note] InnoDB: The InnoDB memory heap is disabled
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-07-30 23:16:50 3056605184 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Using Linux native AIO
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Using generic crc32 instructions
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Completed initialization of buffer pool
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Highest supported file format is Barracuda.
2017-07-30 23:16:50 3056605184 [Note] InnoDB: 128 rollback segment(s) are active.
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Waiting for purge to start
2017-07-30 23:16:50 3056605184 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 4856681914
2017-07-30 23:16:50 3056605184 [Note] Plugin 'FEEDBACK' is disabled.
2017-07-30 23:16:50 1463786304 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-07-30 23:16:50 3056605184 [Note] Server socket created on IP: '127.0.0.1'.
2017-07-30 23:16:50 3056605184 [ERROR] Can't start server : Bind on unix socket: Permission denied
2017-07-30 23:16:50 3056605184 [ERROR] Do you already have another mysqld server running on socket: /var/run/mysqld/mysqld.sock ?
2017-07-30 23:16:50 3056605184 [ERROR] Aborting

***@h1342773:~# ls -l /var/run/mysqld
total 0
***@h1342773:~#

I saw on google that I am not the only one, but could not spot any solution. Any help would be greatly appreciated!

Thanks for the great work,
Harald




-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.41-042stab123.9 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to de_DE.utf8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.utf8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages mariadb-server-10.1 depends on:
ii adduser 3.115
ii debconf [debconf-2.0] 1.5.61
ii galera-3 25.3.19-2
ii gawk 1:4.1.4+dfsg-1
ii init-system-helpers 1.48
ii iproute2 4.9.0-1
ii libaio1 0.3.110-3
ii libc6 2.24-11+deb9u1
ii libdbi-perl 1.636-1+b1
ii libpam0g 1.1.8-3.6
ii libstdc++6 6.3.0-18
ii libsystemd0 232-25+deb9u1
ii lsb-base 9.20161125
ii lsof 4.89+dfsg-0.1
ii mariadb-client-10.1 10.1.23-9+deb9u1
ii mariadb-common 10.1.23-9+deb9u1
ii mariadb-server-core-10.1 10.1.23-9+deb9u1
ii passwd 1:4.4-4.1
ii perl 5.24.1-3+deb9u1
ii psmisc 22.21-2.1+b2
ii rsync 3.1.2-1
ii socat 1.7.3.1-2+deb9u1
ii zlib1g 1:1.2.8.dfsg-5

Versions of packages mariadb-server-10.1 recommends:
ii libhtml-template-perl 2.95-2

Versions of packages mariadb-server-10.1 suggests:
ii bsd-mailx [mailx] 8.1.2-0.20160123cvs-4
pn mariadb-test <none>
pn netcat-openbsd <none>
pn tinyca <none>

-- debconf information:
mariadb-server-10.1/old_data_directory_saved:
mariadb-server-10.1/postrm_remove_databases: false
mariadb-server-10.1/nis_warning:

Loading...