Open jithendra12 opened 3 years ago
You have another process already listing on port 24224.
You can change the port that the metrics server is exposed inside the fluent.conf.rt to resolve this issue.
Example:
<source>
@type prometheus
port 22222
</source>
Yes, I tried it already. On the http interface of the VM, it is working fine when I give a port
and metrics_path
to the prometheus source. I am able to see logs printing on http interface in the browser or through curl http://<IP of VM>:24231/metrics
:
<source>
@type prometheus
bind 0.0.0.0
port 24231
metrics_path /metrics
</source>
but, when I start td-agent
in the VM's shell, the earlier error still shows up:
2021-02-06 00:31:44 +0000 [error]: #0 unexpected error error_class=Errno::EADDRINUSE error="Address already in use - bind(2) for 0.0.0.0:24224"
I was wondering if that effects the logs that are being forwarded to http interface.
I have used the same td-agent.conf file provided in this repo: fluent.conf.rt to collect application metrics of jfrog artifactory on a centos VM. but when I start td-agent, I keep seeing these below errors that 24224 port is already in use.
I checked for processes which are using this port to kill them. But couldn't find any. Also, tried opening range of ports 24210 to 24250. Still did not work. Any suggestions on how to resolve or troubleshoot this issue? Thanks!