PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : mysql startet nach Reboot nicht mehr :-(



rpq
22.10.07, 09:52
Wegen Wartungsarbeiten wurde mein Root-Server mit SuSe 10.1 heute morgen neu gestartet.
Seitdem startet mysql nicht mehr, verabschiedet sich mit
Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)
Die mysql.sock wird erzeugt mit 0Byte.

rcmysql start
Starting service MySQL done

lässt sich starten,

servi:/var/lib/mysql # mysql start
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

dagegen nicht.

Im mysqld.log findet sich


;InnoDB: End of page dump
071022 9:15:36 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
071022 9:15:36InnoDB: Error: trying to access a stray pointer 0x3734bff8
InnoDB: buf pool start is at 0xb733c000, end at 0xb7b3c000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery,
InnoDB: you can look from section 6.1 at http://www.innodb.com/ibman.html
InnoDB: how to force recovery.
071022 9:15:36InnoDB: Assertion failure in thread 3084056256 in file ./../include/buf0buf.ic line 262
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/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
mysqld got signal 11;
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=0
read_buffer_size=258048
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 76399 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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...
Cannot determine thread, fp=0xbfef864c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81476ad
0xffffe420
0x8374bd5
0x82b5baa
0x8249b41
0x824a730
0x822e50c
0x822c428
0x81dafb9
0x81d0dd6
0x8145c85
0x8149945
0xb7d45ea0
0x80c8b41
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
071022 09:15:36 mysqld ended


Da bin ich leider überfordert :-(

Ob eine Deinstallation vund anschliessende Neuinstallation mit Yast hilft?

Kann mir da evtl. jemand einen Tipp geben, schon mal vielen Dank!!

himbeere
22.10.07, 10:19
071022 9:15:36InnoDB: Error: trying to access a stray pointer 0x3734bff8
InnoDB: buf pool start is at 0xb733c000, end at 0xb7b3c000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery,
InnoDB: you can look from section 6.1 at http://www.innodb.com/ibman.html
InnoDB: how to force recovery.

Haste das probiert?

rpq
22.10.07, 10:35
Die Seite ist nicht mehr verfügbar.

und weiss leider nicht, wie ich auf einen "stray-pointer" zugreife...

rpq
22.10.07, 21:03
Dann will ich mir wenigstens selber die Lösung posten ;-)

Naja, zumindest aber für die nachwelt und Google...

Habe das aktuelle mysql-Directory umbenannt, diesen ganzen Krempel

mysql
mysql client
mysql shared
mysql devel
perl DBD-mysql
php5-mysql
myadmin

deinstalliert, und dann alles neu installiert und die Datenbanken aus dem alten mysql-Directory ins neue kopiert...

Jetzt lööpts wieder :-)