Pinpoint: Profile No trace related data

[zhaohaifeng]

Description

Web and collector normal start, but can only view the agent data, can not see the tracking data.。

Environment

• Pinpoint version:1.6.0.release
• OS, WAS, affected library, etc: centos7 X64,openjdk version "1.8.0_111"，hbase 1.0.3
• Additional details (e.g. how your collector/web is set up):
  web and collector in the same tomcat 7.0,and web as ROOT.war,collector as pinpoint-collector-1.6.0.war

Additional Info

I did not start a separate zk, but hbase inherited。
My agent runs in jetty.
I started in my mac quickstart, but can see the data.

[Xylus]

Hi @zhaohaifeng
Could you try running collector and web on a separate instance? I don't think this would be the problem, but it might be worth a try.

Also, does your agent log look different from the one you started from mac quickstart? If you could also post the agent log here, we'll be able to take a look.
Thanks

[zhaohaifeng]

Still unable to work, but I observed agent log, found some different, in the log can not access the trace, a few lines

2016-12-23 18:10:02 [INFO ](.p.r.c.DefaultPinpointClientHandler) [id: 0xae8254c5, /127.0.0.1:52644 => localhost/127.0.0.1:9994] handleHandshakePacket() completed. code:DUPLEX_COMMUNICATION
2016-12-23 18:10:02 [INFO ](c.n.p.p.s.AsyncQueueingExecutor    ) null started.
2016-12-23 18:10:02 [INFO ](c.n.p.p.s.UdpDataSender            ) UdpDataSender initialized. host=localhost, port=9996
2016-12-23 18:10:03 [INFO ](c.n.p.p.s.AsyncQueueingExecutor    ) Pinpoint-UdpSpanDataExecutor(14-0) started.
2016-12-23 18:10:03 [INFO ](c.n.p.p.s.UdpDataSender            ) UdpDataSender initialized. host=localhost, port=9995
2016-12-23 18:10:03 [INFO ](c.n.p.p.s.AsyncQueueingExecutor    ) Pinpoint-UdpStatDataExecutor(15-0) started.
2016-12-23 18:10:03 [INFO ](c.n.p.p.DefaultAgent               ) StorageFactoryType:BufferedStorageFactory{bufferSize=20, dataSender=com.navercorp.pinpoint.profiler.sender.UdpDataSender@6dee4f1b}

2016-12-23 18:46:24 [INFO ](.p.r.c.DefaultPinpointClientHandler) [id: 0xc2c72a78, /192.168.0.5:55146 => /120.26.194.78:9994] handleHandshakePacket() completed. code:DUPLEX_COMMUNICATION
2016-12-23 18:46:24 [INFO ](c.n.p.p.s.AsyncQueueingExecutor    ) null started.
2016-12-23 18:46:24 [INFO ](c.n.p.p.s.UdpDataSender            ) UdpDataSender initialized. host=120.26.194.78, port=9995
2016-12-23 18:46:24 [INFO ](c.n.p.p.s.AsyncQueueingExecutor    ) Pinpoint-UdpStatDataExecutor(15-0) started.
2016-12-23 18:46:24 [INFO ](c.n.p.p.DefaultAgent               ) StorageFactoryType:BufferedStorageFactory{bufferSize=20, dataSender=com.navercorp.pinpoint.profiler.sender.UdpDataSender@4748a0f9}

The first is to use quickstart, you can work, the second my own configuration, can not get the data, less "Pinpoint-UdpSpanDataExecutor (14-0) started"

[Xylus]

Ah yes you're right, the log related to UdpSpanDataSender (to port 9996) is missing... I wonder why that is.
Is there any other errors in the log?

[zhaohaifeng]

I tried again today, UdpSpanDataExecutor normal start, there is no error in the log, but there is no trace data, server jvm data is good.

2016-12-27 11:07:24 [INFO ](.p.r.c.DefaultPinpointClientHandler) [id: 0xed8df460, /192.168.0.5:55122 => /120.26.194.78:9994] handleHandshakePacket() completed. code:DUPLEX_COMMUNICATION
2016-12-27 11:07:24 [INFO ](c.n.p.p.s.UdpDataSender            ) UdpDataSender initialized. host=120.26.194.78, port=9996
2016-12-27 11:07:24 [INFO ](c.n.p.p.s.AsyncQueueingExecutor    ) Pinpoint-UdpSpanDataExecutor(14-0) started.
2016-12-27 11:07:24 [INFO ](c.n.p.p.s.UdpDataSender            ) UdpDataSender initialized. host=120.26.194.78, port=9995
2016-12-27 11:07:24 [INFO ](c.n.p.p.s.AsyncQueueingExecutor    ) Pinpoint-UdpStatDataExecutor(15-0) started.
2016-12-27 11:07:24 [INFO ](c.n.p.p.DefaultAgent               ) StorageFactoryType:BufferedStorageFactory{bufferSize=20, dataSender=com.navercorp.pinpoint.profiler.sender.UdpDataSender@1a6c1270}
2016-12-27 11:07:24 [INFO ](c.n.p.p.DefaultAgent               ) SamplerType:TrueSampler

[zhaohaifeng]

local1-pinpoint.log.zip
this is my log which can't work

[qinshi]

@zhaohaifeng and I find this issue at last, the problem is we use jetty with parameter --exec and jetty will create a child process, but we mistakenly added "-agentlib:...." in start shell (as parameter of parent child) instead of after --exec (as parameter of child process), so our class is not rewrited and trace data cannot be collected.

This is not a problem about pinpoint but usage of jetty, record it here in case someone else may encounter the same situation.

[zhaohaifeng]

@qinshi Well Down! It works for me now~

[Xylus]

Hi @qinshi, thanks for working this out.
If you don't mind, could you add a README.md to the jetty plugin(in this directory) explaining the problem and the solution?
Thanks again.

[qinshi]

ok @Xylus, pull request is submitted (https://github.com/naver/pinpoint/pull/2473)

[Xylus]

@qinshi
Just checked it out and it looks great!
Thanks again :+1: