Kernel: pid 55776 (ntop), uid 0: exited on signal 11 (core dumped)
-
Bump? Anyone? Or is this problem documented and I've missed it?
-
i have this problem.
any solution?
thx.
juanjoA
-
I'm seeing the same error. It seems to dump when I monitor an interface that has VLAN's present.
Idea's anyone?
Thanks, Steve
-
I'm getting this too, and it's very sad. Please help. :(
-
Anybody?
-
I've had this problem also, from everything i've read it appears to be memory. Ntop is very very ram hungry. I would say you would need 1-2gigs of ram for 10,000 states. Don't take that for fact, i've never been able to keep ntop running for more then a couple of hours, but i always assumed i didn't have enough memory.
The next version of ntop 3.3.9 has some fixes for low memory so it doesn't crash.
-
Thanks for the reply, but I don't think that's my problem: the machine we have has 4 gigs of memory so that pfSense will read the maximum it can handle. :(
-
Thanks for the reply, but I don't think that's my problem: the machine we have has 4 gigs of memory so that pfSense will read the maximum it can handle. :(
How many states are doing? Are you tracking both local and remote hosts?
-
Ive found P2P has a huge impact on NTOP on pfsense as well and is part of the reason it crashed for me, since I banned P2P on my network and up'd more memory, I havent had a crash since.
Slam
-
i've got the same problem, when will the update be ready for pfsense?
