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!
On Thu, Jun 20, 2013 at 06:41:09AM -0700, Don O'Neil wrote:
I have just deployed a new CentOS 6.4 image on AWS, and I'm having issues with init.d scripts not starting up.
Which AMI? CentOS genuine one? or yours or 3rd party? http://wiki.centos.org/Cloud/AWS
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
-> rpm --verify -qf /etc/init.d/crond
The processes that aren't loading are;
Clamd, directadmin, exim, freshclam, httpd, mysqld, ossec, proftpd, sshguard
some looks like CentOS ones httpd/mysqld, not the others.
Tru
It wasn't an official AMI, I didn't even know there was one. I was using one that was published by another ISP that was built on 6.4. With the exception of the startup issue, it has worked flawlessly. If I can't get this resolved I guess I can re-build on an official AMI.
I looked in my boot log before (forgot to mention that) and the other startup scripts don't even have entries.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Tru Huynh Sent: Thursday, June 20, 2013 8:10 AM To: CentOS mailing list Subject: Re: [CentOS] init.d scripts not starting at boot
On Thu, Jun 20, 2013 at 06:41:09AM -0700, Don O'Neil wrote:
I have just deployed a new CentOS 6.4 image on AWS, and I'm having issues with init.d scripts not starting up.
Which AMI? CentOS genuine one? or yours or 3rd party? http://wiki.centos.org/Cloud/AWS
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
-> rpm --verify -qf /etc/init.d/crond
The processes that aren't loading are;
Clamd, directadmin, exim, freshclam, httpd, mysqld, ossec, proftpd, sshguard
some looks like CentOS ones httpd/mysqld, not the others.
Tru
-- Tru Huynh (mirrors, CentOS i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B
I think it's either one of two: 1) corrupted machine software 2) A copied machine with specific intention to block specific stuff.
You can rethink your approach like this.
Eliezer
On 06/20/2013 06:42 PM, Don O'Neil wrote:
It wasn't an official AMI, I didn't even know there was one. I was using one that was published by another ISP that was built on 6.4. With the exception of the startup issue, it has worked flawlessly. If I can't get this resolved I guess I can re-build on an official AMI.
I looked in my boot log before (forgot to mention that) and the other startup scripts don't even have entries.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Tru Huynh Sent: Thursday, June 20, 2013 8:10 AM To: CentOS mailing list Subject: Re: [CentOS] init.d scripts not starting at boot
On Thu, Jun 20, 2013 at 06:41:09AM -0700, Don O'Neil wrote:
I have just deployed a new CentOS 6.4 image on AWS, and I'm having issues with init.d scripts not starting up.
Which AMI? CentOS genuine one? or yours or 3rd party? http://wiki.centos.org/Cloud/AWS
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
-> rpm --verify -qf /etc/init.d/crond
The processes that aren't loading are;
Clamd, directadmin, exim, freshclam, httpd, mysqld, ossec, proftpd, sshguard
some looks like CentOS ones httpd/mysqld, not the others.
Tru
-- Tru Huynh (mirrors, CentOS i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Don O'Neil -
Eliezer Croitoru -
Tru Huynh