This is most likely due to improper permissions on the real /tmp directory.
If you use the /scripts/securetmp script at boot time, you may not notice the problem because the script sets permissions correctly after it boots.
The most common error that you will see related to this is that the mysqld daemon will not start with errors that resemble the following example:
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
To fix this, unmount the /var/tmp and /tmp partitions and set the permissions correctly on the real /tmp directory. To do this, perform the following steps:
Run the following commands:
umount /var/tmp umount /tmp chmod 1777 /tmp
Edit the /etc/rc.sysinit file and add the following line near the other references to the /tmp directory:
chmod 1777 /tmp
Then you can reenable the /scripts/securetmp script.
If you have trouble with other services, confirm that they are enabled with the chkconfig –add pure-ftpd command.
If you still receive messages after each reboot from the chkservd daemon about services that are not down, perform the following steps:
Disable the service with the chkconfig command.
Add the service to the end of /etc/rc.local instead, to ensure that other services have time to start up first.
Posted in: Cpanel