Top-Themen

AppleEntwicklungHardwareInternetLinuxMicrosoftMultimediaNetzwerkeOff TopicSicherheitSonstige SystemeVirtualisierungWeiterbildungZusammenarbeit

Aktuelle Themen

Administrator.de FeedbackApache ServerAppleAssemblerAudioAusbildungAuslandBackupBasicBatch & ShellBenchmarksBibliotheken & ToolkitsBlogsCloud-DiensteClusterCMSCPU, RAM, MainboardsCSSC und C++DatenbankenDatenschutzDebianDigitiales FernsehenDNSDrucker und ScannerDSL, VDSLE-BooksE-BusinessE-MailEntwicklungErkennung und -AbwehrExchange ServerFestplatten, SSD, RaidFirewallFlatratesGoogle AndroidGrafikGrafikkarten & MonitoreGroupwareHardwareHosting & HousingHTMLHumor (lol)Hyper-VIconsIDE & EditorenInformationsdiensteInstallationInstant MessagingInternetInternet DomäneniOSISDN & AnaloganschlüsseiTunesJavaJavaScriptKiXtartKVMLAN, WAN, WirelessLinuxLinux DesktopLinux NetzwerkLinux ToolsLinux UserverwaltungLizenzierungMac OS XMicrosoftMicrosoft OfficeMikroTik RouterOSMonitoringMultimediaMultimedia & ZubehörNetzwerkeNetzwerkgrundlagenNetzwerkmanagementNetzwerkprotokolleNotebook & ZubehörNovell NetwareOff TopicOpenOffice, LibreOfficeOutlook & MailPapierkorbPascal und DelphiPeripheriegerätePerlPHPPythonRechtliche FragenRedHat, CentOS, FedoraRouter & RoutingSambaSAN, NAS, DASSchriftartenSchulung & TrainingSEOServerServer-HardwareSicherheitSicherheits-ToolsSicherheitsgrundlagenSolarisSonstige SystemeSoziale NetzwerkeSpeicherkartenStudentenjobs & PraktikumSuche ProjektpartnerSuseSwitche und HubsTipps & TricksTK-Netze & GeräteUbuntuUMTS, EDGE & GPRSUtilitiesVB for ApplicationsVerschlüsselung & ZertifikateVideo & StreamingViren und TrojanerVirtualisierungVisual StudioVmwareVoice over IPWebbrowserWebentwicklungWeiterbildungWindows 7Windows 8Windows 10Windows InstallationWindows MobileWindows NetzwerkWindows ServerWindows SystemdateienWindows ToolsWindows UpdateWindows UserverwaltungWindows VistaWindows XPXenserverXMLZusammenarbeit

MySQL defekt nach Festplattentausch

Frage Linux Ubuntu

Mitglied: mikahaapamaeki

mikahaapamaeki (Level 1) - Jetzt verbinden

11.06.2013 um 12:38 Uhr, 3200 Aufrufe, 17 Kommentare

Hallo ihr Lieben!

gestern ist unserem Server bei Hetzner eine Platte abgeraucht, neue wurde eingebaut und Spiegelung über Nacht zurückgespielt. Soweit alles gut.
Nun Läuft aber mein MySQL Server nimmer... habe schon alles probiert nur keine Anleitung die ich gefunden habe klappt... ensprechend gehen auch die CMS basierten Webseiten und das Zarafa E-Mail System nimmer...

Ich bitte dringend um Hilfe da wir seit gestern keine Mails mehr empfangen oder versenden...

Vielen Dank!!!!!

01.
10:25:19 UTC - mysqld got signal 11 ; 
02.
This could be because you hit a bug. It is also possible that this binary 
03.
or one of the libraries it was linked against is corrupt, improperly built, 
04.
or misconfigured. This error can also be caused by malfunctioning hardware. 
05.
We will try our best to scrape up some info that will hopefully help 
06.
diagnose the problem, but since we have already crashed, 
07.
something is definitely wrong and this may fail. 
08.
 
09.
key_buffer_size=16777216 
10.
read_buffer_size=131072 
11.
max_used_connections=0 
12.
max_threads=151 
13.
thread_count=0 
14.
connection_count=0 
15.
It is possible that mysqld could use up to 
16.
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346682 K  bytes of memory 
17.
Hope that's ok; if not, decrease some variables in the equation. 
18.
 
