This article is intended for anyone installing the Apache Agent. Please make sure the following 11 prerequisites are in place before installing the agent:
sestatusat the host command prompt. If SELinux is active and in enforcing mode, you will need to disable it before continuing. Use the command
sudo setenforce 0to temporarily disable SELinux. NOTE: If your system uses SELInux, you will need to create an appropriate policy file in order to allow the Agent and Proxy task to access the necessary log and configuration files.
ps -ef | grep httpd(use apache2 if httpd is not the name of the server binary). You will see a "root" process id and several "worker" child processes listed in the output. The userid associated with the children of the parent process is the Apache worker process id. This can be set explicitly with the Apache User directive. See here for more details: https://httpd.apache.org/docs/2.4/mod/mod_unixd.html#user
/etc/security/limits.confEdit file to verify that this is the case. There should be both a hard and soft setting for the nofiles entries for the appropriate userid(s).
ps -ef | grep proxy | grep WEB_SERVER | grep -v grepto make sure that there is only one Proxy active. Our best practices suggest you run the Proxy as the same userid as the Apache server worker process. At a minimum, the Proxy task should be started at host boot up and remain active through out the life of the host. There should be no need to restart the Proxy task unless the appdynamics_agent.conf file changes. It is possible to stop/start the webserver without affecting it. Please see here for more details about launching the Proxy: https://docs.appdynamics.com/display/PRO45/Install+the+Apache+Agent#InstalltheApacheAgent-LaunchtheP...