MySQL Error: Unknown table engine ' InnoDB '

Problem:

Zabbix server Restart, enter the Zabbix Web Discovery login does not go in and the Web report mysql error, after viewing the day of MySQL, found an error:

[Email protected] ~]# tail-f/var/log/mysqld.log

140820 16:24:43 [Note]/usr/libexec/mysqld:ready for connections.

Version: ' 5.1.73 ' socket: '/var/lib/mysql/mysql.sock ' port:3306 Source distribution

140917 15:03:03 Mysqld_safe starting mysqld daemon with databases From/var/lib/mysql

/usr/libexec/mysqld:can ' t create/write to file '/tmp/ibedfc8d ' (errcode:13)

140917 15:03:03 InnoDB:Error:unable to create temporary file; Errno:13

140917 15:03:03 [ERROR] Plugin ' InnoDB ' init function returned ERROR.

140917 15:03:03 [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE failed.

After reviewing Zabbix's log, I also found an error

[[email protected] Zabbix] #tail-F/tmp/zabbix_server.log

3545:20140917:154534.090 [Z3005] query failed: [1286] Unknown table engine ' InnoDB ' [select distinct R.druleid,r.iprange, R.name,c.dcheckid from Drules R left join Dchecks C in C.druleid=r.druleid and uniq=1 where R.proxy_hostid is null and R.S Tatus=0 and (r.nextcheck<=1410939934 or R.nextcheck>1410939934+r.delay) and mod (r.druleid,1) =0 and R.druleid Between 0 and 99999999999999]

3545:20140917:154534.090 [Z3005] query failed: [1286] Unknown table engine ' InnoDB ' [select COUNT (*), Min (Nextcheck) from D Rules where Proxy_hostid is null and status=0 and mod (druleid,1) =0 and Druleid between 0 and 99999999999999]

After Baidu query "Unknown table engine ' InnoDB '" solution, a bunch of articles that need to modify the MySQL internal settings adjustment, and thought that there will be no MySQL internal setup problems, because the machine has restarted the problem. After careful check MySQL error, see the key message "/usr/libexec/mysqld:can ' t create/write to file '/tmp/ibedfc8d '", at this time to view the permissions of/TMP, is indeed the wrong permissions, because the machine restarts,/ The permissions of TMP are reset.

Workaround: chmod 777/tmp

That's it, it's simple! Because MySQL will create temporary files and socket files in/tmp at startup, so the/TMP permissions will be incorrect.

This article is from the "Fate" blog, make sure to keep this source http://czybl.blog.51cto.com/4283444/1554389

MySQL Error: Unknown table engine ' InnoDB '