Debian Bug report logs - #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)

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: oxi@gehirnspen.de

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: mariadb-server-10.1: jessie --> stretch: starting mariadb impossible (Failed at step NAMESPACE spawning /usr/bin/install: Value too large for defined data type)

Date: Sun, 30 Jul 2017 23:20:27 +0200

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] 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

root@h1342773:~# ls -l /var/run/mysqld
total 0
root@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:

Message #10 received at 870200@bugs.debian.org (full text, mbox, reply):

From: oxi@gehirnspen.de

To: 870200@bugs.debian.org

Subject: Could start it with --skip-grant-tables

Date: Wed, 9 Aug 2017 21:46:34 +0200

Good evening,

the problem persists, but I can start the database with 
sudo /usr/sbin/mysqld --skip-grant-tables --general-log

and afterwards execute mysql_upgrade without it throwing an error.

The downside is that it does not change anything. I still cannot install mariadb-server-10.1 without the error I metioned.

Would it help to purge the package completly and reinstall the tables from the backup?

Harald

Message #15 received at 870200@bugs.debian.org (full text, mbox, reply):

From: oxi@gehirnspen.de

To: 870200@bugs.debian.org

Subject: Purged and reinstalled

Date: Thu, 10 Aug 2017 23:03:45 +0200

Good evening,

in the meantime I have purged all mariadb packages and reinstalled them. mariadb-server-10.1 did still not install, but with another error. I purged once more and installed version 10.0, which worked fine.

For me, this bug can be closed.

Harald

Message #20 received at 870200@bugs.debian.org (full text, mbox, reply):

From: Ondřej Surý <ondrej@sury.org>

To: oxi@gehirnspen.de, 870200@bugs.debian.org

Subject: Re: Bug#870200: Purged and reinstalled

Date: Fri, 11 Aug 2017 00:44:55 +0200

Hi Harald,

is it possible that you are running some kind of security protection
like apparmor with some old profile loaded, or selinux or you have
edited the default systemd unit and added Private*=yes or other security
options or something like that (check /etc/systemd/, what does systemctl
status mariadb says, etc.).

This:

  Process: 3119 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d
  /var/run/mysqld (code=exited, status=226/NAMESPACE)

has not much to do with mariadb-10.1 itself, but it looks like
overzealous security settings in the system or in the systemd service
file.

Or perhaps you are running in some restricted container/lxc?

Cheers,
-- 
Ondřej Surý <ondrej@sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Thu, Aug 10, 2017, at 23:03, oxi@gehirnspen.de wrote:
> Good evening,
> 
> in the meantime I have purged all mariadb packages and reinstalled them.
> mariadb-server-10.1 did still not install, but with another error. I
> purged once more and installed version 10.0, which worked fine.
> 
> For me, this bug can be closed.
> 
> Harald
> 

Message #25 received at 870200@bugs.debian.org (full text, mbox, reply):

From: oxi@gehirnspen.de

To: 870200@bugs.debian.org

Subject: Additional idea

Date: Sat, 12 Aug 2017 22:47:17 +0200

Good evening,

in the course of fixing issues with my upgrade I got redis-server running which failed due to the odd and old kernel I (have to) use, configured and installed by the provider of the (virtual) machine. Marc Ballarin, who obviously knows a lot more about that topic an who reported #863477 and brought the solution on the way,  mentioned in his original post (https://github.com/systemd/systemd/issues/6318) that he cannot start mariadb either and had to downgrade systemd. So, wventually, this is maybe an issue with my old (and probably quite patched) kernel (3.2.41-042stab123.9) in combination with systemd.

Regards, Harald

Message #30 received at 870200@bugs.debian.org (full text, mbox, reply):

From: Faustin Lammler <faustin@mariadb.org>

To: 870200@bugs.debian.org

Subject: linking to mariadb bug report tool

Date: Tue, 29 May 2018 15:55:05 -0300

Hi Harald,
thank you for your help!

Linking this bug to MariaDB bug report tool:
https://jira.mariadb.org/browse/MDEV-13672

Faustin

Message #35 received at 870200-done@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 787118-done@bugs.debian.org,808419-done@bugs.debian.org,835596-done@bugs.debian.org,851195-done@bugs.debian.org,851643-done@bugs.debian.org,851644-done@bugs.debian.org,852776-done@bugs.debian.org,853972-done@bugs.debian.org,861553-done@bugs.debian.org,864421-done@bugs.debian.org,864943-done@bugs.debian.org,865534-done@bugs.debian.org,865931-done@bugs.debian.org,866751-done@bugs.debian.org,866782-done@bugs.debian.org,866983-done@bugs.debian.org,867137-done@bugs.debian.org,869782-done@bugs.debian.org,870200-done@bugs.debian.org,870433-done@bugs.debian.org,871796-done@bugs.debian.org,873460-done@bugs.debian.org,874370-done@bugs.debian.org,875457-done@bugs.debian.org,879099-done@bugs.debian.org,879728-done@bugs.debian.org,880738-done@bugs.debian.org,887007-done@bugs.debian.org,887655-done@bugs.debian.org,891218-done@bugs.debian.org,897428-done@bugs.debian.org,900398-done@bugs.debian.org,905599-done@bugs.debian.org,912848-done@bugs.debian.org,913207-done@bugs.debian.org,914215-done@bugs.debian.org,919776-done@bugs.debian.org,920380-done@bugs.debian.org,

Cc: mariadb-10.1@packages.debian.org

Subject: Bug#920581: Removed package(s) from unstable

Date: Sun, 27 Jan 2019 11:36:56 +0000

Version: 1:10.1.37-3+rm

Dear submitter,

as the package mariadb-10.1 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/920581

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Message #48 received at 870200-done@bugs.debian.org (full text, mbox, reply):

From: Andreas Beckmann <anbe@debian.org>

To: 887007-done@bugs.debian.org, 873460-done@bugs.debian.org, 864943-done@bugs.debian.org, 870200-done@bugs.debian.org, 865534-done@bugs.debian.org

Subject: mariadb-10.1 has been removed from Debian

Date: Thu, 27 Apr 2023 20:59:46 +0200

Version: 1:10.1.37-3+rm

src:mariadb-10.1 was last released with Debian 9 (stretch)
in June 2017 and was removed from the Debian archive afterwards.
It has been superseded by newer versions.
See https://bugs.debian.org/920581 for details on the removal.
After regular security support for stretch ended in July 2020 and LTS
support ended in July 2022, I'm closing the remaining bug reports now.
In case the bug is still present in recent releases, please reopen and
reassign it.

Andreas

Send a report that this bug log contains spam.