Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
5.5.54
-
None
-
synology DSM 6.1.3.15152 Update 5
Description
Trying to start MariaDB fails. The hostname.err file contains the following:
170928 10:32:34 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended |
170928 10:37:38 mysqld_safe Starting mysqld daemon with databases from /var/packages/MariaDB/target/mysql |
170928 10:37:39 [Note] /usr/bin/mysqld (mysqld 5.5.54-MariaDB) starting as process 20074 ... |
170928 10:37:39 InnoDB: The InnoDB memory heap is disabled |
170928 10:37:39 InnoDB: Mutexes and rw_locks use InnoDB's own implementation |
170928 10:37:39 InnoDB: Compressed tables use zlib 1.2.8 |
170928 10:37:39 InnoDB: Using Linux native AIO |
170928 10:37:39 InnoDB: Initializing buffer pool, size = 16.0M |
170928 10:37:39 InnoDB: Completed initialization of buffer pool |
170928 10:37:39 InnoDB: highest supported file format is Barracuda. |
InnoDB: The log sequence number in ibdata files does not match
|
InnoDB: the log sequence number in the ib_logfiles!
|
170928 10:37:39 InnoDB: Database was not shut down normally! |
InnoDB: Starting crash recovery.
|
InnoDB: Reading tablespace information from the .ibd files...
|
InnoDB: Restoring possible half-written data pages from the doublewrite
|
InnoDB: buffer...
|
170928 10:37:44 InnoDB: Waiting for the background threads to start |
170928 10:37:45 Percona XtraDB (http://www.percona.com) 5.5.52-MariaDB-38.3 started; log sequence number 1598363888 |
170928 10:37:45 [Note] Plugin 'FEEDBACK' is disabled. |
170928 10:37:45 [Note] Server socket created on IP: '0.0.0.0'. |
170928 10:37:47 [Note] Event Scheduler: Loaded 0 events |
170928 10:37:47 [Note] /usr/bin/mysqld: ready for connections. |
Version: '5.5.54-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 Source distribution |
InnoDB: Page directory corruption: infimum not pointed to
|
170928 10:37:47 InnoDB: Page dump in ascii and hex (16384 bytes): |
len 16384; hex 000000000 [REOMVED MANY ZEROS]; asc ; |
InnoDB: End of page dump
|
170928 10:37:47 InnoDB: Page checksum 1575996416 (32bit_calc: 2253597184), prior-to-4.0.14-form checksum 1371122432 |
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 |
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 |
InnoDB: Page number (if stored to page already) 0, |
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 |
InnoDB: Page may be a freshly allocated page
|
InnoDB: Page directory corruption: supremum not pointed to
|
170928 10:37:47 InnoDB: Page dump in ascii and hex (16384 bytes): |
len 16384; hex 000000000; asc ; |
InnoDB: End of page dump
|
170928 10:37:47 InnoDB: Page checksum 1575996416 (32bit_calc: 2253597184), prior-to-4.0.14-form checksum 1371122432 |
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 |
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 |
InnoDB: Page number (if stored to page already) 0, |
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 |
InnoDB: Page may be a freshly allocated page
|
170928 10:37:47 [ERROR] mysqld got signal 11 ; |
This could be because you hit a bug. It is also possible that this binary |
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
 |
To report this bug, see http://kb.askmonty.org/en/reporting-bugs |
 |
We will try our best to scrape up some info that will hopefully help |
diagnose the problem, but since we have already crashed,
|
something is definitely wrong and this may fail. |
 |
Server version: 5.5.54-MariaDB |
key_buffer_size=16384 |
read_buffer_size=262144 |
max_used_connections=1 |
max_threads=153 |
thread_count=0 |
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 354234 K bytes of memory |
Hope that's ok; if not, decrease some variables in the equation. |
 |
Thread pointer: 0x0 |
Attempting backtrace. You can use the following information to find out
|
where mysqld died. If you see no messages after this, something went |
terribly wrong...
|
stack_bottom = 0x0 thread_stack 0x3c000 |
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains |
information that should help you find out what is causing the crash.
|
170928 10:37:47 mysqld_safe Number of processes running now: 0 |
170928 10:37:47 mysqld_safe mysqld restarted |
170928 10:37:48 [Note] /usr/bin/mysqld (mysqld 5.5.54-MariaDB) starting as process 20164 ... |
170928 10:37:48 InnoDB: The InnoDB memory heap is disabled |
170928 10:37:48 InnoDB: Mutexes and rw_locks use InnoDB's own implementation |
170928 10:37:48 InnoDB: Compressed tables use zlib 1.2.8 |
170928 10:37:48 InnoDB: Using Linux native AIO |
170928 10:37:48 InnoDB: Initializing buffer pool, size = 16.0M |
170928 10:37:48 InnoDB: Completed initialization of buffer pool |
170928 10:37:48 InnoDB: highest supported file format is Barracuda. |
InnoDB: The log sequence number in ibdata files does not match
|
InnoDB: the log sequence number in the ib_logfiles!
|
170928 10:37:48 InnoDB: Database was not shut down normally! |
InnoDB: Starting crash recovery.
|
InnoDB: Reading tablespace information from the .ibd files...
|
InnoDB: Restoring possible half-written data pages from the doublewrite
|
InnoDB: buffer...
|
170928 10:37:48 InnoDB: Waiting for the background threads to start |
InnoDB: Page directory corruption: infimum not pointed to
|
170928 10:37:48 InnoDB: Page dump in ascii and hex (16384 bytes): |
len 16384; hex 000000000; asc ; |
InnoDB: End of page dump
|
170928 10:37:48 InnoDB: Page checksum 1575996416 (32bit_calc: 2253597184), prior-to-4.0.14-form checksum 1371122432 |
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 |
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 |
InnoDB: Page number (if stored to page already) 0, |
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 |
InnoDB: Page may be a freshly allocated page
|
InnoDB: Page directory corruption: supremum not pointed to
|
170928 10:37:48 InnoDB: Page dump in ascii and hex (16384 bytes): |
len 16384; hex 000000000; asc ; |
InnoDB: End of page dump
|
170928 10:37:48 InnoDB: Page checksum 1575996416 (32bit_calc: 2253597184), prior-to-4.0.14-form checksum 1371122432 |
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0 |
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0 |
InnoDB: Page number (if stored to page already) 0, |
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 |
InnoDB: Page may be a freshly allocated page
|
170928 10:37:48 [ERROR] mysqld got signal 11 ; |
This could be because you hit a bug. It is also possible that this binary |
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
 |
To report this bug, see http://kb.askmonty.org/en/reporting-bugs |
 |
We will try our best to scrape up some info that will hopefully help |
diagnose the problem, but since we have already crashed,
|
something is definitely wrong and this may fail. |
 |
Server version: 5.5.54-MariaDB |
key_buffer_size=16384 |
read_buffer_size=262144 |
max_used_connections=0 |
max_threads=153 |
thread_count=0 |
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 354234 K bytes of memory |
Hope that's ok; if not, decrease some variables in the equation. |
 |
Thread pointer: 0x0 |
Attempting backtrace. You can use the following information to find out
|
where mysqld died. If you see no messages after this, something went |
terribly wrong...
|
stack_bottom = 0x0 thread_stack 0x3c000 |
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains |
information that should help you find out what is causing the crash.
|
170928 10:37:48 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended |
Tried updates. Out if ideas. Any help is much appreciated!
Max