Use the supervisord binary preferred by the user.

[mastrolinux]

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

SUPERVISORD="/usr/bin/supervisord"

but should just be
SUPERVISORD="$(which supervisord)"

[elijahandrews]

Good catch, thanks for pointing this out!

[mastrolinux]

Thank your for fixing it @elijahandrews . This will semplify a lot our setup.

[rosada]

I have the same experience about this, I need to install the agent without interupting the supervisord that running.
Is that possible?

[olivielpeau]

@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

[rosada]

@olivielpeau thank you for the info.
when installing the agent, it is also installing supervisord. and we are using the default port for supervisord.
The installation is failed because port conflict, I cannot stoping or change the port on curently runnning supervisord.
can I modified the supervisord before it is installed by the agent?

[olivielpeau]

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 /etc/dd-agent/supervisor.conf on an installation of Agent v5). So AFAIK you shouldn't get any port conflict because of the Agent's supervisord

what's the port that's conflicting?

[rosada]

@olivielpeau I am running nginx listening on 80 also, but the conflict says it was because supervisord failed to start

Setting up supervisor (3.0b2-1ubuntu0.1) ... Starting supervisor: Error: Another program is already listening on a port that one of our HTTP servers is configured to use. Shut this program down first before starting supervisord. For help, use /usr/bin/supervisord -h invoke-rc.d: initscript supervisor, action "start" failed.

Any idea?

[olivielpeau]

@rosada this doesn't seem to be related to the Datadog Agent (the Agent does not install the supervisor deb package), I'd advise you to check which port your system supervisor attempts to listen to by default, and compare that to the list of open connections (helpful command: netstat -atunp, run with sudo).