Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #204524 > unrolled thread

mariadb error on start (Debian 9)

Back to article view | Back to linux.debian.user

Contents

  mariadb error on start (Debian 9) Jose Velasco <velasco.lopez@gmail.com> - 2019-01-19 01:20 +0100
    Re: mariadb error on start (Debian 9) Ulf Volmer <u.volmer@u-v.de> - 2019-01-19 02:50 +0100
      Re: mariadb error on start (Debian 9) Jose Velasco <velasco.lopez@gmail.com> - 2019-01-19 09:00 +0100
        Re: mariadb error on start (Debian 9) Jose Velasco <velasco.lopez@gmail.com> - 2019-01-19 14:10 +0100
          Re: mariadb error on start (Debian 9) Ulf Volmer <u.volmer@u-v.de> - 2019-01-19 16:10 +0100
        Re: mariadb error on start (Debian 9) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-21 14:40 +0100

#204524 — mariadb error on start (Debian 9)

[Multipart message — attachments visible in raw view] — view raw

Hello,

I have upgraded a clean install of debian 7 to 9 (stretch) in a VPS, after
upgraded I have installed mariadb-server-10.1.37, but mariadb doesn't
start, the output from systemctl status mariadb.service is:

root@xxxxxx:/etc/systemd/system# systemctl status mariadb.service
* mariadb.service - MariaDB 10.1.37 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor
preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-01-18 00:56:28 CET; 7s
ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 6183 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d
/var/run/mysqld (code=exited, status=226/NAMESPACE)

ene 18 00:56:28 xxxxx.server.info install[6183]: mariadb.service: Failed at
step NAMESPACE spawning /usr/bin/install: Value too large for defined data
type

I have googled for this problem but I don't find any solution to solve it.

If i run mysqld --verbose, it seems to be ok, the output is:
2019-01-18  1:11:22 140380893467072 [Note] mysqld (mysqld
10.1.37-MariaDB-0+deb9u1) starting as process 6297 ...

what could it be the problem?

Thanks in advance.

[toc] | [next] | [standalone]

#204526

On 19.01.19 01:15, Jose Velasco wrote:

> I have upgraded a clean install of debian 7 to 9 (stretch) in a VPS, after

Direct upgrade from 7 to 9 with skipping 8 is not supported.

> ene 18 00:56:28 xxxxx.server.info install[6183]: mariadb.service: Failed at
> step NAMESPACE spawning /usr/bin/install: Value too large for defined data
> type

https://jira.mariadb.org/browse/MDEV-13672

suggest a kernel issue. what is the output of 'uname -a'?

Best regards
Ulf

[toc] | [prev] | [next] | [standalone]

#204530

[Multipart message — attachments visible in raw view] — view raw

It's true, I did an upgrade 7 to 8 and after 8 to 9.

the output of uname -a:
Linux xxxxx-server.info 3.2.41-042stab127.2 #1 SMP Thu Jan 4 16:41:44 MSK
2018 x86_64 GNU/Linux

I suppose that it is a custom kernel by VPS provider.

Thanks Ulf

El sáb., 19 ene. 2019 a las 2:45, Ulf Volmer (<u.volmer@u-v.de>) escribió:

> On 19.01.19 01:15, Jose Velasco wrote:
>
> > I have upgraded a clean install of debian 7 to 9 (stretch) in a VPS,
> after
>
> Direct upgrade from 7 to 9 with skipping 8 is not supported.
>
> > ene 18 00:56:28 xxxxx.server.info install[6183]: mariadb.service:
> Failed at
> > step NAMESPACE spawning /usr/bin/install: Value too large for defined
> data
> > type
>
> https://jira.mariadb.org/browse/MDEV-13672
>
> suggest a kernel issue. what is the output of 'uname -a'?
>
> Best regards
> Ulf
>
>

[toc] | [prev] | [next] | [standalone]

#204537

[Multipart message — attachments visible in raw view] — view raw

finally i have downgraded to jessie, mariadb starts fine now.

Thanks Ulf.

El sáb., 19 ene. 2019 a las 8:52, Jose Velasco (<velasco.lopez@gmail.com>)
escribió:

> It's true, I did an upgrade 7 to 8 and after 8 to 9.
>
> the output of uname -a:
> Linux xxxxx-server.info 3.2.41-042stab127.2 #1 SMP Thu Jan 4 16:41:44 MSK
> 2018 x86_64 GNU/Linux
>
> I suppose that it is a custom kernel by VPS provider.
>
> Thanks Ulf
>
> El sáb., 19 ene. 2019 a las 2:45, Ulf Volmer (<u.volmer@u-v.de>) escribió:
>
>> On 19.01.19 01:15, Jose Velasco wrote:
>>
>> > I have upgraded a clean install of debian 7 to 9 (stretch) in a VPS,
>> after
>>
>> Direct upgrade from 7 to 9 with skipping 8 is not supported.
>>
>> > ene 18 00:56:28 xxxxx.server.info install[6183]: mariadb.service:
>> Failed at
>> > step NAMESPACE spawning /usr/bin/install: Value too large for defined
>> data
>> > type
>>
>> https://jira.mariadb.org/browse/MDEV-13672
>>
>> suggest a kernel issue. what is the output of 'uname -a'?
>>
>> Best regards
>> Ulf
>>
>>

[toc] | [prev] | [next] | [standalone]

#204540

On 19.01.19 14:05, Jose Velasco wrote:

> finally i have downgraded to jessie, mariadb starts fine now.

Yes, that's usually behavior in VPS environments. You are using the
kernel of the host. You should ask your provider which guest systems are
supported.

Best regards
Ulf

[toc] | [prev] | [next] | [standalone]

#204551

On Sat, Jan 19, 2019 at 08:52:13AM +0100, Jose Velasco wrote:
> It's true, I did an upgrade 7 to 8 and after 8 to 9.
> 
> the output of uname -a:
> Linux xxxxx-server.info 3.2.41-042stab127.2 #1 SMP Thu Jan 4 16:41:44 MSK
> 2018 x86_64 GNU/Linux
> 
> I suppose that it is a custom kernel by VPS provider.

OpenVZ, to be precise ("stab" is a dead giveaway).  You're lucky yours
is so new!

greg@remote:~$ uname -a
Linux remote 2.6.32-042stab127.2 #1 SMP Thu Jan 4 16:41:44 MSK 2018 i686 GNU/Linux

Mine is never going past wheezy.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web