Consulta

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
mati-baru
Posts: 1
Joined: Fri Jan 13, 2023 1:00 pm

Consulta

Post by mati-baru »

Hola buenas tardes.

Les hago una consulta ,tengo instalado nagios core Version 4.4.7 en un centos 7 de 64 bits , venia funcionando todo correctamente , hasta que se actualizo el SO , desde entonces nagios quedo como en modo " cache " , no me reconoce cuando detengo el servicio , siempre muestra los mismos datos . Alguno podria ayudarme ? muchas gracias.

[01-13-2023 10:23:36] qh: echo service query handler registered
Informational Message[01-13-2023 10:23:36] qh: core query handler registered
Informational Message[01-13-2023 10:23:36] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
Informational Message[01-13-2023 10:23:36] LOG VERSION: 2.0
Informational Message[01-13-2023 10:23:36] Local time is Fri Jan 13 10:23:36 -03 2023
Program Start[01-13-2023 10:23:36] Nagios 4.4.7 starting... (PID=1160)
Program Restart[01-13-2023 10:23:35] Caught SIGHUP, restarting...
Service Ok[01-13-2023 10:21:57] SERVICE ALERT: Castelar;PING;OK;SOFT;2;PING OK - Packet loss = 0%, RTA = 12.06 ms
Service Warning[01-13-2023 10:20:53] SERVICE ALERT: XXXXXXXX;PING;WARNING;SOFT;1;PING WARNING - Packet loss = 28%, RTA = 12.83 ms
Informational Message[01-13-2023 10:17:00] Auto-save of retention data completed successfully.
sgardil
Posts: 124
Joined: Wed Aug 09, 2023 9:58 am

Re: Consulta

Post by sgardil »

Hey @mati-baru

Sorry that you are having issues after updating your OS. Not sure if I'm understanding this correctly but if you run

Code: Select all

 systemctl stop nagios
 systemctl status nagios
it wont let you stop the service if it was running already? This seems like a strange thing to break for just updating the OS so if you are still having issues with this and you would like to stay on this version of core, do you have a snapshot of the VM before you updated your OS to go back to? If so could you revert and attempt the update again to see if it was just a fluke. If you don't mind updating versions, do you still receive this issue on updating to the current version of core?
Post Reply