Packetbeat Error on running the compiled binary on different systems

Elastic Stack Beats
1 
2017-04-07T08:19:32Z INFO packet decode failed with: TCP data offset greater than packet length
2017-04-07T08:19:33Z INFO packet decode failed with: Invalid (too small) IP header length (0 < 5)
2017-04-07T08:19:53Z INFO Non-zero metrics in the last 30s: libbeat.es.published_and_acked_events=3901 libbeat.es.publish.read_bytes=43447 libbeat.publisher.messages_in_worker_queues=3630 libbeat.es.call_count.PublishEvents=89 tcp.dropped_because_of_gaps=1 libbeat.publisher.published_events=3877 libbeat.es.publish.write_bytes=2761749 redis.unmatched_responses=1
2017-04-07T08:20:03Z INFO Packetbeat send stop signal
2017-04-07T08:20:03Z INFO Input finish. Processed 84295082 packets. Have a nice day!
2017-04-07T08:20:03Z INFO flows worker loop stopped
2017-04-07T08:20:03Z INFO Total non-zero values:  libbeat.es.call_count.PublishEvents=132324 libbeat.es.published_and_acked_events=5697700 icmp.unmatched_responses=3 libbeat.es.publish.write_bytes=4038166199 libbeat.publisher.published_events=5697702 dns.unmatched_responses=1 libbeat.publisher.messages_in_worker_queues=5233729 redis.unmatched_responses=2496 tcp.dropped_because_of_gaps=2960 libbeat.es.publish.read_bytes=64231606 icmp.unmatched_requests=2
2017-04-07T08:20:03Z INFO Uptime: 19h22m39.848264889s
2017-04-07T08:20:03Z INFO packetbeat stopped.

I get the following error on running a compiled binary on another system, but I get no errors while running it on the same system it was compiled on. Any help would be appreciated.

2

Are they both the same OS?

3

One is a Debian and other is Ubuntu

4

kernel versions? Which sniffer type have you configured?

This error is when parsing an packet. That is, it might not be related to OS, but to actual traffic or hardware...

Can you share your packetbeat config (please use the </> button to format your config)

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.