List:General Discussion« Previous MessageNext Message »
From:Don Doumakes Date:October 27 2005 9:14pm
Subject:mysqld crashes and restarts on connect attempt
View as plain text  
I'm installing MySQL 4.1.14 on a new Gentoo box.  When I try to connect 
to the mysqld daemon, it crashes and restarts itself, which just doesn't 
seem right.  I enter these commands:

cd /usr; /usr/bin/mysqld_safe &
mysqladmin -u root password 'foobar'

and get this response:

mysqladmin: connect to server at 'localhost' failed
error: 'Lost connection to MySQL server during query'
Number of processes running now: 0
051027 08:09:52 mysqld restarted

mysqld.err contains this:

InnoDB: !!!!!!!!!!!!!! UNIV_DEBUG switched on !!!!!!!!!!!!!!!
InnoDB: The first specified data file /var/lib/mysql/ibdata1 did not exist:
InnoDB: a new database to be created!
051027 8:09:23 InnoDB: Setting file /var/lib/mysql/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
051027 8:09:23 InnoDB: Log file /var/lib/mysql/ib_logfile0 did not 
exist: new to be created
InnoDB: Setting log file /var/lib/mysql/ib_logfile0 size to 8 MB
InnoDB: Database physically writes the file full: wait...
051027 8:09:24 InnoDB: Log file /var/lib/mysql/ib_logfile1 did not 
exist: new to be created
InnoDB: Setting log file /var/lib/mysql/ib_logfile1 size to 8 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
051027 8:09:35 InnoDB: Started; log sequence number 0 0
/usr/sbin/mysqld: ready for connections.
Version: '4.1.14-debug-log' socket: '/var/run/mysqld/mysqld.sock' port: 
3306 Gentoo Linux mysql-4.1.14
mysqld got signal 4;
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=1
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 
= 233980 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8c8ecd8
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=0xb27db898, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81455c1
0xb7dcbe55
0x814b1ed
0x8155ebf
0x815688a
0xb7dc613d
0xb7c361ba
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=1
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.
InnoDB: !!!!!!!!!!!!!! UNIV_DEBUG switched on !!!!!!!!!!!!!!!
051027 8:09:53 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
051027 8:09:53 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 43634.
InnoDB: Doing recovery: scanned up to log sequence number 0 43634
051027 8:09:53 InnoDB: Flushing modified pages from the buffer pool...
051027 8:09:56 InnoDB: Started; log sequence number 0 43634
/usr/sbin/mysqld: ready for connections.
Version: '4.1.14-debug-log' socket: '/var/run/mysqld/mysqld.sock' port: 
3306 Gentoo Linux mysql-4.1.14
Thread
mysqld crashes and restarts on connect attemptDon Doumakes27 Oct
  • Re: mysqld crashes and restarts on connect attemptGleb Paharenko28 Oct
Re: mysqld crashes and restarts on connect attemptDon Doumakes28 Oct
  • Re: mysqld crashes and restarts on connect attemptGleb Paharenko1 Nov