Number of processes running now: 0
070413 08:57:27 mysqld restarted
070413 8:57:27 InnoDB: Started; log sequence number 0 43655
070413 8:57:27 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.18' socket: '/var/lib/mysql/mysql.sock' port: 3306 SUSE MySQL RPM
edge:~ # tail -n 100 /var/log/mysqld.log
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8a92108
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=0xb4f67488, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817de07
0xffffe420
0xb4f67828
0xb7d1bf8b
0xb7d21911
0xb7d22f84
0x83ef351
0x83ef931
0x819dc05
0x819f1b3
0x819fc1d
0xb7f3c34b
0xb7d7b65e
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is invalid pointer
thd->thread_id=185
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.
070413 8:56:33 [Note] /usr/sbin/mysqld: Normal shutdown
Number of processes running now: 0
070413 08:56:39 mysqld restarted