-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nagstamon crashes on start if the monitoring server is unreacheable #1061
Comments
What monitor server type do you connect to? |
I'm trying to reach a Zabbix 5.0 monitoring server and a Centreon 21.04 one. I will try to upload the debug log. |
Hello. Just upgraded to Nagstamon 3.16.1 and I can still reproduce the issue. Please find the attached debug logs. Regards. |
I can confirm this issue and you can easely reproduce it yourself even without a VPN connection:
This did not happen up to and including version 3.14. |
Hey @nmarie276 - you posted your login credentials in the log files and should consider to change them! |
Regarding the crashes - they seem to have slightly different causes, but well, are annoying. I will try to find some time to inspect this. |
Hello.
I'm using the latest version of Nagstamon under Windows 11. I added a registry to automatically start Nagstamon during logon. My monitoring server is reacheable through our corporate VPN.
I just seen that, if the VPN is not started before Nagstamon, Nagstamon crashes with this content in the Event Viewer:
If I'm not connected to the VPN (so without internal name resolution), Nagstamon crashes immediately. If I add en entry in the Windows
hosts
file, Nagstamon crashes after 15 seconds (probably the request timeout).However, if the VPN isalready started and Nagstamon is running, a VPN deconnection does not cause any crash (I simple see that it cannot reach the monitoring server).
Thanks for your help.
Regards.
The text was updated successfully, but these errors were encountered: