NethSecurity Version: 8-23.05.5-ns.1.4.1 Module: Realtime Monitor: WAN Uplinks
Bug (?): The server that has previsouly been defined in the Ping latency monitor ist not monitored after system restart.
Reproducible: Yes, after every system restart
More Info: the server has already been definied previously, and the hostname to be monitored is listed in the field under “Ping latency monitor”, but it is not used under Realtime Monitor | WAN Uplinks – the monitor frame is empty and a notice is displayed to set a server under “Ping latency monitor”.
Simply going to the “Ping latency monitor” screen and clicking “Save” (the hostname value is already defined) results in correct monitoring of the server.
Just to exclude a browser issue, did you try a (hard-)refresh? Which browser did you use?
I get this when I add a new ping latency monitor host but after some time the stats are there. I couldn’t reproduce it after a restart of NethSecurity.
yes tested with Chrome and Firefox, and because of another issue (described in another thread, and solved(!) with many reboots of Nethsecurity.
The behaviour is consistent: the previously defined value of the target (I have only one defined) for “Ping latency monitor” (a server name) is not used / activated after reboot of Nethsecurity server.
In order to make it work: without having to re-enter the value, simply clicking “save” again in the “Ping latency monitor” entry page will do it.
I will have a look in the logs to see if there is anything related to this.