000028130 - KB-1388 How to disable the automatic starting of ACM on system boot

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000028130
Applies ToAffected Versions: All Versions
Resolution

There are times when the automatic starting of ACM on system boot needs to be disabled or re-enabled. This kbase provides instructions on how to accomplish this task


 


Once the Aveksa Compliance Manager has been installed the Aveksa processes, the ACM Server, Agent and Oracle Instance (for a local install) are started automatically when the system is booted or rebooted. There are times when this automatic startup needs to be temporarily disabled. We use the Linux command, chkconfig to enable/disable these services.


 


The ACM services that are automatically started, when the appliance is booted to run levels 3, 4 and 5 are:


 


aveksa_server


aveksa_agent


aveksa_watchdog


dbora


 


To see the current status of these services, use the following command:


chkconfig --list (RedHat)


chkconfig (SuSE)


 


 


(note this will display all services, not just the ACM ones). You will see output similar to this. Note that the Aveksa Services started will depend on the version of ACM being run.. For example: the aveksa_agent process is no longer started for ACM 4.x+.


 


RedHat


 


aveksa_agent 0:off 1:off 2:off 3:on 4:on 5:on 6:off
aveksa_server 0:off 1:off 2:off 3:on 4:on 5:on 6:off
aveksa_watchdog 0:off 1:off 2:off 3:on 4:on 5:on 6:off
bluetooth 0:off 1:off 2:on 3:on 4:on 5:on 6:off
conman 0:off 1:off 2:off 3:off 4:off 5:off 6:off
cpuspeed 0:off 1:on 2:on 3:on 4:on 5:on 6:off
crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off
cups 0:off 1:off 2:on 3:on 4:on 5:on 6:off
dbora 0:off 1:off 2:off 3:on 4:on 5:on 6:off


 


SuSE


 


SuSEfirewall2_init on


SuSEfirewall2_setup on
autoyast off
aveksa_agent on
aveksa_server on
aveksa_watchdog on
 


 


To disable an ACM service from starting, enter the following command for each ACM service:


 


chkconfig --level 345 aveksa_agent off (RedHat)


chkconfig -s aveksa_agent off (SuSE)


 


Do this for each Aveksa Service you wish disabled from automatically starting at boot time.


 


 


To enable an ACM Service to start at the necessary boot levels, enter the following command for each ACM service you wish to affect:


 


chkconfig --level 345 aveksa_agent on (RedHat)


chkconfig -s aveksa_agent on (SuSE)


 


Do this for each Aveksa Service you wish enabled to automatically startup at boot time.


 


Refer to KB-1277 - What is the Aveksa Watchdog?, for more information on enabling/disabling the Aveksa Watchdog process.

Attachments

    Outcomes