Hello,
I am running a Jaeger setup with the following setup:
> Jaeger collector: kubernetes pod and service ( with an ELB and having ports 14267, 14268, 14269, 9411 open)
> Jaeger query : kubernetes pod and service ( with an ELB )
> Jaeger agent running on VM along with the application and the concerned Jaeger client.
The problem is, Jaeger agent is not showing the Jaeger as connected. The following is coming in logs:
{"level":"info","ts":1514898052.7557952,"caller":"agent/main.go:64","msg":"Starting agent"}
{"level":"info","ts":1514898053.7556117,"caller":"peerlistmgr/peer_list_mgr.go:157","msg":"Not enough connected peers","connected":0,"required":1}
{"level":"info","ts":1514898053.755709,"caller":"peerlistmgr/peer_list_mgr.go:166","msg":"Trying to connect to peer","host:port":"internal-xxxx.ap-south-1.elb.amazonaws.com:14267"}
{"level":"info","ts":1514898053.882661,"caller":"peerlistmgr/peer_list_mgr.go:176","msg":"Connected to peer","host:port":"[::]:14267"}
But the connection is present. The output of telnet is:
HTTP/1.1 204 No Content
Date: Tue, 02 Jan 2018 13:03:59 GMT
/metrics on port 14268 is working and producing the ouput.
Any Idea of what I am doing wrong, or what needs to be checked?