Unable to capture traffic in Solaris 11


(Rodrigo Porto) #1

Hi, first, sorry about my English.

We need to use packetbeat on Solaris 11 servers.

Using go 1.5 builds OK:

ldd ./packetbeat-1.0.0-rc1

libsocket.so.1 => /lib/64/libsocket.so.1
libnsl.so.1 => /lib/64/libnsl.so.1
libsendfile.so.1 => /lib/64/libsendfile.so.1
libpcap.so.1 => /usr/lib/64/libpcap.so.1
libc.so.1 => /lib/64/libc.so.1
libmp.so.2 => /lib/64/libmp.so.2
libmd.so.1 => /lib/64/libmd.so.1
libsoftcrypto.so.1 => /lib/64/libsoftcrypto.so.1
libelf.so.1 => /lib/64/libelf.so.1
libcryptoutil.so.1 => /lib/64/libcryptoutil.so.1
libz.so.1 => /lib/64/libz.so.1
libm.so.2 => /lib/64/libm.so.2

But then, trying to capture traffic (with simultaneous curl requests to some HTTP servers):

./packetbeat-1.0.0-rc1 -c ./etc/packetbeat.yml -e -v -d "*"

2015/11/25 14:56:36.605957 beat.go:94: DBG Initializing output plugins
2015/11/25 14:56:36.606057 geolite.go:52: WARN Couldn't load GeoIP database
2015/11/25 14:56:36.606242 publish.go:196: DBG create output worker: 0xc82115a010, 0xc82115a010
2015/11/25 14:56:36.606308 publish.go:233: DBG No output is defined to store the topology. The server fields might not be filled.
2015/11/25 14:56:36.606384 publish.go:245: INFO No shipper name configured, using hostname 'yvas0f00'
2015/11/25 14:56:36.606570 beat.go:103: DBG Init packetbeat
2015/11/25 14:56:36.607551 packetbeat.go:153: DBG Initializing protocol plugins
2015/11/25 14:56:36.607600 mongodb.go:73: DBG Init a MongoDB protocol parser
2015/11/25 14:56:36.607634 memcache.go:105: DBG init memcache plugin
2015/11/25 14:56:36.607652 memcache.go:158: DBG maxValues = 0
2015/11/25 14:56:36.607661 memcache.go:159: DBG maxBytesPerValue = 2147483647
2015/11/25 14:56:36.607718 tcp.go:211: DBG Port map: map[5432:pgsql 9090:thrift 27017:mongodb 80:http 8080:http 5000:http 11211:memcache 8000:http 8002:http 3306:mysql 6379:redis]
2015/11/25 14:56:36.607743 udp.go:93: DBG Port map: map[53:dns 11211:memcache]
2015/11/25 14:56:36.607758 packetbeat.go:192: DBG Initializing sniffer
2015/11/25 14:56:36.607800 sniffer.go:247: DBG BPF filter: tcp port 80 or tcp port 8080 or tcp port 8000 or tcp port 5000 or tcp port 8002 or tcp port 3306 or tcp port 6379 or tcp port 5432 or tcp port 9090 or tcp port 27017 or udp port 53 or port 11211
2015/11/25 14:56:36.607823 sniffer.go:129: DBG Sniffer type: pcap device: net0
2015/11/25 14:56:36.609211 decoder.go:37: DBG Layer type: Ethernet
2015/11/25 14:56:36.609349 packetbeat.go:224: DBG Waiting for the sniffer to finish
2015/11/25 14:56:37.105269 sniffer.go:293: DBG Interrupted
2015/11/25 14:56:37.605234 sniffer.go:293: DBG Interrupted
2015/11/25 14:56:38.105222 sniffer.go:293: DBG Interrupted
2015/11/25 14:56:38.605204 sniffer.go:293: DBG Interrupted
2015/11/25 14:56:39.105191 sniffer.go:293: DBG Interrupted
2015/11/25 14:56:39.605180 sniffer.go:293: DBG Interrupted
2015/11/25 14:56:40.105165 sniffer.go:293: DBG Interrupted
2015/11/25 14:56:40.605152 sniffer.go:293: DBG Interrupted
2015/11/25 14:56:40.830239 service.go:24: DBG Received sigterm/sigint, stopping
2015/11/25 14:56:41.105138 sniffer.go:293: DBG Interrupted
2015/11/25 14:56:41.105223 sniffer.go:355: INFO Input finish. Processed 0 packets. Have a nice day!
2015/11/25 14:56:41.105247 beat.go:137: DBG Cleanup

No single packet captured.

Same behavior with version 1.0.0

Same test on Linux works perfectly well.

Any idea? Some kind of bug or limitation in "gopacket" with non-Linux kernels?

Thanks in advance.


(Andrew Kroh) #2

See my response in the Github issue you created:


(system) #3