LINUX.ORG.RU
ФорумAdmin

The server quit without updating PID file

 


0

1

При перезапуске mysql выдает следующее сообщение The server quit without updating PID file (/var/lib/mysql/localhost.server...

Перерыл практически все в поисках решения. Может кто сталкивался ? Буду очень признателен за помощь ..

Ответ на: комментарий от anonymous

150423 02:24:44 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150423 2:24:44 [Note] /usr/sbin/mysqld (mysqld 5.5.43) starting as process 3115 ... 150423 2:24:44 [Note] Plugin 'FEDERATED' is disabled. 150423 2:24:44 InnoDB: The InnoDB memory heap is disabled 150423 2:24:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150423 2:24:44 InnoDB: Compressed tables use zlib 1.2.3 150423 2:24:44 InnoDB: Using Linux native AIO 150423 2:24:44 InnoDB: Initializing buffer pool, size = 128.0M 150423 2:24:44 InnoDB: Completed initialization of buffer pool InnoDB: Error: space header page consists of zero bytes in data file ./ibdata1 150423 2:24:44 InnoDB: Could not open or create data files. 150423 2:24:44 InnoDB: If you tried to add new data files, and it failed here, 150423 2:24:44 InnoDB: you should now edit innodb_data_file_path in my.cnf back 150423 2:24:44 InnoDB: to what it was, and remove the new ibdata files InnoDB created 150423 2:24:44 InnoDB: in this failed attempt. InnoDB only wrote those files full of 150423 2:24:44 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 150423 2:24:44 InnoDB: remove old data files which contain your precious data! 150423 2:24:44 [ERROR] Plugin 'InnoDB' init function returned error. 150423 2:24:44 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 150423 2:24:44 [ERROR] Unknown/unsupported storage engine: InnoDB 150423 2:24:44 [ERROR] Aborting

150423 2:24:44 [Note] /usr/sbin/mysqld: Shutdown complete

150423 02:24:44 mysqld_safe mysqld from pid file /var/lib/mysql/localhost.gigabox.tw.pid ended 150423 02:25:01 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150423 2:25:01 [Note] /usr/sbin/mysqld (mysqld 5.5.43) starting as process 3279 ... 150423 2:25:01 [Note] Plugin 'FEDERATED' is disabled. 150423 2:25:01 InnoDB: The InnoDB memory heap is disabled 150423 2:25:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150423 2:25:01 InnoDB: Compressed tables use zlib 1.2.3 150423 2:25:01 InnoDB: Using Linux native AIO 150423 2:25:01 InnoDB: Initializing buffer pool, size = 128.0M 150423 2:25:01 InnoDB: Completed initialization of buffer pool InnoDB: Error: space header page consists of zero bytes in data file ./ibdata1 150423 2:25:01 InnoDB: Could not open or create data files. 150423 2:25:01 InnoDB: If you tried to add new data files, and it failed here, 150423 2:25:01 InnoDB: you should now edit innodb_data_file_path in my.cnf back 150423 2:25:01 InnoDB: to what it was, and remove the new ibdata files InnoDB created 150423 2:25:01 InnoDB: in this failed attempt. InnoDB only wrote those files full of 150423 2:25:01 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 150423 2:25:01 InnoDB: remove old data files which contain your precious data! 150423 2:25:01 [ERROR] Plugin 'InnoDB' init function returned error. 150423 2:25:01 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 150423 2:25:01 [ERROR] Unknown/unsupported storage engine: InnoDB 150423 2:25:01 [ERROR] Aborting

150423 2:25:01 [Note] /usr/sbin/mysqld: Shutdown complete

150423 02:25:01 mysqld_safe mysqld from pid file /var/lib/mysql/localhost.gigabox.tw.pid ended 150423 02:25:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150423 2:25:07 [Note] /usr/sbin/mysqld (mysqld 5.5.43) starting as process 3425 ... 150423 2:25:07 [Note] Plugin 'FEDERATED' is disabled. 150423 2:25:07 InnoDB: The InnoDB memory heap is disabled 150423 2:25:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150423 2:25:07 InnoDB: Compressed tables use zlib 1.2.3

kotfedja
() автор топика
Ответ на: комментарий от kotfedja

150423 2:25:01 [Note] /usr/sbin/mysqld: Shutdown complete

150423 02:25:01 mysqld_safe mysqld from pid file /var/lib/mysql/localhost.gigabox.tw.pid ended 150423 02:25:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150423 2:25:07 [Note] /usr/sbin/mysqld (mysqld 5.5.43) starting as process 3425 ... 150423 2:25:07 [Note] Plugin 'FEDERATED' is disabled. 150423 2:25:07 InnoDB: The InnoDB memory heap is disabled 150423 2:25:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150423 2:25:07 InnoDB: Compressed tables use zlib 1.2.3 150423 2:25:07 InnoDB: Using Linux native AIO 150423 2:25:07 InnoDB: Initializing buffer pool, size = 128.0M 150423 2:25:07 InnoDB: Completed initialization of buffer pool InnoDB: Error: space header page consists of zero bytes in data file ./ibdata1 150423 2:25:07 InnoDB: Could not open or create data files. 150423 2:25:07 InnoDB: If you tried to add new data files, and it failed here, 150423 2:25:07 InnoDB: you should now edit innodb_data_file_path in my.cnf back 150423 2:25:07 InnoDB: to what it was, and remove the new ibdata files InnoDB created 150423 2:25:07 InnoDB: in this failed attempt. InnoDB only wrote those files full of 150423 2:25:07 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 150423 2:25:07 InnoDB: remove old data files which contain your precious data! 150423 2:25:07 [ERROR] Plugin 'InnoDB' init function returned error. 150423 2:25:07 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 150423 2:25:07 [ERROR] Unknown/unsupported storage engine: InnoDB 150423 2:25:07 [ERROR] Aborting

150423 2:25:07 [Note] /usr/sbin/mysqld: Shutdown complete

150423 02:25:07 mysqld_safe mysqld from pid file /var/lib/mysql/localhost.gigabox.tw.pid ended

kotfedja
() автор топика
Ответ на: комментарий от kotfedja

проверяйте права на доступ пользователю mysql к базам и к записи удалению лок файла, и пересмотрите еще остальные логи

anonymous
()

InnoDB: Error: space header page consists of zero bytes in data file ./ibdata1

У вас повредился файл ibdata1.

Перерыл практически все в поисках решения.

Гуглили не саму ошибку, а сообщение, что сервер не запустился

goingUp ★★★★★
()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.