AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.

    Skip to end of metadata
    Go to start of metadata

    If traffic doesn't appear in the Controller after you have installed the AppDynamics PHP Agent and started the instrumented server, try the following troubleshooting steps.

    Ensure that the Agent is Installed in the Correct Directory

    It is possible that the agent was installed in the wrong directory. Verify the location of your PHP installation.

    Then check where the installer actually installed the agent files.

    • The appdynamics_agent.ini file should be in the same directory that contains the php.ini file for your PHP installation.
    • The file should be in the extensions directory for your PHP installation.

    If the agent files are not in the correct directories, re-install the agent with the -i and -e options.

    Re-install the agent

    If the app agent is not installed in the right directory, re-install the agent using the installer with the -i and -e options. Use the -i to install the appdynamics_agent.ini file in the same directory as your php.ini file and the -e option to install the file in the same directory as your PHP extensions directory. See Install the PHP Agent by Shell Script.

    If you initially installed the agent using the RPM installer, you can find the shell script installer at /usr/lib/appdynamics-php5/

    Check error messages in the installation output

    When you reinstall, examine carefully any error messages in the output of the install script, especially those that direct you to copy some settings into your php.ini file.

    If necessary copy those settings into the php.ini file. See PHP Agent Configuration Settings for information on common settings that may be missing.

    Check the AppDynamics Settings Block in the Configuration

    Run this command:

    php -i | less

    and examine the output. You should see an appdynamics_agent.ini file and a configuration block listing appdynamics ini values.

    Confirm User Permissions

    Check that the following permissions are set:

    chown -R <apacheuser>:<apacheuser> <php_agent_install>
    chmod -R 755 <path_to_php_agent_install_logs>
    chmod 777 <php_agent_install>/logs

    Verify that the Proxy is Running

    The Java proxy is the part of the agent that communicates with the Controller. If the agent is installed in the right place, confirm that the Java proxy is running.

    1. From the command line enter,  ps aux | grep java.
    2. Inspect the list. You should see output similar to the following if the proxy is running:
    /usr/lib/appdynamics-php5/proxy/jre/bin/java -server -Xmx120m -classpath /usr/lib/appdynamics-php5/proxy/conf/logging/*:/usr/lib/appdynamics-php5/proxy/lib/*:/usr/lib/appdynamics-php5/proxy/lib/tp/*:/usr/lib/appdynamics-php5/proxy/* -Djava.library.path=/usr/lib/appdynamics-php5/proxy/lib/tp -Dappdynamics.agent.logs.dir=/usr/lib/appdynamics-php5/logs -Dcomm=/tmp/ad-siJ4rp -DagentType=PHP_APP_AGENT -Dappdynamics.agent.runtime.dir=/usr/lib/appdynamics-php5/proxy

    If you are instrumenting a PHP CLI script, you need to start the proxy manually. You may also need to start the proxy manually if you have special requirements for running Java processes. See Start the PHP Agent Proxy Manually

    Check the Configuration Properties

    It is possible that the properties that the proxy uses to communicate with the Controller were not set properly.

    You can modify these properties in the php.ini or appdynamics_agent.ini file, wherever they are set in your environment. See PHP Agent Configuration Settings.