Manager of pid file quit without updating fi failed Live dirty chat

key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=500 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size (read_buffer_size sort_buffer_size)*max_threads = 2184911 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. You can use the following information to find out where mysqld died.If you see no messages after this, something went terribly wrong...I have a Centos VPS server and discovered my My SQL wouldn't start after it suddenly failed.

130319 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 130319 [Warning] '--skip-locking' is deprecated and will be removed in a future release. 130319 [Warning] '--log' is deprecated and will be removed in a future release. ^G/usr/sbin/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13) 130319 [ERROR] Can't open the mysql.plugin table. 130319 Inno DB: Initializing buffer pool, size = 8.0M 130319 Inno DB: Completed initialization of buffer pool 130319 Inno DB: Operating system error number 13 in a file operation.

If it is not fresh installation, do a rpm -Uvh instead) Remove all contents of /var/lib/mysql/ directory Re-install RPM check if /var/lib/mysql/mysql/is created after installing RPM Then give a service mysql start and watch logs.

130319 Inno DB: Operating system error number 13 in a file operation.

Inno DB: If the corrupt page is an index page Inno DB: you can also try to fix the corruption Inno DB: by dumping, dropping, and reimporting Inno DB: the corrupt table.

You can use CHECK Inno DB: TABLE to scan your table for corruption. Inno DB: Ending processing because of a corrupt database page.

Leave a Reply