#1  
Old 6th July 2011, 13:37
terryoleary1981 terryoleary1981 is offline
Member
 
Join Date: Jan 2008
Posts: 91
Thanks: 3
Thanked 2 Times in 2 Posts
Default mysql service won't start

Hi

Had to reboot my server as the mysql service just randomly stopped working. I was then greeted with a disk failure is imminent message which i've managed to recover from but the mysql service still doesnt come up.

So far I've tried a yum update mysqld and that updated some of the modules but the service still doesnt come up. When I enter service mysqld start I just get a failed message and no more information.

I need to access the mysql databases to back everything up before the HDD dies. Any ideas on what the problem is? Would a yum remove mysqld and then reinstall work or would I loose all my databases?
Reply With Quote
Sponsored Links
  #2  
Old 6th July 2011, 14:00
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,983
Thanks: 825
Thanked 5,372 Times in 4,219 Posts
Default

First you should do a harddisk backup of your mysql databases by creating a tar.gz file of the mysql database folder. In case of a harddisk failure you should be able to use that to recover the databases:

tar pcfz mysql_databases.tar.gz /var/lib/mysql

Then you should check if there are any error messages in the syslog or messages log in /var/log/ when you restart mysql

You should also check with "df -h" if none of the harddisk partitions are full.

When mysql is working again, then you should do a normal mysql backup with e.g mysqldump.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #3  
Old 6th July 2011, 14:14
terryoleary1981 terryoleary1981 is offline
Member
 
Join Date: Jan 2008
Posts: 91
Thanks: 3
Thanked 2 Times in 2 Posts
 
Default

thanks for the pointer till

I've done the back up as suggested

I'm only using 17% of the disk so I have plenty of space

The error log contains this:

Code:
110706 10:47:30  mysqld started
InnoDB: Error: tried to read 65536 bytes at offset 0 4124160.
InnoDB: Was only able to read 512.
InnoDB: Fatal error: cannot read from file. OS error number 17.
110706 10:47:48InnoDB: Assertion failure in thread 3087247152 in file os0file.c line 2211
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
110706 10:47:48 - 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=0
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 = 217599 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=0xbff53f88, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x818b124
0x842e63e
0x83ff548
0x83dd267
0x83e7030
0x83e75d2
0x83482c7
0x8254e76
0x8244b1f
0x818c10d
0x818e3ed
0x8275d6
0x80fc111
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
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.
110706 10:47:48  mysqld ended

110706 10:54:36  mysqld started
110706 10:54:36 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
110706 10:54:36 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
InnoDB: Error: tried to read 65536 bytes at offset 0 4124160.
InnoDB: Was only able to read 512.
InnoDB: Fatal error: cannot read from file. OS error number 17.
110706 10:54:55InnoDB: Assertion failure in thread 3086681904 in file os0file.c line 2211
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
110706 10:54:55 - 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=0
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 = 217599 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=0xbfdc95f8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x818f189
0x843940e
0x840a218
0x83e7f07
0x83f1d00
0x83f22a2
0x8352db7
0x825e6f2
0x824e4af
0x819018d
0x819248d
0x8275d6
0x80fd501
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
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110706 10:54:55  mysqld ended

110706 11:04:50  mysqld started
110706 11:04:50 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
110706 11:04:50 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
InnoDB: Error: tried to read 65536 bytes at offset 0 4124160.
InnoDB: Was only able to read 512.
InnoDB: Fatal error: cannot read from file. OS error number 17.
110706 11:05:08InnoDB: Assertion failure in thread 3087075120 in file os0file.c line 2211
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
110706 11:05:08 - 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=0
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 = 217599 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=0xbfe29e58, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x818f189
0x843940e
0x840a218
0x83e7f07
0x83f1d00
0x83f22a2
0x8352db7
0x825e6f2
0x824e4af
0x819018d
0x819248d
0x8275d6
0x80fd501
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
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
110706 11:05:08  mysqld ended
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Another MySQL start problem Numerizen Server Operation 2 18th June 2012 09:41
MySQL Error Nolan Installation/Configuration 12 16th February 2011 02:15
DRBD/HA/OpenFiler issue with 'service openfiler start' CodeChris HOWTO-Related Questions 3 31st May 2010 16:36
Monit & Munin SamTzu HOWTO-Related Questions 1 4th May 2008 18:03
"Too many open files in system" problems Berry Installation/Configuration 3 10th November 2007 21:58


All times are GMT +2. The time now is 02:10.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.