19.
Thread pointer: 0x0 
20.
Attempting backtrace. You can use the following information to find out 
21.
where mysqld died. If you see no messages after this, something went 
22.
terribly wrong... 
23.
stack_bottom = 0 thread_stack 0x30000 
24.
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7f725f2197b9] 
25.
/usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7f725f0df8f3] 
26.
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f725de2ccb0] 
27.
/usr/sbin/mysqld(+0x6a57ee)[0x7f725f3697ee] 
28.
/usr/sbin/mysqld(+0x6a1955)[0x7f725f365955] 
29.
/usr/sbin/mysqld(+0x6a1a4f)[0x7f725f365a4f] 
30.
/usr/sbin/mysqld(+0x67c675)[0x7f725f340675] 
31.
/usr/sbin/mysqld(+0x6011d5)[0x7f725f2c51d5] 
32.
/usr/sbin/mysqld(+0x5cae89)[0x7f725f28ee89] 
33.
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7f725f0e1fc1] 
34.
/usr/sbin/mysqld(+0x30afc1)[0x7f725efcefc1] 
35.
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa94)[0x7f725efd25e4] 
36.
/usr/sbin/mysqld(+0x284686)[0x7f725ef48686] 
37.
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x59b)[0x7f725ef4be2b] 
38.
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f725d48376d] 
39.
/usr/sbin/mysqld(+0x27e1b5)[0x7f725ef421b5] 
40.
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains 
41.
information that should help you find out what is causing the crash. 
42.
 
43.
 
44.
 
Mitglied: colinardo
11.06.2013 um 13:02 Uhr
Hi mikahaapamaeki,
hast du das in der mysql-Anleitung auch schon probiert ?:
Stop the mysqld server with mysqladmin shutdown, run myisamchk --silent --force */*.MYI from the data directory to check all MyISAM tables, and restart mysqld. This ensures that you are running from a clean state. See Chapter 5, MySQL Server Administration.

Grüße Uwe
Bitte warten ..
Mitglied: mikahaapamaeki
11.06.2013, aktualisiert um 13:10 Uhr
Das kam dabei raus ...

01.
root@server ~ # mysqladmin shutdown 
02.
mysqladmin: connect to server at 'localhost' failed 
03.
error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)' 
04.
Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! 
05.
root@server ~ # myisamchk --silent --force */*.MYI  
06.
myisamchk: error: File '*/*.MYI' doesn't exist 
07.
myisamchk: error: File '*/*.MYI' doesn't exist 
08.
root@server ~ #
Gruß,
Mika

EDIT

ggf hilft das ja weiter...

01.
root@server ~ # /etc/init.d/mysql start 
02.
Rather than invoking init scripts through /etc/init.d, use the service(8) 
03.
utility, e.g. service mysql start 
04.
 
05.
Since the script you are attempting to invoke has been converted to an 
06.
Upstart job, you may also use the start(8) utility, e.g. start mysql 
07.
mysql start/running, process 6176 
08.
root@server ~ # service mysql status 
09.
mysql stop/waiting 
10.
root@server ~ # 
Bitte warten ..
Mitglied: colinardo
11.06.2013, aktualisiert um 13:15 Uhr
/etc/init.d/mysql stop
run myisamchk --silent --force */*.MYI from the data directory
klar wenn du das im home-Verzeichnis machst, kann er nix finden

Das Standard-Datenverzeichnis lautet:
/var/lib/mysql
Bitte warten ..
Mitglied: mikahaapamaeki
11.06.2013, aktualisiert um 13:38 Uhr
habe es in /var/lib/mysql geamcht, lief durch, habe dann service mysql start gemacht aber immernoch mysql stop/waiting
Aber mein Zarafa-Server funkt nun auf einmal... leider komme ich aber immernoch nicht rein da mysql nicht läuft...

01.
 
02.
root@server /var/lib/mysql # myisamchk --silent --force */*.MYI 
03.
myisamchk: MyISAM file bmwv/PageStatistics.MYI 
04.
myisamchk: error: Found key at page 143360 that points to record outside datafile 
05.
myisamchk: Unknown error 126 
06.
myisamchk: MyISAM file vhaus@002dohg/PageSearchIndex.MYI 
07.
myisamchk: error: Keyblock size at page 32768 is not correct.  Block length: 902  key length: 49 
08.
 
