Jaeger tracing kubernetes-VM setup problem.

90 views
Skip to first unread message

Aditya

unread,
Jan 3, 2018, 3:04:29 AM1/3/18
to Jaeger Tracing
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:
Trying x.x.x.x...
Connected to internal-xxxx.ap-south-1.elb.amazonaws.com.
Escape character is '^]'.

Also, healthcheck port(which I opened separately) is working:
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?

Prithvi Raj

unread,
Jan 3, 2018, 8:30:28 AM1/3/18
to Aditya, Jaeger Tracing
Hi Aditya, 
 
{"level":"info","ts":1514898053.882661,"caller":"peerlistmgr/peer_list_mgr.go:176","msg":"Connected to peer","host:port":"[::]:14267"}


I see the above in the log lines that you posted, which correspond to the following code snippet:
if conn.IsActive() {
m.logger.Info("Connected to peer", zap.String("host:port", conn.RemotePeerInfo().HostPort))
numConnected++
if numConnected >= minPeers {
return
}
}
I'm wondering whether the log line isn't displaying the hostname of the remote peer for some reason.
Could you submit some traces to the agent and look at the agent metrics to verify that they are reported accurately?

--
You received this message because you are subscribed to the Google Groups "Jaeger Tracing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jaeger-tracing+unsubscribe@googlegroups.com.
To post to this group, send email to jaeger-tracing@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jaeger-tracing/34bbbe16-21c5-47a1-9a49-7b2a030b7524%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages