Ntopng: mvneta0: promiscuous mode disabled, Either port in use or another ntopng instance
-
Netgate 2100
23.09.1-RELEASE (arm64)
built on Wed Dec 6 13:22:00 MST 2023
FreeBSD 14.0-CURRENTMorning,
After restarting several times, I decided to take a look at the logs and found:
Mar 26 04:09:00 sshguard 87024 Exiting on signal. Mar 26 04:08:20 kernel mvneta0: promiscuous mode disabled Mar 26 04:08:20 kernel pid 49524 (ntopng), jid 0, uid 0: exited on signal 11 (core dumped)
and
Mar 25 19:00:14 ntopng 30736 [HTTPserver.cpp:1679] ERROR: Either port in use or another ntopng instance is running (using the same port) Mar 25 19:00:14 ntopng 30736 [HTTPserver.cpp:1673] ERROR: Unable to start HTTP server (IPv4) on ports 3000s Mar 25 19:00:14 ntopng 30736 [mongoose.c:4647] ERROR: set_ports_option: cannot bind to 3000s: No error: 0 Mar 25 19:00:14 ntopng 30736 [HTTPserver.cpp:1388] ERROR: [HTTP] set_ports_option: cannot bind to 3000s: Address already in use
and
Mar 25 18:59:45 php-fpm 19320 /rc.start_packages: The command '/usr/local/etc/rc.d/ntopng.sh stop' returned exit code '1', the output was 'No matching processes were found No matching processes were found'
I'm rebooting now, but is there another way to fix this? Also can the port be changed?
-
@nasheayahu Did you discover what other process had port 3000 locked?
-
@dennypage said in Ntopng: mvneta0: promiscuous mode disabled, Either port in use or another ntopng instance:
Did you discover what other process had port 3000 locked?
Evening, not yet, and after the reboot and as of today is running as expected...., but will see how long, the only I have done is run the gui in another web tab, so I will give it a try and see what happens in a few days. Also I do run it from another system, so maybe that's causing the problem. I will test that also.