habe es noch mal wiederholt und es kam nichts... zarafa-server und mysql starten immer noch nicht...
Bitte warten ..
Mitglied: mikahaapamaeki
11.06.2013 um 13:39 Uhr
kann ich mysql irgendwie neu installieren ohne die Datenbanken zu verlieren?
Bitte warten ..
Mitglied: colinardo
11.06.2013, aktualisiert um 13:42 Uhr
ich weiß jetzt nicht ob deine Datenbank InnoDB oder ISAM Datenbanken benutzt aber für InnoDB kann man in die mysql Konfigurationsdatei folgenden Eintrag hinzufügen um den Recovery-Modus zu starten:
[mysqld] 
innodb_force_recovery = 4
Und danach einen Dump der Tabellen machen.
Siehe dazu folgendes PDF Seite 29

Am einfachsten wäre es ein Backup zurückzuspielen, aber ich denke das hast du wahrscheinlich nicht ...
Bitte warten ..
Mitglied: colinardo
11.06.2013, aktualisiert um 13:48 Uhr
Zitat von mikahaapamaeki:
kann ich mysql irgendwie neu installieren ohne die Datenbanken zu verlieren?
Denke dass es nicht an der MySQL-Installation liegt sondern an den Datenbanken die durch den Ausfall der Platte irgendwo beschädigt worden sind.
Bitte warten ..
Mitglied: mikahaapamaeki
11.06.2013, aktualisiert um 13:46 Uhr
Backup habe ich bisher nicht gemacht da mir das RAID1 als "ausreichend galt..."

Wenn ich den dump machen will kommt folgender Fehler...

mysqldump: Couldn't execute 'UNLOCK TABLES': Lost connection to MySQL server during query (2013)

hmm die Datenbanken kann man doch sicherlich irgendwie reparieren oder?
Bitte warten ..
Mitglied: colinardo
11.06.2013, aktualisiert um 13:54 Uhr
Backup habe ich bisher nicht gemacht da mir das RAID1 als "ausreichend galt..."
Das wird dir eine Lehre sein ...RAID ersetzt kein Backup !

probier mal :
mysqlcheck -Aor
oder
mysqlcheck --all-databases -r #repair 
mysqlcheck --all-databases -a #analyze 
mysqlcheck --all-databases -o #optimize
als root
Bitte warten ..
Mitglied: mikahaapamaeki
11.06.2013 um 14:07 Uhr
jetzt geht nichts mehr...

start: Job failed to start

wenn ich versuche mysql zu starten... ich stehe echt kurz davor alles einfach hinzuschmeißen und abzuhauen... was ist denn jetzt schonwieder???
Bitte warten ..
Mitglied: mikahaapamaeki
11.06.2013 um 16:50 Uhr
hier noch eine Info, ggf sagt euch das was ?!?

