[MDEV-15586] MariaDB server won''t start. Created: 2018-03-16  Updated: 2018-03-16  Resolved: 2018-03-16

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 5.5.59
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Dermot Brereton Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty

Attachments: Text File error.log    

 Description   

Mar 16 13:35:55 git kernel: [ 6256.343743] init: mysql main process ended, respawning
Mar 16 13:35:55 git kernel: [ 6256.655402] init: mysql post-start process (2853) terminated with status 1
Mar 16 13:35:55 git kernel: [ 6256.669565] audit: type=1400 audit(1521207355.329:33): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/mysqld" pid=2901 comm="apparmor_parser"
Mar 16 13:35:57 git kernel: [ 6258.419730] init: mysql main process (2913) terminated with status 1
Mar 16 13:35:57 git kernel: [ 6258.419749] init: mysql main process ended, respawning
Mar 16 13:35:57 git kernel: [ 6258.725988] init: mysql post-start process (2914) terminated with status 1
Mar 16 13:35:57 git kernel: [ 6258.740062] audit: type=1400 audit(1521207357.401:34): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/mysqld" pid=2962 comm="apparmor_parser"
Mar 16 13:35:59 git kernel: [ 6260.495716] init: mysql main process (2974) terminated with status 1
Mar 16 13:35:59 git kernel: [ 6260.495737] init: mysql respawning too fast, stopped
Mar 16 13:36:17 git console-kit-daemon[1406]: GLib-CRITICAL: Source ID 114 was not found when attempting to remove it
Mar 16 13:39:22 git kernel: [ 6464.313194] audit: type=1400 audit(1521207562.970:35): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/mysqld" pid=3127 comm="apparmor_parser"

 Comments   
Comment by Elena Stepanova [ 2018-03-16 ]

Please paste the error log of mysqld, it is not it.
It can be either a separate file or a part of syslog.

Comment by Dermot Brereton [ 2018-03-16 ]

error.log

/var/log/mysql/error.log uploaded as requested.

Comment by Elena Stepanova [ 2018-03-16 ]

Dermot.Brereton, thanks.

First of all, from all appearances, it's not MariaDB, but MySQL, particularly this package provided by Ubuntu: https://packages.ubuntu.com/trusty/amd64/database/mysql-server-5.5.
If you expect to have MariaDB, but got MySQL instead, something must have gone wrong upon installation or upgrade.

But regardless of that, according to our InnoDB experts, the general explanation of the crash is already visible here in the first lines:

180316 11:16:50  InnoDB: Error: page 32780 log sequence number 44761426002
 
InnoDB: is in the future! Current system log sequence number 44761424692.
 
InnoDB: Your database may be corrupt or you may have copied the InnoDB
 
InnoDB: tablespace but not the InnoDB log files. See
 
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
 
InnoDB: for more information.

It's pretty much a self-contained message, the likely reason is that the data directory has been compromised either by taking a copy of a running database (without backup tools like xtrabackup/mariabackup) and trying to use it, or copying/moving/overriding some files but not all, or using files from different backups, like too old redo file and too new data files, etc.

Comment by Dermot Brereton [ 2018-03-16 ]

You are correct this is a MySQL installation.

Thank you for your explanation on this issue. It can now be closed.

Generated at Thu Feb 08 08:22:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.