Jericho, can you please try to generate a crash dump as described in http://www.ntop.org/support/kb/how-to-report-a-bug-on-ntop-apps/
Thanks Luca On Nov 7, 2012, at 10:52 AM, Jericho Gutierrez <[email protected]> wrote: > Hello - > > I'm evaluating the demo version of nProbe as a flow probe for Scrutinizer. > However, I'm finding that nProbe crashes fairly regularly and has to be > restarted. I'm running it at the console to debug the service: > > nprobe /c -i 0 -n 10.111.2.40:2055 -b 1 -V 10 -T "%RTP_FIRST_SSRC > %RTP_FIRST_TS %RTP_LAST_SSRC %RTP_LAST_TS %RTP_IN_JITTER %RTP_OUT_JITTER > %RTP_IN_PKT_LOST %RTP_OUT_PKT_LOST %RTP_OUT_PAYLOAD_TYPE %RTP_IN_MAX_DELTA > %RTP_OUT_MAX_DELTA %L7_PROTO_NAME %IPV4_SRC_ADDR %IPV4_DST_ADDR > %IPV4_NEXT_HOP %INPUT_SNMP %OUTPUT_SNMP %IN_PKTS %L4_DST_PORT %L4_SRC_PORT > %IN_BYTES %FIRST_SWITCHED %LAST_SWITCHED %PROTOCOL %IPV4_SRC_MASK > %IPV4_DST_MASK %IN_SRC_MAC %OUT_DST_MAC % TCP_FLAGS %CLIENT_NW_DELAY_SEC > %CLIENT_NW_DELAY_USEC %SERVER_NW_DELAY_SEC %SERVER_NW_DELAY_USEC > %APPL_LATENCY_SEC %APPL_ LATENCY_USEC %LAST_SWITCHED %FIRST_SWITCHED > %IN_BYTES %IN_PKTS %OUT_BYTES %OUT_PKTS %SIP_CALL_ID %SIP_CALLING_PARTY > %SIP_CALLED_PARTY %SIP_RTP_CODECS %SIP_RTP_IPV4_SRC_ADDR %SIP_RTP_L4_SRC_PORT > %SIP_RTP_IPV4_DST_ADDR %SIP_RTP_L4_DST_PORT %SIP_FAILURE_CODE > %SIP_REASON_CAUSE %TRANS_RTP_JITTER %ipClassOfService" > > I'm not seeing any errors when it stops. Is there a way to get more debug > info to troubleshoot this? > > Thanks in advance, > > -Jericho > > _______________________________________________ > Ntop-misc mailing list > [email protected] > http://listgateway.unipi.it/mailman/listinfo/ntop-misc
_______________________________________________ Ntop-misc mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-misc