01.
root@server /etc/mysql # dmesg | grep mysql 
02.
[   13.673454] type=1400 audit(1370961675.701:11): apparmor="STATUS" operation="profile_load" name="/usr/sbin/mysqld" pid=946 comm="apparmor_parser" 
03.
[   13.843446] init: mysql main process (1027) terminated with status 1 
04.
[   13.843464] init: mysql main process ended, respawning 
05.
[   14.734502] init: mysql post-start process (1029) terminated with status 1 
06.
[   14.759071] init: mysql main process (1287) terminated with status 1 
07.
[   14.759086] init: mysql main process ended, respawning 
08.
[   15.749974] init: mysql post-start process (1288) terminated with status 1 
09.
[   15.789021] init: mysql main process (1330) terminated with status 1 
10.
[   15.789055] init: mysql respawning too fast, stopped 
11.
[  115.381602] type=1400 audit(1370961777.125:25): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2646 comm="apparmor_parser" 
12.
[  115.419482] init: mysql main process (2650) terminated with status 1 
13.
[  115.419514] init: mysql main process ended, respawning 
14.
[  116.401268] init: mysql post-start process (2651) terminated with status 1 
15.
[  116.409737] type=1400 audit(1370961778.153:26): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2684 comm="apparmor_parser" 
16.
[  116.449316] init: mysql main process (2688) terminated with status 1 
17.
[  116.449350] init: mysql main process ended, respawning 
18.
[  117.428930] init: mysql post-start process (2689) terminated with status 1 
19.
[  117.437369] type=1400 audit(1370961779.181:27): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2722 comm="apparmor_parser" 
20.
[  117.472016] init: mysql main process (2726) terminated with status 1 
21.
[  117.472049] init: mysql respawning too fast, stopped 
22.
[  386.483461] type=1400 audit(1370962048.385:28): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2779 comm="apparmor_parser" 
23.
[  386.523267] init: mysql main process (2783) terminated with status 1 
24.
[  386.523282] init: mysql main process ended, respawning 
25.
[  387.502949] init: mysql post-start process (2784) terminated with status 1 
26.
[  387.511275] type=1400 audit(1370962049.413:29): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2817 comm="apparmor_parser" 
27.
[  387.550574] init: mysql main process (2821) terminated with status 1 
28.
[  387.550608] init: mysql main process ended, respawning 
29.
[  388.530955] init: mysql post-start process (2822) terminated with status 1 
30.
[  388.539250] type=1400 audit(1370962050.441:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2855 comm="apparmor_parser" 
31.
[  388.573423] init: mysql main process (2859) terminated with status 1 
32.
[  388.573456] init: mysql respawning too fast, stopped 
33.
[  415.137346] type=1400 audit(1370962077.053:31): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2904 comm="apparmor_parser" 
34.
[  415.172988] init: mysql main process (2908) terminated with status 1 
35.
[  415.173023] init: mysql main process ended, respawning 
36.
[  416.156999] init: mysql post-start process (2909) terminated with status 1 
37.
[  416.165521] type=1400 audit(1370962078.085:32): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2942 comm="apparmor_parser" 
38.
[  416.205439] init: mysql main process (2946) terminated with status 1 
39.
[  416.205454] init: mysql main process ended, respawning 
40.
[  417.185076] init: mysql post-start process (2947) terminated with status 1 
41.
[  417.193539] type=1400 audit(1370962079.113:33): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2980 comm="apparmor_parser" 
42.
[  417.233167] init: mysql main process (2984) terminated with status 1 
43.
[  417.233202] init: mysql respawning too fast, stopped 
44.
root@server /etc/mysql # 
Bitte warten ..
Mitglied: mikahaapamaeki
11.06.2013, aktualisiert um 18:33 Uhr
Also um mal zum Abschluss zu kommen... ich hoffe nur ich nerve nicht langsam... Aber vielen Dank schonmal für die Hilfe
Error log habe ich komplett geleert und einmal versucht mysql zu starten das ist alles was da kommt...

01.
130611 18:30:55 [Note] Plugin 'FEDERATED' is disabled. 
02.
130611 18:30:55 InnoDB: The InnoDB memory heap is disabled 
03.
130611 18:30:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
04.
130611 18:30:55 InnoDB: Compressed tables use zlib 1.2.3.4 
05.
130611 18:30:55 InnoDB: Initializing buffer pool, size = 3.9G 
06.
130611 18:30:55 InnoDB: Completed initialization of buffer pool 
07.
130611 18:30:55 InnoDB: highest supported file format is Barracuda. 
08.
InnoDB: Database page corruption on disk or a failed 
09.
InnoDB: file read of page 220. 
10.
InnoDB: You may have to recover from a backup. 
11.
130611 18:30:55  InnoDB: Page dump in ascii and hex (16384 bytes): 
12.
 len 16384; hex d4b4c382000000dc000000000000000000000003a8e3ddc40006000000000000000000000000fffffffe00000000000000060000c2d405df0000c2d4007800000000000000022eb20000c2d40000431bfffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff$ 
13.
InnoDB: End of page dump 
14.
130611 18:30:55  InnoDB: Page checksum 579790626, prior-to-4.0.14-form checksum 3456036086 
15.
InnoDB: stored checksum 3568616322, prior-to-4.0.14-form stored checksum 3456036086 
16.
InnoDB: Page lsn 3 2833505732, low 4 bytes of lsn at page end 2833505732 
17.
InnoDB: Page number (if stored to page already) 220, 
18.
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 
19.
InnoDB: Page may be a system page 
20.
InnoDB: Database page corruption on disk or a failed 
21.
InnoDB: file read of page 220. 
22.
InnoDB: You may have to recover from a backup. 
23.
InnoDB: It is also possible that your operating 
24.
InnoDB: system has corrupted its own file cache 
25.
InnoDB: and rebooting your computer removes the 
26.
InnoDB: error. 
27.
InnoDB: If the corrupt page is an index page 
28.
InnoDB: you can also try to fix the corruption 
29.
InnoDB: by dumping, dropping, and reimporting 
30.
InnoDB: the corrupt table. You can use CHECK 
31.
InnoDB: TABLE to scan your table for corruption. 
32.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html 
33.
InnoDB: about forcing recovery. 
34.
InnoDB: Ending processing because of a corrupt database page. 
35.
130611 18:30:55  InnoDB: Assertion failure in thread 140574115022656 in file buf0buf.c line 3629 
36.
InnoDB: We intentionally generate a memory trap. 
37.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 
38.
InnoDB: If you get repeated assertion failures or crashes, even 
39.
InnoDB: immediately after the mysqld startup, there may be 
40.
InnoDB: corruption in the InnoDB tablespace. Please refer to 
41.
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html 
42.
InnoDB: about forcing recovery. 
43.
16:30:55 UTC - mysqld got signal 6 ; 
44.
This could be because you hit a bug. It is also possible that this binary 
45.
or one of the libraries it was linked against is corrupt, improperly built, 
46.
or misconfigured. This error can also be caused by malfunctioning hardware. 
47.
We will try our best to scrape up some info that will hopefully help 
48.
diagnose the problem, but since we have already crashed, 
49.
something is definitely wrong and this may fail. 
50.
 
51.
key_buffer_size=16777216 
52.
read_buffer_size=131072 
53.
max_used_connections=0 
54.
max_threads=151 
55.
thread_count=0 
56.
connection_count=0 
57.
It is possible that mysqld could use up to 
58.
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346682 K  bytes of memory 
59.
Hope that's ok; if not, decrease some variables in the equation. 
60.
 
61.
Thread pointer: 0x0 
62.
Attempting backtrace. You can use the following information to find out 
63.
where mysqld died. If you see no messages after this, something went 
64.
terribly wrong... 
65.
stack_bottom = 0 thread_stack 0x30000 
66.
terribly wrong... 
67.
stack_bottom = 0 thread_stack 0x30000 
68.
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7fd9f68767b9] 
69.
/usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7fd9f673c8f3] 
70.
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7fd9f5489cb0] 
71.
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7fd9f4af5425] 
72.
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7fd9f4af8b8b] 
73.
/usr/sbin/mysqld(+0x645171)[0x7fd9f6966171] 
74.
/usr/sbin/mysqld(+0x6509e8)[0x7fd9f69719e8] 
75.
/usr/sbin/mysqld(+0x65138c)[0x7fd9f697238c] 
76.
/usr/sbin/mysqld(+0x640c16)[0x7fd9f6961c16] 
77.
/usr/sbin/mysqld(+0x6122a6)[0x7fd9f69332a6] 
78.
/usr/sbin/mysqld(+0x61305c)[0x7fd9f693405c] 
79.
/usr/sbin/mysqld(+0x614a03)[0x7fd9f6935a03] 
80.
/usr/sbin/mysqld(+0x6011cc)[0x7fd9f69221cc] 
81.
/usr/sbin/mysqld(+0x5cae89)[0x7fd9f68ebe89] 
82.
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fd9f673efc1] 
83.
/usr/sbin/mysqld(+0x30afc1)[0x7fd9f662bfc1] 
84.
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa94)[0x7fd9f662f5e4] 
85.
/usr/sbin/mysqld(+0x284686)[0x7fd9f65a5686] 
86.
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x59b)[0x7fd9f65a8e2b] 
87.
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fd9f4ae076d] 
88.
/usr/sbin/mysqld(+0x27e1b5)[0x7fd9f659f1b5] 
89.
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains 
90.
information that should help you find out what is causing the crash. 
91.
130611 18:30:56 [Note] Plugin 'FEDERATED' is disabled. 
92.
130611 18:30:56 InnoDB: The InnoDB memory heap is disabled 
93.
130611 18:30:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
94.
130611 18:30:56 InnoDB: Compressed tables use zlib 1.2.3.4 
95.
130611 18:30:56 InnoDB: Initializing buffer pool, size = 3.9G 
96.
130611 18:30:56 InnoDB: Completed initialization of buffer pool 
97.
130611 18:30:56 InnoDB: highest supported file format is Barracuda. 
98.
InnoDB: Database page corruption on disk or a failed 
99.
InnoDB: file read of page 220. 
100.
InnoDB: You may have to recover from a backup. 
101.
130611 18:30:56  InnoDB: Page dump in ascii and hex (16384 bytes): 
102.
 len 16384; hex d4b4c382000000dc000000000000000000000003a8e3ddc40006000000000000000000000000fffffffe00000000000000060000c2d405df0000c2d4007800000000000000022eb20000c2d40000431bfffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff$ 
103.
InnoDB: End of page dump 
104.
130611 18:30:56  InnoDB: Page checksum 579790626, prior-to-4.0.14-form checksum 3456036086 
105.
InnoDB: stored checksum 3568616322, prior-to-4.0.14-form stored checksum 3456036086 
106.
InnoDB: Page lsn 3 2833505732, low 4 bytes of lsn at page end 2833505732 
107.
InnoDB: Page number (if stored to page already) 220, 
108.
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 
109.
InnoDB: Page may be a system page 
110.
InnoDB: Database page corruption on disk or a failed 
111.
InnoDB: file read of page 220. 
112.
InnoDB: You may have to recover from a backup. 
113.
InnoDB: It is also possible that your operating 
114.
InnoDB: system has corrupted its own file cache 
115.
InnoDB: and rebooting your computer removes the 
116.
InnoDB: error. 
117.
InnoDB: If the corrupt page is an index page 
118.
InnoDB: you can also try to fix the corruption 
119.
InnoDB: by dumping, dropping, and reimporting 
120.
InnoDB: the corrupt table. You can use CHECK 
121.
InnoDB: TABLE to scan your table for corruption. 
122.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html 
123.
InnoDB: about forcing recovery. 
124.
InnoDB: Ending processing because of a corrupt database page. 
125.
130611 18:30:56  InnoDB: Assertion failure in thread 140198699333440 in file buf0buf.c line 3629 
126.
InnoDB: We intentionally generate a memory trap. 
127.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 
128.
InnoDB: If you get repeated assertion failures or crashes, even 
129.
InnoDB: immediately after the mysqld startup, there may be 
130.
InnoDB: corruption in the InnoDB tablespace. Please refer to 
131.
InnoDB: immediately after the mysqld startup, there may be 
132.
InnoDB: corruption in the InnoDB tablespace. Please refer to 
133.
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html 
134.
InnoDB: about forcing recovery. 
135.
16:30:56 UTC - mysqld got signal 6 ; 
136.
This could be because you hit a bug. It is also possible that this binary 
137.
or one of the libraries it was linked against is corrupt, improperly built, 
138.
or misconfigured. This error can also be caused by malfunctioning hardware. 
139.
We will try our best to scrape up some info that will hopefully help 
140.
diagnose the problem, but since we have already crashed, 
141.
something is definitely wrong and this may fail. 
142.
 
