MySQL Forums
Forum List  »  Newbie

Mysql 4.x startup crash!
Posted by: tim o
Date: March 27, 2005 04:51PM

I recently installed phpbb on my system, installed Mysql from RPM, restarted now i get this error:

Number of processes running now: 0
050327 17:49:08 mysqld restarted
050327 17:49:09 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 43644
InnoDB: Doing recovery: scanned up to log sequence number 0 43644
050327 17:49:09 InnoDB: Flushing modified pages from the buffer pool...
050327 17:49:09 InnoDB: Started
050327 17:49:09 Found invalid password for user: 'root'@'localhost'; Ignoring user
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=16384
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 = 19215 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x882a2e8
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=0xbfffeb04, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81025a1
0xffffe420
0x838ae40
0x8150229
0x8105606
0x401a9ea0
0x80b52c1
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/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=0
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.



any ideas?

Options: ReplyQuote


Subject
Written By
Posted
Mysql 4.x startup crash!
March 27, 2005 04:51PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.