1.2.3_rc3 and ntop

  • Has anyone else noticed a much higher amount of CPU usage with ntop in this version?

    I'm seeing 50-100% cpu all the time now.

  • never mind, i figured out the issue….device polling is apparently broken in this version (i had 1.2.3_rc1 which it seemingly worked fine in)

  • I have an other (or maybe not) issue with 1.2.3RC3 and ntop:

    The ntop service dies after a few minutes from starting the service with no system log entries to try and figure out the reason. I have pfSense installed on the firewall's HDD.

    Could this be related?

  • Did get this system log entry this time:

    kernel: pid 1680 (ntop), uid 0: exited on signal 11 (core dumped)

  • All i know is that ntop used to never work for me, it's been working fine for the past few months

  • ntop is working perfectly here.  using the 23 october snapshop on an intel d945gclf2 board, dual core atom 330 (4 cores w/ ht turned on), 2gb ddr2, 500gb disk, onboard intel gigabit to my switch and a dual port intel nic with each port going to it's own dsl modem.

  • I used to always have ntop crash on me after a while (random hour to couple of hours).  I put a cron schedule like someone suggested in the forums that starts ntop in case it's crashed.  I've never bothered to change that setting.

    Am I understanding everyone now that the latest 1.2.3 builds do not have that problem with ntop? (so I can delete my cron setting)

  • I used to have it crash all the time, but for the past few month or two it's been stable.
    I dont' have a cron job and it's still running from when i instaled my last snapshot…which was....2 weeks ago

  • kernel: pid 14149 (ntop), uid 0: exited on signal 11 (core dumped)
    kernel: fxp0: promiscuous mode disabled

    uname -a

    FreeBSD pfSense.local 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Sat Oct 31 14:46:26 UTC 2009    sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.7.i386  i386

Log in to reply