Mysql doesnt start correctly after reboot
Posted: Fri Nov 21, 2014 9:08 pm
Hi
Testing vestacp and noticed a problem that i replicate with rebooting the server.
It looks like there is to mysql servers trying to start, but i can't find the source of it
Some extra info:
[*]I can manually log into the mysqld from console but php to mysql doesnt work
[*] stopping and starting mysql solves the problem
Running ubuntu 14.04 (trusty)
The logs show this:
Testing vestacp and noticed a problem that i replicate with rebooting the server.
It looks like there is to mysql servers trying to start, but i can't find the source of it
Some extra info:
[*]I can manually log into the mysqld from console but php to mysql doesnt work
[*] stopping and starting mysql solves the problem
Running ubuntu 14.04 (trusty)
The logs show this:
Code: Select all
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.
141121 15:41:21 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
141121 15:41:21 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.5/en/operating-system-error-codes.html
141121 15:41:21 InnoDB: Could not open or create data files.
141121 15:41:21 InnoDB: If you tried to add new data files, and it failed here,
141121 15:41:21 InnoDB: you should now edit innodb_data_file_path in my.cnf back
141121 15:41:21 InnoDB: to what it was, and remove the new ibdata files InnoDB created
141121 15:41:21 InnoDB: in this failed attempt. InnoDB only wrote those files full of
141121 15:41:21 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
141121 15:41:21 InnoDB: remove old data files which contain your precious data!
141121 15:41:21 [ERROR] Plugin 'InnoDB' init function returned error.
141121 15:41:21 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
141121 15:41:21 [ERROR] Unknown/unsupported storage engine: InnoDB
141121 15:41:21 [ERROR] Aborting