NtopNG is very unstable on arm64
NtopNG will start and run after being initially configured even though this error:
Jul 21 17:20:37 ntopng [Redis.cpp:111] ERROR: ntopng requires redis server to be up and running Jul 21 17:20:37 ntopng [Redis.cpp:112] ERROR: Please start it and try again or use -r Jul 21 17:20:37 ntopng [Redis.cpp:113] ERROR: to specify a redis server other than the default
At that point it is possible to connect to it.
However if you restart the service or reboot the firewall you see this:
Jul 21 17:52:02 ntopng [HTTPserver.cpp:1005] ERROR: [HTTP] set_ports_option: cannot bind to 3000s: Address already in use Jul 21 17:52:02 ntopng [mongoose.c:4591] ERROR: set_ports_option: cannot bind to 3000s: No error: 0 Jul 21 17:52:02 ntopng [HTTPserver.cpp:1189] ERROR: Unable to start HTTP server (IPv4) on ports 3000s Jul 21 17:52:02 ntopng [HTTPserver.cpp:1195] ERROR: Either port in use or another ntopng instance is running (using the same port)
At that point it is no longer possible to connect to the service and attempting to do so will cause further problems such as:
Jul 21 17:52:20 kernel pid 11689 (ntopng), jid 0, uid 0: exited on signal 11 (core dumped) Jul 21 17:52:20 kernel bridge0: promiscuous mode disabled Jul 21 17:52:23 kernel bridge0: promiscuous mode enabled
In one case an SG-1100 rebooted after that.
I note that x86 installs also show similar error and freqyent coredumps but continue to be mostly accessible.