Some services (like MySQL) aren’t starting on reboots. You get errors create/write to file in /tmp (Errcode: 13).

This is most likely due to improper permissions on the real /tmp directory. If using /scripts/securetmp at boot time, you may not notice the problem since the script sets permissions correctly after it’s booted. The most common error you will see related to this is that mysqld will not start with errors like the following:

061113 00:14:46 mysqld started

/usr/sbin/mysqld: Can't create/write to file '/tmp/ibEkcOgQ' (Errcode: 13)

061113 0:14:47 InnoDB: Error: unable to create temporary file; errno: 13

061113 0:14:47 [ERROR] Can't init databases

061113 0:14:47 [ERROR] Aborting

061113 0:14:47 [Note] /usr/sbin/mysqld: Shutdown complete

061113 00:14:47 mysqld ended


How to fix this issue?

To fix this, unmount the /var/tmp and /tmp partitions and set the permissions correctly on the real /tmp directory ilke so:

# umount /var/tmp

# umount /tmp

# chmod 1777 /tmp

Edit /etc/rc.sysinit and add the following line somewhere near the rest of the /tmp stuff:

chmod 1777 /tmp

Then you can reenable /scripts/securetmp if you’d like.

If you are having trouble with other services, be sure they are enabled:

chkconfig –add pure-ftpd

If you are still getting messages after each reboot from chkservd about

services not being down, you may want to disable it with chkconfig and add it to the end of /etc/rc.local instead, to ensure that other services have time to start up first.


5.00 avg. rating (92% score) - 1 vote
Website Pin Facebook Twitter Myspace Friendfeed Technorati Digg Google StumbleUpon Premium Responsive