Hi
this bug is strange. Is it possible to ssh to your host to see what happens?
Cheers Luca
On 06/11/2013 11:31 AM, Dpto. Datos Television Costa Blanca wrote:
Hi,
Im glad to help you debugging this.
11/Jun/2013 11:32:08 [NetworkInterface.cpp:207] WARNING: IPv4
fragments are not handled yet
11/Jun/2013 11:32:08 [NetworkInterface.cpp:207] WARNING: IPv4
fragments are not handled yet
11/Jun/2013 11:32:09 [NetworkInterface.cpp:383] Purged 5752/27016 idle
flows
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe6ffd700 (LWP 3253)]
0x000000000040f663 in Flow::key (this=0x7fffc7c5d8e0) at Flow.h:92
92 inline u_int32_t key() {
return(src_host->key()+dst_host->key()+src_port+dst_port+vlanId+protocol);
}
(gdb) backtrace
#0 0x000000000040f663 in Flow::key (this=0x7fffc7c5d8e0) at Flow.h:92
#1 0x000000000040fa87 in GenericHash::add (this=0x7686a0,
h=0x7fffc7c5d8e0) at GenericHash.cpp:62
#2 0x00000000004250a6 in NetworkInterface::getFlow (this=0x768d90,
src_eth=0x7ffff601866c "", dst_eth=0x7ffff6018666 "", vlan_id=0,
src_ip=0x7fffe6ffcc30,
dst_ip=0x7fffe6ffcc50, src_port=7531, dst_port=22336, l4_proto=17
'\021', src2dst_direction=0x7fffe6ffcc2e, first_seen=1370943129,
last_seen=1370943129)
at NetworkInterface.cpp:137
#3 0x00000000004255e0 in NetworkInterface::packet_processing
(this=0x768d90, time=1370943129001, eth=0x7ffff6018666, vlan_id=0,
iph=0x7ffff6018674, ip6=0x0,
ipsize=46, rawsize=60) at NetworkInterface.cpp:249
#4 0x0000000000425b9b in NetworkInterface::packet_dissector
(this=0x768d90, h=0x7fffe6ffcde0, packet=0x7ffff6018666 "") at
NetworkInterface.cpp:357
#5 0x0000000000429681 in pcap_packet_callback (args=0x768d90
"\360\231R", h=0x7fffe6ffcde0, packet=0x7ffff6018666 "") at
PcapInterface.cpp:67
#6 0x00007ffff7bab44c in ?? () from
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8
#7 0x00007ffff7bad971 in pcap_loop () from
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8
#8 0x00000000004296bc in packetPollLoop (ptr=0x768d90) at
PcapInterface.cpp:75
#9 0x00007ffff71f9e9a in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007ffff650cccd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000000000 in ?? ()
Thank you!,
El 11/06/2013 10:39, Luca Deri escribió:
Hi,
I need you to help me debugging the issue. Please use gdb or valgrind
to see what happens or send me (private) a mail with the login
credentials
We're still working at the performance, this is the current ongoing
work. I have not understood if we not use more or less CPU with
respect to before
We will add the demon mode.
Regards Luca
On 06/11/2013 10:16 AM, Dpto. Datos Television Costa Blanca wrote:
Hi all,
Updating this, just downloaded the last svn one, now it goes faster,
but still crashing but without saying the Segmentation Fault.
Now it uses at least more CPU, like 30-40% of total.
Thank you,
El 10/06/2013 20:43, Dpto. Datos Television Costa Blanca escribió:
Hi all,
Just installed Ntopng on a ubuntu server 64bits.
I'm getting tons of [NetworkInterface.cpp:268] WARNING: IP
fragments are not handled yet!
and [NetworkInterface.cpp:268] WARNING: IPv4 fragments are not
handled yet!
Is it possible to run ntopng in daemon mode like old ntop?
Can those messages be ignored?
When I start it, starts working well, but suddenly it start going
really slow, only reading 2Mbps, 19Mbps, 0Mbps, 2Mbps... then
segmentation fault. I It happens in less than a minute or can be
working for 5 o 6.
Htop sais ntopng is only using 3% cpu in 2 threads (total 6%)
Luca, I can give you access to the machine for testing if you want.
Also, Im getting like 65% of traffic as unknow.
Thank you,
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