143.
key_buffer_size=16777216 
144.
read_buffer_size=131072 
145.
max_used_connections=0 
146.
max_threads=151 
147.
thread_count=0 
148.
connection_count=0 
149.
It is possible that mysqld could use up to 
150.
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346682 K  bytes of memory 
151.
Hope that's ok; if not, decrease some variables in the equation. 
152.
 
153.
Thread pointer: 0x0 
154.
Attempting backtrace. You can use the following information to find out 
155.
where mysqld died. If you see no messages after this, something went 
156.
terribly wrong... 
157.
stack_bottom = 0 thread_stack 0x30000 
158.
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7f828e0297b9] 
159.
/usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7f828deef8f3] 
160.
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f828cc3ccb0] 
161.
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f828c2a8425] 
162.
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7f828c2abb8b] 
163.
/usr/sbin/mysqld(+0x645171)[0x7f828e119171] 
164.
/usr/sbin/mysqld(+0x6509e8)[0x7f828e1249e8] 
165.
/usr/sbin/mysqld(+0x65138c)[0x7f828e12538c] 
166.
/usr/sbin/mysqld(+0x640c16)[0x7f828e114c16] 
167.
/usr/sbin/mysqld(+0x6122a6)[0x7f828e0e62a6] 
168.
/usr/sbin/mysqld(+0x61305c)[0x7f828e0e705c] 
169.
/usr/sbin/mysqld(+0x614a03)[0x7f828e0e8a03] 
170.
/usr/sbin/mysqld(+0x6011cc)[0x7f828e0d51cc] 
171.
/usr/sbin/mysqld(+0x5cae89)[0x7f828e09ee89] 
172.
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7f828def1fc1] 
173.
/usr/sbin/mysqld(+0x30afc1)[0x7f828dddefc1] 
174.
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa94)[0x7f828dde25e4] 
175.
/usr/sbin/mysqld(+0x284686)[0x7f828dd58686] 
176.
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x59b)[0x7f828dd5be2b] 
177.
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f828c29376d] 
178.
/usr/sbin/mysqld(+0x27e1b5)[0x7f828dd521b5] 
179.
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains 
180.
information that should help you find out what is causing the crash. 
181.
130611 18:30:57 [Note] Plugin 'FEDERATED' is disabled. 
182.
130611 18:30:57 InnoDB: The InnoDB memory heap is disabled 
183.
130611 18:30:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
184.
130611 18:30:57 InnoDB: Compressed tables use zlib 1.2.3.4 
185.
130611 18:30:57 InnoDB: Initializing buffer pool, size = 3.9G 
186.
130611 18:30:57 InnoDB: Completed initialization of buffer pool 
187.
130611 18:30:57 InnoDB: highest supported file format is Barracuda. 
188.
InnoDB: Database page corruption on disk or a failed 
189.
InnoDB: file read of page 220. 
190.
InnoDB: You may have to recover from a backup. 
191.
130611 18:30:57  InnoDB: Page dump in ascii and hex (16384 bytes): 
192.
 len 16384; hex d4b4c382000000dc000000000000000000000003a8e3ddc40006000000000000000000000000fffffffe00000000000000060000c2d405df0000c2d4007800000000000000022eb20000c2d40000431bfffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff$ 
