Mysql is always crashed when I wake up the morning

N

networe

New member
Joined
Jul 8, 2012
Messages
15
Hi,

My Mysql is always crashed when I wake up the morning. I don't know why.

I am trying to find good error logs but I completely dont find good mysql error logs

Where are they ? Is there a way to setup all of them in my.cnf ?

If it's possible to hire an Directadmin expert for around 40-50$ to check configs - mysql if they are all correct and resolve mysql bugs.

Thanks

Skype : Networe
 
This is my error log for my hostname
Note : There is a bunchhhhhh of InnoDB....Unable to lock...Check...

Mysql Started when I restarted the server at 13:20 (The morning for me)

InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
120711 5:01:47 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
120711 5:01:47 InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
120711 5:01:47 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
120711 5:01:47 [ERROR] Do you already have another mysqld server running on port: 3306 ?
120711 5:01:47 [ERROR] Aborting

120711 5:01:47 [Note] /usr/sbin/mysqld: Shutdown complete

120711 05:01:47 mysqld ended

120711 13:20:06 mysqld started
Click to expand...
 
Hello,

My guess would be that MySQL somehow fails to restart. You probably have running a zombie process of mysqld, so try and post here results of

Code: 
ps aux | grep -v grep | grep -i mysql


If you want I could check your setup, send me a PM if you interested.
 
not sure if this helps but I had similar errors when I was running sphinx search and had an error on my sphinx conf file. the system was locking up running a delta check.
 
You must log in or register to reply here.
Back
Top