Datenbank Server Startet nicht mehr

[Domenick Waldvogel]

Hallo,

ich habe das Problem das mein Datenbank Server nicht mehr startet. Ich hab auch schon ein Backup ausprobiert aber jedesmal nach ca. 10 Minuten stürzt dieser ab und lässt sich nicht mehr starten.

Die Log sagt folgendes:

Server version: 5.5.44-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
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 = 466713 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7fe71697a4ed]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7fe716590385]
/lib64/libpthread.so.0(+0xf100)[0x7fe715cc0100]
/lib64/libc.so.6(gsignal+0x37)[0x7fe7144745f7]
/lib64/libc.so.6(abort+0x148)[0x7fe714475ce8]
/usr/libexec/mysqld(+0x6497df)[0x7fe71673a7df]
/usr/libexec/mysqld(+0x64a419)[0x7fe71673b419]
/usr/libexec/mysqld(+0x74b2a4)[0x7fe71683c2a4]
/usr/libexec/mysqld(+0x740295)[0x7fe716831295]
/usr/libexec/mysqld(+0x64c619)[0x7fe71673d619]
/usr/libexec/mysqld(+0x640586)[0x7fe716731586]
/lib64/libpthread.so.0(+0x7dc5)[0x7fe715cb8dc5]
/lib64/libc.so.6(clone+0x6d)[0x7fe71453528d]
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.
160225 16:43:38 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
160225 16:53:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160225 16:53:21 [Note] /usr/libexec/mysqld (mysqld 5.5.44-MariaDB) starting as process 11775 ...
160225 16:53:21 [Warning] option 'innodb-buffer-pool-size': signed value 2097152 adjusted to 5242880
160225 16:53:21 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288
160225 16:53:21 InnoDB: The InnoDB memory heap is disabled
160225 16:53:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160225 16:53:21 InnoDB: Compressed tables use zlib 1.2.7
160225 16:53:21 InnoDB: Using Linux native AIO
160225 16:53:21 InnoDB: Initializing buffer pool, size = 5.0M
160225 16:53:21 InnoDB: Completed initialization of buffer pool
160225 16:53:21 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 3924048755
160225 16:53:21 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...
InnoDB: Doing recovery: scanned up to log sequence number 3924050893
160225 16:53:21 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
160225 16:53:21 InnoDB: Waiting for the background threads to start
160225 16:53:21 InnoDB: Assertion failure in thread 140222708090624 in file trx0purge.c line 848
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
160225 16:53:21 [ERROR] mysqld got signal 6 ;
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.44-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
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 = 466713 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7f883f08d4ed]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7f883eca3385]
/lib64/libpthread.so.0(+0xf100)[0x7f883e3d3100]
/lib64/libc.so.6(gsignal+0x37)[0x7f883cb875f7]
/lib64/libc.so.6(abort+0x148)[0x7f883cb88ce8]
/usr/libexec/mysqld(+0x6497df)[0x7f883ee4d7df]
/usr/libexec/mysqld(+0x64a419)[0x7f883ee4e419]
/usr/libexec/mysqld(+0x74b2a4)[0x7f883ef4f2a4]
/usr/libexec/mysqld(+0x740295)[0x7f883ef44295]
/usr/libexec/mysqld(+0x64c619)[0x7f883ee50619]
/usr/libexec/mysqld(+0x640586)[0x7f883ee44586]
/lib64/libpthread.so.0(+0x7dc5)[0x7f883e3cbdc5]
/lib64/libc.so.6(clone+0x6d)[0x7f883cc4828d]
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.
160225 16:53:22 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended



Ich habe schon seit 2 Tagen das Internet durchforstet und garnichts hat geholfen. Und der Recovery Modus funktioniert ebenfalls nicht (startet nicht).

Ich bitte um Hilfe

LG