MySQL Not Working

Is there anything that is confusing you, or that you are unable to understand? You can clarify here.
Post Reply

MySQL Not Working

Post by gabeosx » Fri Feb 09, 2007 5:25 pm

I'm trying to install MySQL server on my Fedora Core 5 virtual server. When I install it from the RPMs, it crashes.

[root@gabealbert gabe]# yum groupinstall "MySQL Database"

Everything installs fine, no errors.

Then I try to run MySQL....

[root@gabealbert gabe]# /etc/rc.d/init.d/mysqld restart
Stopping MySQL: [FAILED]
Timeout error occurred trying to start MySQL Daemon.
Starting MySQL: [FAILED]

I check /var/log/mysqld.log and I get the following:

070209 11:21:21 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 000000000000000000000000000000000000000000000000000000000000000$
070209 11:21:21 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksu$
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
070209 11:21:21InnoDB: Error: trying to access a stray pointer 0x8000002a971b3f$
InnoDB: buf pool start is at 0x2a971a4000, end at 0x2a979a4000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: how to force recovery.
070209 11:21:21InnoDB: Assertion failure in thread 182920090800 in file ./../in$
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
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 **** up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
The manual page at contains
information that should help you find out what is causing the crash.
070209 11:21:21 mysqld ended

My guess is that this has something to do with running MySQL in a VM. Any ideas?


Post by gabeosx » Fri Feb 09, 2007 5:45 pm

By disabling innodb, I was able to get MySQL to start.

Posts: 720
Joined: Mon Jan 29, 2007 1:39 pm

Post by iBye » Fri Feb 09, 2007 6:00 pm

Oh, that's good. :)
Tired of Newbies asking Questions? Tell them [color="Red"][/color]

Posts: 2049
Joined: Sat Dec 18, 2004 11:28 am

Post by SHAdmin » Fri Feb 09, 2007 6:44 pm

gabeosx wrote:By disabling innodb, I was able to get MySQL to start.

You can contact the support team, and can get the pre-configured MySQL application template installed on your VPS.

Post Reply