193.
InnoDB: End of page dump 
194.
130611 18:30:57  InnoDB: Page checksum 579790626, prior-to-4.0.14-form checksum 3456036086 
195.
InnoDB: stored checksum 3568616322, prior-to-4.0.14-form stored checksum 3456036086 
196.
130611 18:30:57  InnoDB: Page checksum 579790626, prior-to-4.0.14-form checksum 3456036086 
197.
InnoDB: stored checksum 3568616322, prior-to-4.0.14-form stored checksum 3456036086 
198.
InnoDB: Page lsn 3 2833505732, low 4 bytes of lsn at page end 2833505732 
199.
InnoDB: Page number (if stored to page already) 220, 
200.
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 
201.
InnoDB: Page may be a system page 
202.
InnoDB: Database page corruption on disk or a failed 
203.
InnoDB: file read of page 220. 
204.
InnoDB: You may have to recover from a backup. 
205.
InnoDB: It is also possible that your operating 
206.
InnoDB: system has corrupted its own file cache 
207.
InnoDB: and rebooting your computer removes the 
208.
InnoDB: error. 
209.
InnoDB: If the corrupt page is an index page 
210.
InnoDB: you can also try to fix the corruption 
211.
InnoDB: by dumping, dropping, and reimporting 
212.
InnoDB: the corrupt table. You can use CHECK 
213.
InnoDB: TABLE to scan your table for corruption. 
214.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html 
215.
InnoDB: about forcing recovery. 
216.
InnoDB: Ending processing because of a corrupt database page. 
217.
130611 18:30:57  InnoDB: Assertion failure in thread 139689218172736 in file buf0buf.c line 3629 
218.
InnoDB: We intentionally generate a memory trap. 
219.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 
220.
InnoDB: If you get repeated assertion failures or crashes, even 
221.
InnoDB: immediately after the mysqld startup, there may be 
222.
InnoDB: corruption in the InnoDB tablespace. Please refer to 
223.
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html 
224.
InnoDB: about forcing recovery. 
225.
16:30:57 UTC - mysqld got signal 6 ; 
226.
This could be because you hit a bug. It is also possible that this binary 
227.
or one of the libraries it was linked against is corrupt, improperly built, 
228.
or misconfigured. This error can also be caused by malfunctioning hardware. 
229.
We will try our best to scrape up some info that will hopefully help 
230.
diagnose the problem, but since we have already crashed, 
231.
something is definitely wrong and this may fail. 
232.
 
233.
key_buffer_size=16777216 
234.
read_buffer_size=131072 
235.
max_used_connections=0 
236.
max_threads=151 
237.
thread_count=0 
238.
connection_count=0 
239.
It is possible that mysqld could use up to 
240.
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346682 K  bytes of memory 
241.
Hope that's ok; if not, decrease some variables in the equation. 
242.
 
