Starting mysql manager of pid file quit without updating fi
160308 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql160308 [Warning] Using unique option prefix log-slave-update instead of log_slave_updates is deprecated and will be removed in a future release.Please use the full name instead.160308 [Note] Plugin 'FEDERATED' is disabled.160308 [Note] Plugin 'partition' is disabled.160308 Inno DB: The Inno DB memory heap is disabled160308 Inno DB: Mutexes and rw_locks use GCC atomic builtins160308 Inno DB: Compressed tables use zlib 1.2.3160308 Inno DB: Using Linux native AIO160308 Inno DB: Initializing buffer pool, size = 64.0M160308 Inno DB: Completed initialization of buffer pool160308 Inno DB: highest supported file format is Barracuda.이미 그런 일을 벌였다면 문제를 일으키고 있는 로그 파일의 소유자를 mysql 을 구동하는 계정으로 만들어 줘야 한다.만약 mysql 의 데이터 디렉토리가 /usr/local/mysql/data 라면 다음과 같이 해보자.Inno DB: Restoring possible half-written data pages from the doublewrite Inno DB: buffer...Inno DB: Last My SQL binlog file position 0 195017, file name /var/lib/mysql/ssgbin-log.000065160308 Inno DB: Waiting for the background threads to start160308 Inno DB: 5.5.42 started; log sequence number 93104858507160308 [Note] Recovering after a crash using /var/lib/mysql/ssgbin-log160308 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 249, event_type: 2160308 [Note] Starting crash recovery...160308 [Note] Crash recovery finished. UTC - mysqld got signal 11 ; This could be because you hit a bug.We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.----------------------------------------- Confidentiality Notice: The following mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If I remove all innodb value My SQL start and working fine.
If you have received this communication in error, please notify us immediately by reply e-mail and destroy all copies of the original message.
Description: severals day ago, Cent OS is power off unexpectedly.
Inno DB: If that is the case, please refer to Inno DB: [ERROR] Plugin ‘Inno DB’ init function returned error.
110621 [ERROR] Plugin ‘Inno DB’ registration as a STORAGE ENGINE failed.