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:
root@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
root@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:
root@h1342773:~# mkdir /var/run/mysqld
root@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
