Nagstamon crashes on start if the monitoring server is unreacheable

[nmarie276]

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:

EventData 

- System 
 
  - Provider 
   [ Name]  Application Error 
   [ Guid]  {a0e9b465-b939-57d7-b27d-95d8e925ff57} 
   EventID 1000 
   Version 0 
   Level 2 
   Task 100 
   Opcode 0 
   Keywords 0x8000000000000000 
 
  - TimeCreated 
   [ SystemTime]  2024-10-08T11:27:44.2533140Z 
   EventRecordID 164659 
   Correlation 
 
  - Execution 
   [ ProcessID]  27024 
   [ ThreadID]  28812 
   Channel Application 
   Computer LAPTOP.acme.corp 
 
  - Security 
   [ UserID]  S-1-5-21

- EventData 

  AppName Nagstamon.exe 
  AppVersion 0.0.0.0 
  AppTimeStamp 66d5d6de 
  ModuleName Qt6Core.dll 
  ModuleVersion 6.7.2.0 
  ModuleTimeStamp 6662f2a0 
  ExceptionCode c0000409 
  FaultingOffset 0000000000025508 
  ProcessId 0x408c 
  ProcessCreationTime 0x1db197510796698 
  AppPath C:\Program Files\Nagstamon\Nagstamon.exe 
  ModulePath C:\Program Files\Nagstamon\_internal\PyQt6\Qt6\bin\Qt6Core.dll 
  IntegratorReportId 4dea77e6-c510-47c2-a889-24fbda9a3572 
  PackageFullName  
  PackageRelativeAppId  
 

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.

[HenriWahl]

What monitor server type do you connect to?

[nmarie276]

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.

[nmarie276]

Hello.

Just upgraded to Nagstamon 3.16.1 and I can still reproduce the issue. Please find the attached debug logs.

• nagstamon-issue-1061.log
• nagstamon-azure-issue-1061.log

Regards.