PfSense 2.4.3-RELEASE and ntopng Core Dump
-
Same issue on various firewalls we recently updated. Thanks for the tip on not ticking the alerts setting. That got ntopng started for us. Also explains the mystery of why a couple of the firewalls had ntopng running - they had the alert setting already unticked.
-
By default, alert is unchecked and checking does nothing to get it running…the ball seems to have been dropped for January's update. According to the developer:
Redis is a separate server package, just like mysql, for example. MySQL
provides separate server package and client libraries. ports usually
depend only on the client part. No dependency is added on the server,
because the server needs extra configuration, but most importantly the
server does not need to run on the same machine.Redis does not have a "client library" so no dependency is needed to
compile and run ntopng. The redis server is required but could run on
another machine. Adding an hard dependency on redis would not solve your
problem (you would anyway have to start and maybe configure it) and
would be an annoyance for people using a redis server residing somewhere
else (another machine, or perhaps the amazon Elasicache service).So, it seems that, that were missed with the upgrade to Pfsense 2.4.3 release. That Redis issue started sometime in January as that's when It stops working for me; so, I uninstalled with hope would get fixed for April's release...disappointed now!
-
any updates on this? I am experiencing the same issues with ntopng after updating. I'm missing my beloved ntopng :'( :'( :'(
-
Yeah curious about this as well as the same thing is happening to me and its one of the reason why I installed pfSense for.
I've tried all the fixes but it still ends up with a core dump.
I've seen posts about maybe updating it to the package from the 2.3.5 release but not sure how one would do that?
-
Yeah curious about this as well as the same thing is happening to me and its one of the reason why I installed pfSense for.
I've tried all the fixes but it still ends up with a core dump.
I've seen posts about maybe updating it to the package from the 2.3.5 release but not sure how one would do that?
latest version of ntopng (0.8.12) solves the problem
-
Yeah curious about this as well as the same thing is happening to me and its one of the reason why I installed pfSense for.
I've tried all the fixes but it still ends up with a core dump.
I've seen posts about maybe updating it to the package from the 2.3.5 release but not sure how one would do that?
latest version of ntopng (0.8.12) solves the problem
And how would I install it? Because according to pfSense I am running the latest version.
-
Yeah curious about this as well as the same thing is happening to me and its one of the reason why I installed pfSense for.
I've tried all the fixes but it still ends up with a core dump.
I've seen posts about maybe updating it to the package from the 2.3.5 release but not sure how one would do that?
latest version of ntopng (0.8.12) solves the problem
I have updated nTopNG to 0.8.12 and package manager says that as well. But still not able to start the service.
I have unticked the Disable alerts in NtopNG settings
Also checked the /usr/local/etc/rc.d/ntopng.sh file and there is no -H in line 9.Any thoughts?
-
I solved this,
Uninstalled ntopng package, and reinstall.
After setting up the config and save, ntopng is now running.
-
even updating to 2.4.4 gives me the same problem: 0.8.13_1
pid 50447 (ntopng), uid 0: exited on signal 11 (core dumped)
Any ideas?
-
Same here with pfsense 2.4.4-RELEASE (amd64)
kompiliert am: Thu Sep 20 09:03:12 EDT 2018
FreeBSD 11.2-RELEASE-p3pid 81079 (ntopng), uid 0: exited on signal 11 (core dumped)
:(
uninstalled with deleting settings, reinstalled, no change.
I'm using squid and squidguard, snort and lightsquid...
