Beiträge von kaiwe

InnoDB: End of page dump
2016-07-30 18:25:52 7f33b434e740 InnoDB: uncompressed page, stored checksum in field1 16843009, calculated checksums for field1: crc32 1329801086, innodb 1910826816, none 3735928559, stored checksum in field2 16843009, calculated checksums for field2: crc32 1329801086, innodb 1091675344, none 3735928559, page LSN 16843009 16843009, low 4 bytes of LSN at page end 16843009, page number (if stored to page already) 16843009, space id (if created with >= MySQL-4.1.1 and stored already) 16843009
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 776.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also MySQL :: MySQL 5.6 Reference Manual :: 14.21.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
2016-07-30 18:25:52 7f33b434e740 InnoDB: Assertion failure in thread 139860043425600 in file buf0buf.cc line 4295
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to MySQL Bugs.
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: MySQL :: MySQL 5.6 Reference Manual :: 14.21.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
16:25:52 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=8388608
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 = 68095 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x7f33b4a83cec]
/usr/sbin/mysqld(handle_fatal_signal+0x481)[0x7f33b481c851]
/lib64/libpthread.so.0(+0xf870)[0x7f33b2e5d870]
/lib64/libc.so.6(gsignal+0x37)[0x7f33b22bc0a7]
/lib64/libc.so.6(abort+0x118)[0x7f33b22bd458]
/usr/sbin/mysqld(+0x8883a8)[0x7f33b4c033a8]
/usr/sbin/mysqld(+0x89bd98)[0x7f33b4c16d98]
/usr/sbin/mysqld(+0x883345)[0x7f33b4bfe345]
/usr/sbin/mysqld(+0x848c32)[0x7f33b4bc3c32]
/usr/sbin/mysqld(+0x83e23f)[0x7f33b4bb923f]
/usr/sbin/mysqld(+0x83ee45)[0x7f33b4bb9e45]
/usr/sbin/mysqld(+0x83fdf7)[0x7f33b4bbadf7]
/usr/sbin/mysqld(+0x8299ae)[0x7f33b4ba49ae]
/usr/sbin/mysqld(+0x767d1c)[0x7f33b4ae2d1c]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x7f33b4760878]
/usr/sbin/mysqld(+0x528531)[0x7f33b48a3531]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x940)[0x7f33b48a99b0]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x8b8)[0x7f33b475a368]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f33b22a8b05]
/usr/sbin/mysqld(+0x3d22ad)[0x7f33b474d2ad]
The manual page at MySQL :: MySQL 5.7 Reference Manual :: B.5.3.3 What to Do If MySQL Keeps Crashing contains
information that should help you find out what is causing the crash.

DESTASWW02:~ # systemctl status mysql.service
mysql.service - MySQL server
Loaded: loaded (/usr/lib/systemd/system/mysql.service; disabled)
Active: activating (start-post) (Result: exit-code) since Sat 2016-07-30 17:15:17 CEST; 19s ago
Process: 11433 ExecStart=/usr/lib/mysql/mysql-systemd-helper start default (code=exited, status=1/FAILURE)
Process: 11424 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade default (code=exited, status=0/SUCCESS)
Process: 11416 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install default (code=exited, status=0/SUCCESS)
Main PID: 11433 (code=exited, status=1/FAILURE); : 11434 (mysql-systemd-h)
CGroup: /system.slice/mysql.service
ââcontrol
ââ11434 /bin/bash /usr/lib/mysql/mysql-systemd-helper wait default
ââ11499 sleep 1
Jul 30 17:15:17 DESTASWW02 mysql-systemd-helper[11434]: Waiting for MySQL to start
Jul 30 17:15:17 DESTASWW02 mysql-systemd-helper[11433]: 2016-07-30 17:15:17 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server opti...ore details).
Jul 30 17:15:17 DESTASWW02 mysql-systemd-helper[11433]: 2016-07-30 17:15:17 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30) starting as process 11433 ...
Jul 30 17:15:18 DESTASWW02 systemd[1]: mysql.service: main process exited, code=exited, status=1/FAILURE
Hint: Some lines were ellipsized, use -l to show in full.