Follow Docker-Instructions.md gets dial tcp 127.0.0.1: 25225: connection refused about oms-agent-for-linux HOT 6 CLOSED

@agup006 Can you take a look at this, provide guidance, and correct docs if needed?

from oms-agent-for-linux.

@agup006 Did you take a look at this? Can this issue be closed?

from oms-agent-for-linux.

@jeffaco
I think the instructions are correct since as prerequisite of using OMS with Docker is:

Your container hosts must be running:

Docker 1.8 or later

My original intention was to set up a Linux VM using an ARM Template with the following:

• Docker Extension
• OMS Monitoring the Docker Containers

The problem with this approach is that OMS won't enable Docker monitoring if Docker is not installed. You could first use the docker extension and then the OMS extension but this would fail by "log-driver=fluentd" docker start-up parameter - since the service is started by the OMS Extension.

I think a possible solution could be to flag the OMS extension to enable Docker Monitoring even if is not currently installed. A Workaround would be to have a custom script to restart the docker server as the last step on the ARM Template.

Thanks for your help!

from oms-agent-for-linux.

@jmacias I'm somewhat confused by your message.

Unfortunately, I don't know a lot about the Docker extension, but I know enough where we can hopefully help each other.

Normally, we only listen for log messages via UDP 25225. We do this because it's "lower weight", and generally sufficient for us to capture all logging information. But we later learned that, under very high message loads (like ~1000 messages/second), messages can be lost (even on the same system) with UDP, and you really needed TCP. So we did some optimization work to make OMS more efficient with batching, and we documented how to enable TCP/IP if you needed it.

So, with that explained, are you saying that Docker will only work with TCP/IP enabled (it won't work otherwise)? If so, that's definitely a documentation problem, and Anurag will need to fix that. Or are you saying something else?

Next, I don't fully understand your issue. The Docker agent does require that Docker be installed (it uses Docker directly). And you're running Docker containers, so you must have Docker installed, right?

The message on the portal is maintained by someone else; I can refer him to this thread if needed. But right now, I'd just like to clearly and succinctly understand your issues.

Thanks, and sorry for my confusion. There's multiple teams maintaining different components, and I need to clearly understand what's happening so I can involve the proper teams.

from oms-agent-for-linux.

I'm having the same issue. TCP port 25225 is not running.
There is a tcp port 24220 and a UDP port 25224 coming from a ruby script which I assume is the OMS agent.

following the instructions exactly, on multiple machines, port 25225 is never running.

Host OS is Centos 7.1
Docker v 1.9.1
omsagent version 1.1.0-239

changing the docker options line to use
OPTIONS="--log-driver=fluentd --log-opt fluentd-address=localhost:24220"

instead of

OPTIONS="--log-driver=fluentd --log-opt fluentd-address=localhost:25224"

works like a charm.

from oms-agent-for-linux.

Hi all, In some cases the docker configuration does not get loaded as part of the agent install. The container.conf file can be found here - and can be copied over to /etc/opt/microsoft/omsagent/conf/omsagent.d/.

This configuration file opens the port to listen for logs being sent from the docker daemon.

from oms-agent-for-linux.