I have just deployed a new CentOS 6.4 image on AWS, and I'm having issues with init.d scripts not starting up. I've verified the following; 1) They work on their own after boot 2) They're set to run at runlevel 3,4, and 5 via chkconfig 3) The system boots up in runlevel 3 (no GUI) 4) There are no lingering PID files around after boot 5) Permissions are correct on the files in init.d 6) /etc/init.d is linked to /etc/rc.d/init.d 7) Some functions start up correctly at start up (such as bind) 8) All file systems are mounted in runlevel 3 9) The IP address is static on the server One specific example is crond; Chkconfig output: crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off permissions in init.d: -rwxr-xr-x 1 root root 2793 Jul 18 2011 crond The processes that aren't loading are; Clamd, directadmin, exim, freshclam, httpd, mysqld, ossec, proftpd, sshguard Any ideas what I need to check/change to resolve this problem? Thanks everyone!