Hello,

I have been working for days trying to resolve a segfault issue like the 
following:

Nov  4 10:46:54 NTOP-SC kernel: ntop[25479]: segfault at 645 ip 
00007f95f3cf3395 sp 00007f95e9b75ae8 error 6 in 
libntop-4.1.1.so[7f95f3cb9000+56000]

The environment is an ESX 5 VM.

Guest OS I have tried:

1. CentOS 6
2. Fedora 15
3. Network Security Toolkit (uses 4865 of the current dev tree)

Versions I have tried:

1. Current dev tree.
2. Current stable version (4.1.0)

The times variate on where these faults occur, but it is relevant to network 
load factors.

My test networks:

1. Simple home network with all packets going to NTOP.
2. High load work network that can see 25 Gig in 15 mins.

The most stable I have seen is a clean CentOS install, build ntop from trunk 
tree, install and run.

The quickest segfault I can obtain is when I implement PF_RING, use a e1000 
card in the vm, and use the pf_ring aware e1000 driver.   Can get a segfault 
usually within 30 mins on the busy network.

The common theme is the segfaulting.  I did attempt a gdb on the device one 
time and saw a malloc issue, but all these VMs have 4GB memory and I have tried 
tuning different hash sizes to see how this impacts the issue, but it really 
never does.  Use smaller hash values, and I get more messages of low memory, 
etc.

I am really not sure what else to do, if there is anything I can do to present 
more information, please let me know as I would like to stop this incessant 
segfaulting.






_______________________________________________
Ntop-misc mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

Reply via email to