MySQL startet nicht auf Linux Vserver

[ChilloutFuzi]

Hey,
Ich hab mysql auf meinem vserver installiert. Dort läuft Debian. Das Problem ist mysql lässt sich nicht starten.
Es kommt folgender Fehler:

[....] Starting mysql (via systemctl): mysql.serviceJob for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details.
failed!

Ich starte mit folgendem Befehl:
/etc/init.d/mysql start

Und wenn ich systemctl status mysql.service eingebe kommt:

● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Thu 2015-12-03 09:06:13 EST; 2min 6s ago
Process: 5808 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

Dec 03 09:05:42 igcommunity systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Dec 03 09:06:13 igcommunity mysql[5808]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . ...failed!
Dec 03 09:06:13 igcommunity systemd[1]: mysql.service: control process exited, code=exited status=1
Dec 03 09:06:13 igcommunity systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Dec 03 09:06:13 igcommunity systemd[1]: Unit mysql.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

Hoffe mir kann da jemand helfen.
MFG

[Der-Eddy]

Was steht den in deiner /var/log/mysqld.log ?
(Hoffe mal das ist der richtige Pfad, nutze leider kein MySQL)

[ChilloutFuzi]

Die war unglücklicherweise leer. Hab aber einen Unterordner gefunden der mysql hieß und dort war eine error.log

151203 1:45:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:45:41 [Note] Plugin 'FEDERATED' is disabled.
151203 1:45:41 InnoDB: The InnoDB memory heap is disabled
151203 1:45:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:45:41 InnoDB: Compressed tables use zlib 1.2.8
151203 1:45:41 InnoDB: Using Linux native AIO
151203 1:45:41 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:45:41 InnoDB: Completed initialization of buffer pool
151203 1:45:41 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:45:41 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:45:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:45:41 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:45:41 [ERROR] Aborting

151203 1:45:41 [Note] /usr/sbin/mysqld: Shutdown complete

151203 1:45:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:45:41 [Note] Plugin 'FEDERATED' is disabled.
151203 1:45:41 InnoDB: The InnoDB memory heap is disabled
151203 1:45:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:45:41 InnoDB: Compressed tables use zlib 1.2.8
151203 1:45:41 InnoDB: Using Linux native AIO
151203 1:45:41 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:45:41 InnoDB: Completed initialization of buffer pool
151203 1:45:41 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:45:41 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:45:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:45:41 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:45:41 [ERROR] Aborting

151203 1:45:41 [Note] /usr/sbin/mysqld: Shutdown complete

151203 1:45:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:45:41 [Note] Plugin 'FEDERATED' is disabled.
151203 1:45:41 InnoDB: The InnoDB memory heap is disabled
151203 1:45:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:45:41 InnoDB: Compressed tables use zlib 1.2.8
151203 1:45:41 InnoDB: Using Linux native AIO
151203 1:45:41 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:45:41 InnoDB: Completed initialization of buffer pool
151203 1:45:41 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:45:41 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:45:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:45:41 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:45:41 [ERROR] Aborting

151203 1:45:41 [Note] /usr/sbin/mysqld: Shutdown complete

151203 1:45:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:45:41 [Note] Plugin 'FEDERATED' is disabled.
151203 1:45:41 InnoDB: The InnoDB memory heap is disabled
151203 1:45:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:45:41 InnoDB: Compressed tables use zlib 1.2.8
151203 1:45:41 InnoDB: Using Linux native AIO
151203 1:45:41 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:45:41 InnoDB: Completed initialization of buffer pool
151203 1:45:41 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:45:41 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:45:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:45:41 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:45:41 [ERROR] Aborting

151203 1:45:41 [Note] /usr/sbin/mysqld: Shutdown complete

151203 1:45:41 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:45:41 [Note] Plugin 'FEDERATED' is disabled.
151203 1:45:41 InnoDB: The InnoDB memory heap is disabled
151203 1:45:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:45:41 InnoDB: Compressed tables use zlib 1.2.8
151203 1:45:41 InnoDB: Using Linux native AIO
151203 1:45:41 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:45:41 InnoDB: Completed initialization of buffer pool
151203 1:45:41 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:45:41 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:45:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:45:41 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:45:41 [ERROR] Aborting

151203 1:45:41 [Note] /usr/sbin/mysqld: Shutdown complete

151203 01:45:42 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151203 1:45:42 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:45:42 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 949 ...
151203 1:45:42 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:45:42 [Note] Plugin 'FEDERATED' is disabled.
151203 1:45:42 InnoDB: The InnoDB memory heap is disabled
151203 1:45:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:45:42 InnoDB: Compressed tables use zlib 1.2.8
151203 1:45:42 InnoDB: Using Linux native AIO
151203 1:45:42 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:45:42 InnoDB: Completed initialization of buffer pool
151203 1:45:42 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:45:42 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:45:42 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:45:42 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:45:42 [ERROR] Aborting

151203 1:45:42 [Note] /usr/sbin/mysqld: Shutdown complete

151203 01:45:42 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151203 01:49:40 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151203 1:49:40 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:49:40 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 609 ...
151203 1:49:40 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:49:40 [Note] Plugin 'FEDERATED' is disabled.
151203 1:49:40 InnoDB: The InnoDB memory heap is disabled
151203 1:49:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:49:40 InnoDB: Compressed tables use zlib 1.2.8
151203 1:49:40 InnoDB: Using Linux native AIO
151203 1:49:40 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:49:40 InnoDB: Completed initialization of buffer pool
151203 1:49:40 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:49:40 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:49:40 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:49:40 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:49:40 [ERROR] Aborting

151203 1:49:40 [Note] /usr/sbin/mysqld: Shutdown complete

151203 01:49:40 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151203 1:50:32 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:50:32 [Note] Plugin 'FEDERATED' is disabled.
151203 1:50:32 InnoDB: The InnoDB memory heap is disabled
151203 1:50:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:50:32 InnoDB: Compressed tables use zlib 1.2.8
151203 1:50:32 InnoDB: Using Linux native AIO
151203 1:50:32 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:50:32 InnoDB: Completed initialization of buffer pool
151203 1:50:32 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:50:32 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:50:32 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:50:32 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:50:32 [ERROR] Aborting

151203 1:50:32 [Note] /usr/sbin/mysqld: Shutdown complete

151203 1:50:32 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:50:32 [Note] Plugin 'FEDERATED' is disabled.
151203 1:50:32 InnoDB: The InnoDB memory heap is disabled
151203 1:50:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:50:32 InnoDB: Compressed tables use zlib 1.2.8
151203 1:50:32 InnoDB: Using Linux native AIO
151203 1:50:32 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:50:32 InnoDB: Completed initialization of buffer pool
151203 1:50:32 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:50:32 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:50:32 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:50:32 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:50:32 [ERROR] Aborting

151203 1:50:32 [Note] /usr/sbin/mysqld: Shutdown complete

151203 1:50:32 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:50:32 [Note] Plugin 'FEDERATED' is disabled.
151203 1:50:32 InnoDB: The InnoDB memory heap is disabled
151203 1:50:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:50:32 InnoDB: Compressed tables use zlib 1.2.8
151203 1:50:32 InnoDB: Using Linux native AIO
151203 1:50:32 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:50:32 InnoDB: Completed initialization of buffer pool
151203 1:50:32 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:50:32 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:50:32 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:50:32 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:50:32 [ERROR] Aborting

151203 1:50:32 [Note] /usr/sbin/mysqld: Shutdown complete

151203 1:50:32 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:50:32 [Note] Plugin 'FEDERATED' is disabled.
151203 1:50:32 InnoDB: The InnoDB memory heap is disabled
151203 1:50:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:50:32 InnoDB: Compressed tables use zlib 1.2.8
151203 1:50:32 InnoDB: Using Linux native AIO
151203 1:50:32 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:50:32 InnoDB: Completed initialization of buffer pool
151203 1:50:32 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:50:32 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:50:32 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:50:32 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:50:32 [ERROR] Aborting

151203 1:50:32 [Note] /usr/sbin/mysqld: Shutdown complete

151203 01:50:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151203 1:50:32 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:50:32 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 1547 ...
151203 1:50:32 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 1:50:32 [Note] Plugin 'FEDERATED' is disabled.
151203 1:50:32 InnoDB: The InnoDB memory heap is disabled
151203 1:50:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 1:50:32 InnoDB: Compressed tables use zlib 1.2.8
151203 1:50:32 InnoDB: Using Linux native AIO
151203 1:50:32 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
151203 1:50:32 InnoDB: Completed initialization of buffer pool
151203 1:50:32 InnoDB: Fatal error: cannot allocate memory for the buffer pool
151203 1:50:32 [ERROR] Plugin 'InnoDB' init function returned error.
151203 1:50:32 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
151203 1:50:32 [ERROR] Unknown/unsupported storage engine: InnoDB
151203 1:50:32 [ERROR] Aborting

151203 1:50:32 [Note] /usr/sbin/mysqld: Shutdown complete

151203 01:50:32 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151203 08:27:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151203 8:27:54 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:27:54 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 2601 ...
151203 8:27:54 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:27:54 [Note] Plugin 'FEDERATED' is disabled.
151203 8:27:54 InnoDB: The InnoDB memory heap is disabled
151203 8:27:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 8:27:54 InnoDB: Compressed tables use zlib 1.2.8
151203 8:27:54 InnoDB: Using Linux native AIO
151203 8:27:54 InnoDB: Assertion failure in thread 140133302531904 in file ut0mem.c line 103
InnoDB: Failing assertion: ret || !assert_on_error
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to .
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:
InnoDB: about forcing recovery.
13:27:54 UTC - 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.
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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x7f7354073793]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7f7353f60b44]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7f735375e8d0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f7352156107]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f73521574e8]
/usr/sbin/mysqld(+0x542b95)[0x7f73540d1b95]
/usr/sbin/mysqld(+0x5dc0b0)[0x7f735416b0b0]
/usr/sbin/mysqld(+0x51eb1c)[0x7f73540adb1c]
/usr/sbin/mysqld(+0x51f685)[0x7f73540ae685]
/usr/sbin/mysqld(+0x523bfd)[0x7f73540b2bfd]
/usr/sbin/mysqld(+0x4f1915)[0x7f7354080915]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_in t+0x3f)[0x7f7353f62d3f]
/usr/sbin/mysqld(+0x2f5431)[0x7f7353e84431]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x903)[0x7f7353e888a3]
/usr/sbin/mysqld(+0x27bfd8)[0x7f7353e0afd8]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7f7353e0fa1b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f7352142b45]
/usr/sbin/mysqld(+0x277cf8)[0x7f7353e06cf8]
The manual page at contains
information that should help you find out what is causing the crash.
151203 08:27:54 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151203 08:29:11 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151203 8:29:11 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:29:11 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 3290 ...
151203 8:29:11 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:29:11 [Note] Plugin 'FEDERATED' is disabled.
151203 8:29:11 InnoDB: The InnoDB memory heap is disabled
151203 8:29:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 8:29:11 InnoDB: Compressed tables use zlib 1.2.8
151203 8:29:11 InnoDB: Using Linux native AIO
151203 8:29:11 InnoDB: Unable to allocate memory of size 320120.
151203 8:29:11 InnoDB: Assertion failure in thread 140661127104320 in file mem0mem.c line 361
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to .
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:
InnoDB: about forcing recovery.
13:29:11 UTC - 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.
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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x7fee38d30793]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7fee38c1db44]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fee3841b8d0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fee36e13107]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fee36e144e8]
/usr/sbin/mysqld(+0x5d1bad)[0x7fee38e1dbad]
/usr/sbin/mysqld(+0x51ea7a)[0x7fee38d6aa7a]
/usr/sbin/mysqld(+0x51f685)[0x7fee38d6b685]
/usr/sbin/mysqld(+0x523bfd)[0x7fee38d6fbfd]
/usr/sbin/mysqld(+0x4f1915)[0x7fee38d3d915]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_in t+0x3f)[0x7fee38c1fd3f]
/usr/sbin/mysqld(+0x2f5431)[0x7fee38b41431]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x903)[0x7fee38b458a3]
/usr/sbin/mysqld(+0x27bfd8)[0x7fee38ac7fd8]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7fee38acca1b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fee36dffb45]
/usr/sbin/mysqld(+0x277cf8)[0x7fee38ac3cf8]
The manual page at contains
information that should help you find out what is causing the crash.
151203 08:29:11 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151203 08:37:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151203 8:37:03 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:37:03 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 3993 ...
151203 8:37:03 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:37:03 [Note] Plugin 'FEDERATED' is disabled.
151203 8:37:03 InnoDB: The InnoDB memory heap is disabled
151203 8:37:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 8:37:03 InnoDB: Compressed tables use zlib 1.2.8
151203 8:37:03 InnoDB: Using Linux native AIO
151203 8:37:03 InnoDB: Unable to allocate memory of size 320120.
151203 8:37:03 InnoDB: Assertion failure in thread 139691744859968 in file mem0mem.c line 361
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to .
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:
InnoDB: about forcing recovery.
13:37:03 UTC - 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.
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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x7f0c8523d793]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7f0c8512ab44]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7f0c849288d0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0c83320107]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0c833214e8]
/usr/sbin/mysqld(+0x5d1bad)[0x7f0c8532abad]
/usr/sbin/mysqld(+0x51ea7a)[0x7f0c85277a7a]
/usr/sbin/mysqld(+0x51f685)[0x7f0c85278685]
/usr/sbin/mysqld(+0x523bfd)[0x7f0c8527cbfd]
/usr/sbin/mysqld(+0x4f1915)[0x7f0c8524a915]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_in t+0x3f)[0x7f0c8512cd3f]
/usr/sbin/mysqld(+0x2f5431)[0x7f0c8504e431]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x903)[0x7f0c850528a3]
/usr/sbin/mysqld(+0x27bfd8)[0x7f0c84fd4fd8]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7f0c84fd9a1b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f0c8330cb45]
/usr/sbin/mysqld(+0x277cf8)[0x7f0c84fd0cf8]
The manual page at contains
information that should help you find out what is causing the crash.
151203 08:37:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151203 08:38:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151203 8:38:34 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:38:34 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 4722 ...
151203 8:38:34 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:38:34 [Note] Plugin 'FEDERATED' is disabled.
151203 8:38:34 InnoDB: The InnoDB memory heap is disabled
151203 8:38:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 8:38:34 InnoDB: Compressed tables use zlib 1.2.8
151203 8:38:34 InnoDB: Using Linux native AIO
151203 8:38:34 InnoDB: Unable to allocate memory of size 320120.
151203 8:38:34 InnoDB: Assertion failure in thread 140196487657280 in file mem0mem.c line 361
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to .
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:
InnoDB: about forcing recovery.
13:38:34 UTC - 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.
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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x7f820a27b793]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7f820a168b44]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7f82099668d0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f820835e107]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f820835f4e8]
/usr/sbin/mysqld(+0x5d1bad)[0x7f820a368bad]
/usr/sbin/mysqld(+0x51ea7a)[0x7f820a2b5a7a]
/usr/sbin/mysqld(+0x51f685)[0x7f820a2b6685]
/usr/sbin/mysqld(+0x523bfd)[0x7f820a2babfd]
/usr/sbin/mysqld(+0x4f1915)[0x7f820a288915]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_in t+0x3f)[0x7f820a16ad3f]
/usr/sbin/mysqld(+0x2f5431)[0x7f820a08c431]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x903)[0x7f820a0908a3]
/usr/sbin/mysqld(+0x27bfd8)[0x7f820a012fd8]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7f820a017a1b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f820834ab45]
/usr/sbin/mysqld(+0x277cf8)[0x7f820a00ecf8]
The manual page at contains
information that should help you find out what is causing the crash.
151203 08:38:34 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151203 08:41:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151203 8:41:13 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:41:13 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 5441 ...
151203 8:41:13 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 8:41:13 [Note] Plugin 'FEDERATED' is disabled.
151203 8:41:13 InnoDB: The InnoDB memory heap is disabled
151203 8:41:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 8:41:13 InnoDB: Compressed tables use zlib 1.2.8
151203 8:41:13 InnoDB: Using Linux native AIO
151203 8:41:13 InnoDB: Assertion failure in thread 139755961595712 in file ut0mem.c line 103
InnoDB: Failing assertion: ret || !assert_on_error
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to .
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:
InnoDB: about forcing recovery.
13:41:13 UTC - 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.
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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x7f1b78c17793]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7f1b78b04b44]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7f1b783028d0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f1b76cfa107]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f1b76cfb4e8]
/usr/sbin/mysqld(+0x542b95)[0x7f1b78c75b95]
/usr/sbin/mysqld(+0x52652c)[0x7f1b78c5952c]
/usr/sbin/mysqld(+0x52806e)[0x7f1b78c5b06e]
/usr/sbin/mysqld(+0x51f128)[0x7f1b78c52128]
/usr/sbin/mysqld(+0x51f680)[0x7f1b78c52680]
/usr/sbin/mysqld(+0x523bfd)[0x7f1b78c56bfd]
/usr/sbin/mysqld(+0x4f1915)[0x7f1b78c24915]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_in t+0x3f)[0x7f1b78b06d3f]
/usr/sbin/mysqld(+0x2f5431)[0x7f1b78a28431]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x903)[0x7f1b78a2c8a3]
/usr/sbin/mysqld(+0x27bfd8)[0x7f1b789aefd8]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7f1b789b3a1b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f1b76ce6b45]
/usr/sbin/mysqld(+0x277cf8)[0x7f1b789aacf8]
The manual page at contains
information that should help you find out what is causing the crash.
151203 08:41:13 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
151203 09:05:42 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
151203 9:05:42 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
151203 9:05:42 [Note] /usr/sbin/mysqld (mysqld 5.5.46-0+deb8u1) starting as process 6179 ...
151203 9:05:42 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
151203 9:05:42 [Note] Plugin 'FEDERATED' is disabled.
151203 9:05:42 InnoDB: The InnoDB memory heap is disabled
151203 9:05:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
151203 9:05:42 InnoDB: Compressed tables use zlib 1.2.8
151203 9:05:42 InnoDB: Using Linux native AIO
151203 9:05:42 InnoDB: Assertion failure in thread 139922524952384 in file ut0mem.c line 103
InnoDB: Failing assertion: ret || !assert_on_error
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to .
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:
InnoDB: about forcing recovery.
14:05:42 UTC - 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.
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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x7f4240b49793]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7f4240a36b44]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7f42402348d0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f423ec2c107]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f423ec2d4e8]
/usr/sbin/mysqld(+0x542b95)[0x7f4240ba7b95]
/usr/sbin/mysqld(+0x5dc0b0)[0x7f4240c410b0]
/usr/sbin/mysqld(+0x51eb1c)[0x7f4240b83b1c]
/usr/sbin/mysqld(+0x51f685)[0x7f4240b84685]
/usr/sbin/mysqld(+0x523bfd)[0x7f4240b88bfd]
/usr/sbin/mysqld(+0x4f1915)[0x7f4240b56915]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_in t+0x3f)[0x7f4240a38d3f]
/usr/sbin/mysqld(+0x2f5431)[0x7f424095a431]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x903)[0x7f424095e8a3]
/usr/sbin/mysqld(+0x27bfd8)[0x7f42408e0fd8]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7f42408e5a1b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f423ec18b45]
/usr/sbin/mysqld(+0x277cf8)[0x7f42408dccf8]
The manual page at contains
information that should help you find out what is causing the crash.
151203 09:05:42 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

[xinput.dll]

Navigiere mal nach /var/lib/mysql (bzw. in dem Ordner in dem du mysql installiert hast) und lösche die Dateien ./ib_logfile0 und ./ib_logfile1 falls vorhanden.

[ChilloutFuzi]

ich hab dort kein mysql ordner. Hab aber unter /etc/mysql was gefunden dort sind die Dateien bzw Ordner conf.d, debian-start, debian.cnf, my.cnf
Aber ib_logfile0 und 1 find ich nicht

[xinput.dll]

Originally Posted by ChilloutFuzi

ich hab dort kein mysql ordner. Hab aber unter /etc/mysql was gefunden dort sind die Dateien bzw Ordner conf.d, debian-start, debian.cnf, my.cnf
Aber ib_logfile0 und 1 find ich nicht

ok hast du an der my.cnf was angepasst gehabt?


mach mal ein cat auf my.cnf und poste mal den output des wertes "innodb_log_file_size"

[ChilloutFuzi]

Habe nichts angepasst.
Die innodb_log_file_size gibts in der datei nicht.

Wäre es vielleicht nicht einfach mysql neu zu installieren ?

[Zypr]

Originally Posted by ChilloutFuzi

Habe nichts angepasst.
Die innodb_log_file_size gibts in der datei nicht.

Wäre es vielleicht nicht einfach mysql neu zu installieren ?

Kannst du natürlich auch machen, dann solltest du allerdings alles löschen, was Mysql betrifft.

apt-get purge mysql-*

Dann suchst du nach allen Mysql Ordnern und entfernst diese per Hand:

find / -name mysql

rm -r /var/lib/mysql/
rm -r /und/so/weiter