AppD Archive

How to configure agent with start-stop-daemon init script

Mike_Gordon
New Member

Hi,

We're trying to test run the agent on a gunicorn based app. We've walked though all the usual troubleshooting steps (outbound conn, watchdog and proxy start etc) and everything looks fine but no data comes back to the SaaS controller. Though there is this when starting the app "No handlers could be found for logger “appdynamics.agent"" my guess is that it has to do with how pyagent is called in the init script. I've not been able to place the agent startup call on the right side of the start-stop-daemon call. Has anyone gotten this particular config to work in the past?

/usr/local/bin/pyagent run -c /etc/appdynamics.cfg -- start-stop-daemon --start --pidfile /var/run/gunicorn/gunicorn.pid -c measureworks -d /home/measureworks/www/rijksoverheid --exec /home/measureworks/.virtualenvs/rijksoverheid/bin/gunicorn -- -b 127.0.0.1:8000 --timeout=300 wsgi:application -D -p /var/run/gunicorn/gunicorn.pid --access-logfile /var/log/gunicorn/accessGunicorn.log --error-logfile /var/log/gunicorn/errorGunicorn.log --log-level debug

0 Karma
Get Updates on the Splunk Community!

Dashboards: Hiding charts while search is being executed and other uses for tokens

There are a couple of features of SimpleXML / Classic dashboards that can be used to enhance the user ...

Splunk Observability Cloud's AI Assistant in Action Series: Explaining Metrics and ...

This is the fourth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how ...

Brains, Bytes, and Boston: Learn from the Best at .conf25

When you think of Boston, you might picture colonial charm, world-class universities, or even the crack of a ...