-
Notifications
You must be signed in to change notification settings - Fork 812
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the supervisord binary preferred by the user. #580
Comments
Good catch, thanks for pointing this out! |
Thank your for fixing it @elijahandrews . This will semplify a lot our setup. |
I have the same experience about this, I need to install the agent without interupting the supervisord that running. |
@rosada the Agent now uses (since at least v5.0.0) its own supervisord (see https://github.com/DataDog/dd-agent/blob/5.27.2/packaging/debian/datadog-agent.init#L29), so the agent install should not have any effect on your system-wide supervisord |
@olivielpeau thank you for the info. |
the agent's supervisord uses a unix socket file and not a port: https://github.com/DataDog/dd-agent/blob/5.27.2/packaging/supervisor.conf#L1-L5 (that file should be present at what's the port that's conflicting? |
@olivielpeau I am running nginx listening on 80 also, but the conflict says it was because supervisord failed to start
Any idea? |
@rosada this doesn't seem to be related to the Datadog Agent (the Agent does not install the |
If another version of supervisord is already present on the system installed via pip, it will be installed in /usr/local/bin/supervisord and the installation script of datadog will fail because supervisord cannot be installed by apt-get.
Please avoid the usage of /usr/bin/supervisord but use the supervisord in the path if the user has already installed it.
I cannot try the fix at line:
dd-agent/packaging/datadog-agent-base-deb/datadog-agent.init
Line 27 in 1fa0c19
but should just be
SUPERVISORD="$(which supervisord)"
The text was updated successfully, but these errors were encountered: