Hi!
nach einem apt-get upgrade gestern spinnt mein Mysql-Server :-(
Hat jemand eine Idee?? Ich dachte ja zuerst, dass es am bin_log liegt
... aber das abgeschaltet liefert immer noch das selbe Problem.
LAMP besteht aus apache1.x, PHP 4.X und MySQL 5 - PHP 5 geht leider
nicht :-(
Das ganze laeuft in einer virtuellen Umgebung (Debian in VMWare) mit 1
GB RAM zugewiesen
ich bin ein wenig ratlos ...
Hier einmal die Log-Datei ...
-- cut here --
Sep 21 19:03:42 s3-server mysqld[3351]: mysqld got signal 11;
Sep 21 19:03:42 s3-server mysqld[3351]: This could be because you hit
a bug. It is also possible that this binary
Sep 21 19:03:42 s3-server mysqld[3351]: or one of the libraries it was
linked against is corrupt, improperly built,
Sep 21 19:03:42 s3-server mysqld[3351]: or misconfigured. This error
can also be caused by malfunctioning hardware.
Sep 21 19:03:42 s3-server mysqld[3351]: We will try our best to scrape
up some info that will hopefully help diagnose
Sep 21 19:03:42 s3-server mysqld[3351]: the problem, but since we have
already crashed, something is definitely wrong
Sep 21 19:03:42 s3-server mysqld[3351]: and this may fail.
Sep 21 19:03:42 s3-server mysqld[3351]:
Sep 21 19:03:42 s3-server mysqld[3351]: key_buffer_size=16777216
Sep 21 19:03:42 s3-server mysqld[3351]: read_buffer_size=131072
Sep 21 19:03:42 s3-server mysqld[3351]: max_used_connections=2
Sep 21 19:03:42 s3-server mysqld[3351]: max_connections=250
Sep 21 19:03:42 s3-server mysqld[3351]: threads_connected=2
Sep 21 19:03:42 s3-server mysqld[3351]: It is possible that mysqld
could use up to
Sep 21 19:03:42 s3-server mysqld[3351]: key_buffer_size +
(read_buffer_size + sort_buffer_size)*max_connections = 560382 K
Sep 21 19:03:42 s3-server mysqld[3351]: bytes of memory
Sep 21 19:03:42 s3-server mysqld[3351]: Hope that's ok; if not,
decrease some variables in the equation.
Sep 21 19:03:42 s3-server mysqld[3351]:
Sep 21 19:03:42 s3-server mysqld[3351]: thd=0x8ae67b0
Sep 21 19:03:42 s3-server mysqld[3351]: Attempting backtrace. You can
use the following information to find out
Sep 21 19:03:42 s3-server mysqld[3351]: where mysqld died. If you see
no messages after this, something went
Sep 21 19:03:42 s3-server mysqld[3351]: terribly wrong...
Sep 21 19:03:42 s3-server mysqld[3351]: Cannot determine thread,
fp=0xb3f717d8, backtrace may not be correct.
Sep 21 19:03:42 s3-server mysqld[3351]: Stack range sanity check OK,
backtrace follows:
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81c0759
Sep 21 19:03:42 s3-server mysqld[3351]: 0xb7d19e30
Sep 21 19:03:42 s3-server mysqld[3351]: 0xb7d1b9ef
Sep 21 19:03:42 s3-server mysqld[3351]: 0x8485476
Sep 21 19:03:42 s3-server mysqld[3351]: 0x820202c
Sep 21 19:03:42 s3-server mysqld[3351]: 0x82033c5
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81fc8b8
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81fde24
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81fe495
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81fe6dd
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81d7843
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81dbeb7
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81dc370
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81dd648
Sep 21 19:03:42 s3-server mysqld[3351]: 0x81de054
Sep 21 19:03:42 s3-server mysqld[3351]: 0xb7f44240
Sep 21 19:03:42 s3-server mysqld[3351]: 0xb7d7f49e
Sep 21 19:03:42 s3-server mysqld[3351]: New value of fp=(nil) failed
sanity check, terminating stack trace!
Sep 21 19:03:42 s3-server mysqld[3351]: Please read
http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow
instructions on how to resolve the stack trace. Resolved
Sep 21 19:03:42 s3-server mysqld[3351]: stack trace is much more
helpful in diagnosing the problem, so please do
Sep 21 19:03:42 s3-server mysqld[3351]: resolve it
Sep 21 19:03:42 s3-server mysqld[3351]: Trying to get some variables.
Sep 21 19:03:42 s3-server mysqld[3351]: Some pointers may be invalid
and cause the dump to abort...
Sep 21 19:03:42 s3-server mysqld[3351]: thd->query at 0x8b11eb8 =
SELECT content
Sep 21 19:03:42 s3-server mysqld[3351]: ^I^I^IFROM cache_hash
Sep 21 19:03:42 s3-server mysqld[3351]: ^I^I^IWHERE
Sep 21 19:03:42 s3-server mysqld[3351]:
^I^I^I^Ihash='629aeba07ffaa4435d2c22e052d9bed7'
Sep 21 19:03:42 s3-server mysqld[3351]: thd->thread_id=2
Sep 21 19:03:42 s3-server mysqld[3351]: The manual page at
http://www.mysql.com/doc/en/Crashing.html contains
Sep 21 19:03:42 s3-server mysqld[3351]: information that should help
you find out what is causing the crash.
--- cut here --