NTOP 5.0.1 v2.3 not working under pfsense 2.1-RC1
-
Recently upgraded to pfsense 2.1-RC1. Prior to the update (from RC0), NTOP installed and operated without issue. Since updating to 2.1-RC1, NTOP installs and allows me to access the settings screen, but won't launch. when I go to Diagnostics > ntop, it returns a 'Connection was reset' error page. I've tried to uninstall/re-install ntop, click the XML option, etc. Each method works successfully, only ntop connection reset message appears. The ntop service itself is running steady. Thanks.
-
It's working fine, here, on the latest 2.1 snapshot with the current ntop package.
Anything in the system logs from ntop?
-
It's working fine, here, on the latest 2.1 snapshot with the current ntop package.
Anything in the system logs from ntop?
Not really. If I got into the NTOP Settings and click SAVE. Then attempt to 'Access Ntop', I receive a 'connection reset' message and must BACK to pfsense. However the system log immediately reflects this:
Aug 12 10:41:23 ntop[41094]: THREADMGMT[t685773120]: ntop RUNSTATE: INIT(2)
Aug 12 10:41:23 ntop[41094]: THREADMGMT[t685773120]: ntop RUNSTATE: PREINIT(1)
Aug 12 10:41:19 ntop[16182]: THREADMGMT[t685773120]: ntop RUNSTATE: INIT(2)
Aug 12 10:41:19 ntop[16182]: THREADMGMT[t685773120]: ntop RUNSTATE: PREINIT(1)
Aug 12 10:40:58 check_reload_status: Syncing firewall
Aug 12 10:40:57 ntop[12204]: THREADMGMT[t685773120]: ntop RUNSTATE: INIT(2)
Aug 12 10:40:57 ntop[12204]: THREADMGMT[t685773120]: ntop RUNSTATE: PREINIT(1)
Aug 12 10:40:53 ntop[11639]: THREADMGMT[t685773120]: ntop RUNSTATE: INIT(2)
Aug 12 10:40:53 ntop[11639]: THREADMGMT[t685773120]: ntop RUNSTATE: PREINIT(1) -
That's right at the place it should be daemonizing and running.
Which interface(s) did you select in the NTOP config? What type of NICs are they?
-
I only enabled for LAN. It has worked in the past on pf2.0RC0 just prior to me updating to RC1 this past weekend. It's a Supermicro X7SPA-HF mini ITX motherboard so they are Intel NICs. Wasn't sure if there's anything I can do to uninstall and completely wipe NTOP package from my system in order to reinstall clean?
-
uninstall the ntop package and then from the command line check "pbi_info" to see if it is still listed. If it is, use "pbi_delete <exact name="" as="" shown="" in="" pbi_info="">" to remove it, and then reinstall.</exact>
-
uninstall the ntop package and then from the command line check "pbi_info" to see if it is still listed. If it is, use "pbi_delete <exact name="" as="" shown="" in="" pbi_info="">" to remove it, and then reinstall.</exact>
after uninstalling ntop package, I'm not finding a pbi_info anywhere… or perhaps am not looking in right location.
EDIT: I did notice upon clicking the CHANGE option in NTOP Settings that pfsense appears somewhat unresponsive (waiting state) ... 30-60 seconds before I am able to click another web option. i don't recall there being such a delay in the past.
-
Hi
I have the same problem.
I'm running pfsense 2.0.3 x86This is the only thing I get in the logs:
Sep 14 19:40:26 php: /pkg_mgr_install.php: Beginning package installation for ntop.
Sep 14 19:45:07 check_reload_status: Syncing firewall
Sep 14 19:45:08 check_reload_status: Reloading filter
Sep 14 19:46:40 php: /pkg_edit.php: The command '/usr/local/etc/rc.d/ntop.sh stop' returned exit code '1', the output was 'No matching processes were found'
Sep 14 19:46:42 check_reload_status: Syncing firewall
Sep 14 19:46:44 php: /pkg_edit.php: The command '/usr/local/etc/rc.d/ntop.sh stop' returned exit code '1', the output was 'No matching processes were found'Seems like ntop is not starting at all.
Reinstalled and it didn't help at all.
pbi_info was clean.BR Chris
EDIT:
This is what I get when I start it up directly from ssh:
[2.0.3-RELEASE][dale@asdf]/home/dale(1): /usr/local/etc/rc.d/ntop.sh start
/libexec/ld-elf.so.1: Shared object "libpcap.so.1" not found, required by "ntop"
[2.0.3-RELEASE][dale@asdf]/home/dale(2):BR Chris
-
I am experiencing the same exact problem. Any ideas?
-
Same problem for me, on pfSense 2.0.3, 3 firewalls.
:-\ -
Hi all,
I had a similar problem after updating and tried the reinstall approach.
What I found was that I had to go back into ntop settings and set a new admin password. After I did this, the service started normally.
Cheers,
Toby
