mysql startet nicht mehr

Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

Hinweis: In dem Thema mysql startet nicht mehr gibt es 5 Antworten. Der letzte Beitrag () befindet sich ganz unten auf dieser Seite.
  • mysql startet nicht mehr

    Ich habe meinen opesuse 13.2 Server mit init 0 heruntergefahren und nach einigen Stunden wieder gestartet.
    Alle Dienste ( ssh, apache, samba ) lassen sich problemlos starten, nur der mysql Dienst bringt untenstehende
    Fehlermeldung.

    Die verschiedenen Lösungsansätze im Internet ( Rechte setzen usw. ) waren nicht erfolgreich, zumal an der Config
    nichts geändert wurde, der Server war einfach nur aus.

    Kann mir hier bitte jemand helfen ?

    Vielen Dank schon mal !


    Quellcode

    1. DESTASWW02:~ # systemctl status mysql.service
    2. mysql.service - MySQL server
    3. Loaded: loaded (/usr/lib/systemd/system/mysql.service; disabled)
    4. Active: activating (start-post) (Result: exit-code) since Sat 2016-07-30 17:15:17 CEST; 19s ago
    5. Process: 11433 ExecStart=/usr/lib/mysql/mysql-systemd-helper start default (code=exited, status=1/FAILURE)
    6. Process: 11424 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade default (code=exited, status=0/SUCCESS)
    7. Process: 11416 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install default (code=exited, status=0/SUCCESS)
    8. Main PID: 11433 (code=exited, status=1/FAILURE); : 11434 (mysql-systemd-h)
    9. CGroup: /system.slice/mysql.service
    10. ââcontrol
    11. ââ11434 /bin/bash /usr/lib/mysql/mysql-systemd-helper wait default
    12. ââ11499 sleep 1
    13. Jul 30 17:15:17 DESTASWW02 mysql-systemd-helper[11434]: Waiting for MySQL to start
    14. 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).
    15. 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 ...
    16. Jul 30 17:15:18 DESTASWW02 systemd[1]: mysql.service: main process exited, code=exited, status=1/FAILURE
    17. Hint: Some lines were ellipsized, use -l to show in full.
    Alles anzeigen
    Konsolenausgaben bitte in Code-Tags

    Für den Inhalt des Beitrages 97347 haftet ausdrücklich der jeweilige Autor: kaiwe

  • im /var/log/messages steht folgendes:

    Quellcode

    1. InnoDB: End of page dump
    2. 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
    3. InnoDB: Database page corruption on disk or a failed
    4. InnoDB: file read of page 776.
    5. InnoDB: You may have to recover from a backup.
    6. InnoDB: It is also possible that your operating
    7. InnoDB: system has corrupted its own file cache
    8. InnoDB: and rebooting your computer removes the
    9. InnoDB: error.
    10. InnoDB: If the corrupt page is an index page
    11. InnoDB: you can also try to fix the corruption
    12. InnoDB: by dumping, dropping, and reimporting
    13. InnoDB: the corrupt table. You can use CHECK
    14. InnoDB: TABLE to scan your table for corruption.
    15. InnoDB: See also MySQL :: MySQL 5.6 Reference Manual :: 14.21.2 Forcing InnoDB Recovery
    16. InnoDB: about forcing recovery.
    17. InnoDB: Ending processing because of a corrupt database page.
    18. 2016-07-30 18:25:52 7f33b434e740 InnoDB: Assertion failure in thread 139860043425600 in file buf0buf.cc line 4295
    19. InnoDB: We intentionally generate a memory trap.
    20. InnoDB: Submit a detailed bug report to MySQL Bugs.
    21. InnoDB: If you get repeated assertion failures or crashes, even
    22. InnoDB: immediately after the mysqld startup, there may be
    23. InnoDB: corruption in the InnoDB tablespace. Please refer to
    24. InnoDB: MySQL :: MySQL 5.6 Reference Manual :: 14.21.2 Forcing InnoDB Recovery
    25. InnoDB: about forcing recovery.
    26. 16:25:52 UTC - mysqld got signal 6 ;
    27. This could be because you hit a bug. It is also possible that this binary
    28. or one of the libraries it was linked against is corrupt, improperly built,
    29. or misconfigured. This error can also be caused by malfunctioning hardware.
    30. We will try our best to scrape up some info that will hopefully help
    31. diagnose the problem, but since we have already crashed,
    32. something is definitely wrong and this may fail.
    33. key_buffer_size=8388608
    34. read_buffer_size=131072
    35. max_used_connections=0
    36. max_threads=151
    37. thread_count=0
    38. connection_count=0
    39. It is possible that mysqld could use up to
    40. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68095 K bytes of memory
    41. Hope that's ok; if not, decrease some variables in the equation.
    42. Thread pointer: 0x0
    43. Attempting backtrace. You can use the following information to find out
    44. where mysqld died. If you see no messages after this, something went
    45. terribly wrong...
    46. stack_bottom = 0 thread_stack 0x40000
    47. /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x7f33b4a83cec]
    48. /usr/sbin/mysqld(handle_fatal_signal+0x481)[0x7f33b481c851]
    49. /lib64/libpthread.so.0(+0xf870)[0x7f33b2e5d870]
    50. /lib64/libc.so.6(gsignal+0x37)[0x7f33b22bc0a7]
    51. /lib64/libc.so.6(abort+0x118)[0x7f33b22bd458]
    52. /usr/sbin/mysqld(+0x8883a8)[0x7f33b4c033a8]
    53. /usr/sbin/mysqld(+0x89bd98)[0x7f33b4c16d98]
    54. /usr/sbin/mysqld(+0x883345)[0x7f33b4bfe345]
    55. /usr/sbin/mysqld(+0x848c32)[0x7f33b4bc3c32]
    56. /usr/sbin/mysqld(+0x83e23f)[0x7f33b4bb923f]
    57. /usr/sbin/mysqld(+0x83ee45)[0x7f33b4bb9e45]
    58. /usr/sbin/mysqld(+0x83fdf7)[0x7f33b4bbadf7]
    59. /usr/sbin/mysqld(+0x8299ae)[0x7f33b4ba49ae]
    60. /usr/sbin/mysqld(+0x767d1c)[0x7f33b4ae2d1c]
    61. /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x7f33b4760878]
    62. /usr/sbin/mysqld(+0x528531)[0x7f33b48a3531]
    63. /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x940)[0x7f33b48a99b0]
    64. /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x8b8)[0x7f33b475a368]
    65. /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f33b22a8b05]
    66. /usr/sbin/mysqld(+0x3d22ad)[0x7f33b474d2ad]
    67. The manual page at MySQL :: MySQL 5.7 Reference Manual :: B.5.3.3 What to Do If MySQL Keeps Crashing contains
    68. information that should help you find out what is causing the crash.
    Alles anzeigen
    Konsolenausgaben bitte in Code-Tags

    Für den Inhalt des Beitrages 97348 haftet ausdrücklich der jeweilige Autor: kaiwe

  • auch an dieser Stelle danke für den Hinweis !

    Ich hoffe, es hilft mir trotzdem jemand.

    Vielen Dank schon mal !

    Für den Inhalt des Beitrages 97350 haftet ausdrücklich der jeweilige Autor: kaiwe

  • Einfache Möglichkeit:
    Backup einspielen.

    Professionelle Möglichkeit:
    Dealing with corrupted InnoDB data - Percona Database Performance Blog
    Links in dieser Signatur bitte zum Lesen anklicken!

    Code-Tags <<<Klick mich
    zypper <<<Klick mich
    Netzwerkprobleme <<<Klick mich

    Für den Inhalt des Beitrages 97351 haftet ausdrücklich der jeweilige Autor: Sauerland