ntopng - You're not supposed to be here!

florisveulemans

Thanks @aivxtla, stopping and restarting ntopng does the trick!

Gertjan

When using the 'RC' version, I would do a reboot after each update.
This will eliminate this kind of situations.
( and force to bring up other, much worse, situations ^^ )

pwnell

I get the same error after upgrading from the latest 2.4.5 to 2.5.0 Release. A reboot did not help. Stop / start of ntop did not help. I get it when I click on a host.

Batnun

Same problem here with the final 21.02 version on the Netgate SG-5100 (NTOPNG 4.2), happened when I click on a host.

Hoodwink

I'm getting the same error as well since updating to the 2.5.0 release.

Paint

I also cannot get ntopng to start or login for that matter after updating to pfSense 2.5

pietjepuk

Same problem here, pfsense 2.5, when clicking on a host i get You're not supposed to be here!
After disabling and enabling ntopng again the error disappears some time and then comes back again.

Brgds Piet

pbnet

Same issue on PFSense+ 21.02.

florisveulemans

@sbourdeaud posted a possible fix;

https://forum.netgate.com/topic/161495/solved-ntopng-you-re-not-supposed-to-be-here-missing-lua-module-active_monitoring-am_utils

Have not tried it as after a fresh install I didn't encounter the issue (yet).

Batnun

@florisveulemans After posting here, I removed NTOPNG completely (include the settings), and re-installed it.
That was 3 days ago, seems ok so far. I didn't touch the Timeseries settings.

pbnet

@batnun How did you remove all the settings?

Thanks.

Batnun

@pbnet before removing ntopng, uncheck Keep Data/Settings in ntopng settings (enabled by default):

pbnet

@batnun Thanks a lot.
Works great so far on 21.02-RELEASE-p1

silentnomad

@pbnet I know that was quite a while ago but I was wondering if you or anyone else were still getting this issue? I'm on 2.5.1 and I reinstalled ntopng and made sure to not save any settings. All works for a few days and then I get that dreaded error message, and only a re-start of the service fixes it (for a few days at least).

Paint

@silentnomad Im still having these issues so I am interested in seeing how we can get the ntopng package working again

Paint

deleting my data twice and reinstalling ntopng fixed the problem now.

luisbuides

@pwnell a mi me pasa lo mismo al acceder a un host para saber su informacion

michmoor

Curious but do you guys leave ntopng running constantly in the background? Just wondering if you use it for some type of historical feature or something like that.

keyser

@michmoor I let it run continiously because “diagnostics use” usually requires quick intervention and perhaps has a great advantage of being able to see trends for the last couple of minutes.

But to be honest ntopng is notoriously buggy, and I have to restart the package once in a while because it stops generating alerts, and starts showing LUA error text instead of trends when clicking on a client.

Also: Ntopng has very little usable historical data.- it only has some client trends, timeline datavolume and protocol distribution. It really is a near realtime/realtime tool.

silentnomad

@michmoor Yup, keep it running all the time. It's great to help me see which clients are are consuming bandwidth, for example, and I also look at historic bandwidth usage on an interface.

I've done a complete uninstall and re-install, and disabled some features that I didn't need. It's been quite stable and I no longer get the error messages.