请教军哥，lnmp1.4 阿里云镜像恢复 mysql 启动错误

ijinson

请教军哥，我原有一个阿里云服务器，使用的是LNMP1.4，然后创建了镜像。

然后我新购了一台服务器恢复镜像，恢复后。 发现启动 lnmp 提示错误   该怎么弄？

licess

按反馈必读要求提供mysql的错误日志，只有通过日志才能确定原因

ijinson

军哥？  这是在/usr/local/mysql/var的mysql  /usr/local/mysql/var/主机名.err ， 复制了最后面的几十行日志
-----------------------------
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock /usr/local/mysql/var/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 /usr/local/mysql/var/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 /usr/local/mysql/var/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 /usr/local/mysql/var/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 /usr/local/mysql/var/ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
180803 16:14:36  InnoDB: Unable to open the first data file
InnoDB: Error in opening /usr/local/mysql/var/ibdata1
180803 16:14:36  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
180803 16:14:36 InnoDB: Could not open or create data files.
180803 16:14:36 InnoDB: If you tried to add new data files, and it failed here,
180803 16:14:36 InnoDB: you should now edit innodb_data_file_path in my.cnf back
180803 16:14:36 InnoDB: to what it was, and remove the new ibdata files InnoDB created
180803 16:14:36 InnoDB: in this failed attempt. InnoDB only wrote those files full of
180803 16:14:36 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
180803 16:14:36 InnoDB: remove old data files which contain your precious data!
180803 16:14:36 [ERROR] Plugin 'InnoDB' init function returned error.
180803 16:14:36 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
180803 16:14:36 [ERROR] Unknown/unsupported storage engine: InnoDB
180803 16:14:36 [ERROR] Aborting

180803 16:14:36 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

180803 16:26:50 [Note] Plugin 'FEDERATED' is disabled.
180803 16:26:50 InnoDB: The InnoDB memory heap is disabled
180803 16:26:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180803 16:26:50 InnoDB: Compressed tables use zlib 1.2.7
180803 16:26:50 InnoDB: Initializing buffer pool, size = 256.0M
180803 16:26:50 InnoDB: Completed initialization of buffer pool
180803 16:26:50 InnoDB: highest supported file format is Barracuda.
180803 16:26:50  InnoDB: Waiting for the background threads to start
180803 16:26:51 InnoDB: 5.5.56 started; log sequence number 1616417
180803 16:26:51 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180803 16:26:51 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180803 16:26:51 [Note] Server socket created on IP: '0.0.0.0'.
180803 16:26:51 [Warning] 'user' entry 'fsgt@localhost' has both a password and an authentication plugin specified. The password will be ignored.
180803 16:26:51 [Warning] 'user' entry 'fswc@localhost' has both a password and an authentication plugin specified. The password will be ignored.
180803 16:26:51 [Warning] 'user' entry 'sydd@localhost' has both a password and an authentication plugin specified. The password will be ignored.
180803 16:26:51 [Note] Event Scheduler: Loaded 0 events
180803 16:26:51 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.56-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
180803 16:30:58 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown

180803 16:30:58 [Note] Event Scheduler: Purging the queue. 0 events
180803 16:30:58  InnoDB: Starting shutdown...
180803 16:30:59  InnoDB: Shutdown completed; log sequence number 1616417
180803 16:30:59 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

180803 16:31:01 [Note] Plugin 'FEDERATED' is disabled.
180803 16:31:01 InnoDB: The InnoDB memory heap is disabled
180803 16:31:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180803 16:31:01 InnoDB: Compressed tables use zlib 1.2.7
180803 16:31:01 InnoDB: Initializing buffer pool, size = 256.0M
180803 16:31:01 InnoDB: Completed initialization of buffer pool
180803 16:31:01 InnoDB: highest supported file format is Barracuda.
180803 16:31:01  InnoDB: Waiting for the background threads to start
180803 16:31:02 InnoDB: 5.5.56 started; log sequence number 1616417
180803 16:31:02 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180803 16:31:02 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
180803 16:31:02 [Note] Server socket created on IP: '0.0.0.0'.
180803 16:31:02 [Warning] 'user' entry 'fsgt@localhost' has both a password and an authentication plugin specified. The password will be ignored.
180803 16:31:02 [Warning] 'user' entry 'fswc@localhost' has both a password and an authentication plugin specified. The password will be ignored.
180803 16:31:02 [Warning] 'user' entry 'sydd@localhost' has both a password and an authentication plugin specified. The password will be ignored.
180803 16:31:02 [Note] Event Scheduler: Loaded 0 events
180803 16:31:02 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.56-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

ijinson

完整err错误日志

licess

mysql已经在运行，只是pid文件没有或者被删除
killall mysqld的进程再启动试试