DA cannot start mysql

E

erinys

New member
Joined
Mar 7, 2008
Messages
3
Hi guys,

i have about 4 hours downtime last night because mysql was down.
for some reason DA wasnt able to start/restart it due to an error.

i had to login root, and when did /sbin/service mysqld start 2>&1 it gave me an error and couldnt restart.

so i googled a bit since my hosting wasnt responding.. and found that

[root@wbsvr1 /]# killall mysqld
[root@wbsvr1 /]# /sbin/service mysqld start 2>&1
Starting MySQL SUCCESS!

did the trick.

is there a way to prevent this from happening and also seeing what went wrong so i can prevent that aswel?
 
Thanks for the tips erinys. My server just occur the same problems as yours today. Now i can start mysql service as usual.

Did you manage to find how this problem occur?
 
What errors are displayed in the log? Hard to say how to prevent a problem if we don't know the details. :)
 
Thanks Dravu.This the error log occur before i manage to start the service back. What happens with this error log.

080511 00:41:47 mysqld started
080511 0:41:47 [Warning] Asked for 196608 thread stack, but got 126976
080511 0:41:47 InnoDB: Retrying to lock the first data file
080511 0:43:27 InnoDB: Unable to open the first data file
080511 0:43:27 InnoDB: Operating system error number 11 in a file operation.
080511 0:43:27 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
080511 0:43:27 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080511 0:43:27 [ERROR] Aborting
080511 0:43:27 [Note] /usr/sbin/mysqld: Shutdown complete
080511 00:43:27 mysqld ended
080511 00:53:01 mysqld started
080511 0:53:02 [Warning] Asked for 196608 thread stack, but got 126976
080511 0:53:02 InnoDB: Started; log sequence number 0 43655
080511 0:53:02 [Note] /usr/sbin/mysqld: ready for connections.
 
mikegrungey said:
Thanks Dravu.This the error log occur before i manage to start the service back. What happens with this error log.

080511 00:41:47 mysqld started
080511 0:41:47 [Warning] Asked for 196608 thread stack, but got 126976
080511 0:41:47 InnoDB: Retrying to lock the first data file
080511 0:43:27 InnoDB: Unable to open the first data file
080511 0:43:27 InnoDB: Operating system error number 11 in a file operation.
080511 0:43:27 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
080511 0:43:27 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080511 0:43:27 [ERROR] Aborting
080511 0:43:27 [Note] /usr/sbin/mysqld: Shutdown complete
080511 00:43:27 mysqld ended
080511 00:53:01 mysqld started
080511 0:53:02 [Warning] Asked for 196608 thread stack, but got 126976
080511 0:53:02 InnoDB: Started; log sequence number 0 43655
080511 0:53:02 [Note] /usr/sbin/mysqld: ready for connections.
Click to expand...
Sounds like jlasman was right. Some processes were still running. Next time, do service mysqld restart as you'll have to stop it to start it again.

Are there any other entries related to why it wasn't working in the first place? The part that you gave just showed that it was still running when you tried to start it again.
 
Here is on 090508. I only took apart of it before it went down for the whole day and i only noticed it 24hrs later.

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.
080509 2:06:58 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
080509 2:06:58 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!
080509 2:06:58 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
080509 2:06:58 [ERROR] Do you already have another mysqld server running on port: 3306 ?
080509 2:06:58 [ERROR] Aborting

080509 2:06:58 [Note] /usr/sbin/mysqld: Shutdown complete

080509 02:06:58 mysqld ended
 
[root@server /]# /sbin/service mysqld start
Starting MySQL. ERROR! Manager of pid-file quit without updating file.
 
You must log in or register to reply here.
Back
Top