Bug #7941: ntop-ng. Unable to reach web page - pfSense Packages - pfSense bugtracker

Actions

Copy link

Bug #7941

closed

ntop-ng. Unable to reach web page

Added by Steve Wheeler over 7 years ago. Updated over 7 years ago.

Status:

Not a Bug

Priority:

Normal

Assignee:

Steve Wheeler

Category:

ntop

Target version:

Start date:

10/15/2017

Due date:

% Done:

Estimated time:

Plus Target Version:

Affected Version:

2.4

Affected Plus Version:

Affected Architecture:

Description

After installing and enabling ntop-ng with default settings in 2.4 it is not possible to reach the data display page in some circumstances.
Try to reach it results in a time out.
The logs show:

Oct 15 14:22:13     ntopng         [mongoose.c:4515] ERROR: set_ports_option: cannot bind to 3000s: Address already in use
Oct 15 14:22:13     ntopng         [HTTPserver.cpp:806] ERROR: Unable to start HTTP server (IPv4) on ports 3000s
Oct 15 14:23:22     kernel         pid 75194 (ntopng), uid 0: exited on signal 11 (core dumped)

During install the following errors are logged:

Oct 15 13:56:48 4860 php: /etc/rc.packages: The command '/bin/cp -Rp /usr/local/lib/X11/fonts/webfonts/ /usr/local/lib/X11/fonts/TTF/' returned exit code '1', the output was 'cp: directory /usr/local/lib/X11/fonts/TTF does not exist' 
Oct 15 13:56:55 4860 php: /etc/rc.packages: The command '/usr/bin/fetch -o /usr/local/share/ntopng -T 5 https://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz' returned exit code '1', the output was 'fetch: transfer timed out fetch: /usr/local/share/ntopng/GeoLiteCity.dat.gz appears to be truncated: 0/11754322 bytes'

Actions

Copy link

Updated by Jim Pingle over 7 years ago

Status changed from New to Feedback
Assignee set to Steve Wheeler

I see those errors here but it appears they happen during install or boot when it gets stopped/started a couple times in a row.

It works fine for me, so long as access to the port is allowed. The daemon runs, it is bound to port 3000, I can access it, login, see data, etc. Since it runs on port 3000, the most common error here may be that the user's firewall rules do not allow access to port 3000.

It starts OK after a reboot as well.

The font error appears to need fixing, it's harmless though. Apparently the font location moved but since the ntopng GUI appears to be fine it may not need that old fix any longer so I'll take it out.

If there is a problem here, I don't see it, so we'll need to find out exactly what the special circumstances are which make the problem appear.

Actions

Copy link