The agent will not work if the proxy did not start.

Determine whether the proxy started by running this command:

ps aux|grep java

If the proxy is running, you should see java and proxy in the output, something like this:

/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 com.appdynamics.ee.agent.proxy.kernel.Prox

If the proxy did not start, the most common reason is insufficient permissions.

• The agent installation directory, and its proxy control subdirectory, must be readable and executable by all and writable by the directory owner:

  chmod -R 755 <agent_install_dir>

• The agent installation directory must be owned by the instrumented application user. Who this user is depends on the platform. It could be the Apache user, the python container user, the nginx user, etc.

  chown -R <appuser>:<appsuser> <agent_install_dir>

If the proxy did not start, set these permissions and try again.