243.
Thread pointer: 0x0 
244.
Attempting backtrace. You can use the following information to find out 
245.
where mysqld died. If you see no messages after this, something went 
246.
terribly wrong... 
247.
stack_bottom = 0 thread_stack 0x30000 
248.
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7f0bee9107b9] 
249.
/usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7f0bee7d68f3] 
250.
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f0bed523cb0] 
251.
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f0becb8f425] 
252.
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7f0becb92b8b] 
253.
/usr/sbin/mysqld(+0x645171)[0x7f0beea00171] 
254.
/usr/sbin/mysqld(+0x6509e8)[0x7f0beea0b9e8] 
255.
/usr/sbin/mysqld(+0x65138c)[0x7f0beea0c38c] 
256.
/usr/sbin/mysqld(+0x640c16)[0x7f0bee9fbc16] 
257.
/usr/sbin/mysqld(+0x6122a6)[0x7f0bee9cd2a6] 
258.
/usr/sbin/mysqld(+0x61305c)[0x7f0bee9ce05c] 
259.
/usr/sbin/mysqld(+0x614a03)[0x7f0bee9cfa03] 
260.
/usr/sbin/mysqld(+0x6011cc)[0x7f0bee9bc1cc] 
261.
/usr/sbin/mysqld(+0x614a03)[0x7f0bee9cfa03] 
262.
/usr/sbin/mysqld(+0x6011cc)[0x7f0bee9bc1cc] 
263.
/usr/sbin/mysqld(+0x5cae89)[0x7f0bee985e89] 
264.
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7f0bee7d8fc1] 
265.
/usr/sbin/mysqld(+0x30afc1)[0x7f0bee6c5fc1] 
266.
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa94)[0x7f0bee6c95e4] 
267.
/usr/sbin/mysqld(+0x284686)[0x7f0bee63f686] 
268.
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x59b)[0x7f0bee642e2b] 
269.
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f0becb7a76d] 
270.
/usr/sbin/mysqld(+0x27e1b5)[0x7f0bee6391b5] 
271.
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains 
272.
information that should help you find out what is causing the crash.
Bitte warten ..
Mitglied: mikahaapamaeki
11.06.2013 um 20:20 Uhr
es wurde soeben festgestellt, dass der Arbeitsspeicher ebenfalls einen Defekt aufweist. Könnte dies damit zusammenhängen, dass mein MySQL nicht laufen wollte? Also Server ist erstmal 4-5 Stunden down wegen Prüfung und Tausch
Bitte warten ..
Mitglied: LordGurke
12.06.2013 um 00:40 Uhr
Das wäre sogar sehr wahrscheinlich... Wenn der MySQL seinen Programmcode in den RAM schreibt und irgendein Müll wieder rauskommt kann kein Programm mehr funktionieren ("Page fault" ist ein Hinweis darauf dass entweder der RAM, die CPU oder die MySQL-Binaries defekt sind).

Wenn du Pech hast, hat der MySQL-Server jetzt aber vielleicht sogar die Dateien kaputtgeschrieben - ich hoffe, du hast sie dir vor den Reparaturversuchen irgendwohin kopiert?
Bitte warten ..
Mitglied: mikahaapamaeki
12.06.2013 um 00:45 Uhr
ich hoffe, dass Du die Conf Dateien meinst. Vermute aber eher Du meinst die Datenbankdateien, die ich leider sichern wollte als mir der Server abgestürzt ist... also nein... freue mich schon auf einen sehr unruhigen Schlaf, Danke aber für die Info, zumindest weiß ich, dass es auch daran gelegen haben kann...
Bitte warten ..
Mitglied: mikahaapamaeki
12.06.2013, aktualisiert um 15:49 Uhr
tja... MySQL läuft wieder... und es ist so wie Du es schon gesagt hast... Datenbanken im Ar... habe nur noch die FRM Dateien... kann man da noch was retten?!?

Also die meisten (wichtigen) Tabellen liefen mit MyISAM!!! ich habe also die FRM Daten und die dazugehörige ibdata1 daraus muss man doch was machen können oder`?
Bitte warten ..
Neuester Wissensbeitrag
Humor (lol)

Linkliste für Adventskalender

(3)

Information von nikoatit zum Thema Humor (lol) ...

Ähnliche Inhalte
PHP
PHP MySQL Login (7)

Frage von Yanmai zum Thema PHP ...

Webbrowser
gelöst Daten in entfernte Mysql DB schreiben (3)

Frage von nullacht15 zum Thema Webbrowser ...

Datenbanken
MySQL: Zwei Spalten in einer View zählen (11)

Frage von Memo66 zum Thema Datenbanken ...

Heiß diskutierte Inhalte
Windows Server
DHCP Server switchen (25)

Frage von M.Marz zum Thema Windows Server ...

SAN, NAS, DAS
gelöst HP-Proliant Microserver Betriebssystem (14)

Frage von Yannosch zum Thema SAN, NAS, DAS ...

Grafikkarten & Monitore
Win 10 Grafikkarte Crash von Software? (13)

Frage von Marabunta zum Thema Grafikkarten & Monitore ...

Windows 7
Verteillösung für IT-Raum benötigt (12)

Frage von TheM-Man zum Thema Windows 7 ...