Hi All,
I am using MySQL on a Debian Sarge. I used apt-get to upgrade from 4.0 to 5.0.21. After this upgrade the MySQL server doesn't want to start anymore. I have tried everything that sounded logical to me and have read almost "every" bug or error report on the Internet; but no progress so far.
If I try "/etc/init.d/mysql start", this is what I get:
Quote:
...failed or took more than 6s.
Please take a look at the syslog.
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
|
If try "mysqld_safe", this is what I get then:
Quote:
Starting mysqld daemon with databases from /var/lib/mysql
mysqld_safe[1541]: started
STOPPING server from pid file /var/run/mysqld/mysqld.pid
mysqld_safe[1548]: ended
|
Running "mysqld" gives this:
Quote:
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=16777216
read_buffer_size=131072
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 = 233983 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=0x42327158, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8195bac
0x42327450
(nil)
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Us...ack_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.
|
Does anyone know, what is going on here? Any pointers and help is appreciated.
Thanks in advance.
