Problem Logs

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
neo_infraestructura
Posts: 61
Joined: Wed Jan 17, 2018 3:55 pm

Re: Problem Logs

Post by neo_infraestructura »

So I did find the log in /usr/local/nagios/var/nagios.log

Code: Select all

[1532946071] HOST ALERT: NEO-MNG-EPO-TMX02;DOWN;SOFT;1;PING CRITICAL - Packet loss = 100%
Why this log is not in the /var/log/messages or in the loc7 system file?
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Problem Logs

Post by scottwilkerson »

I honestly cannot say for sure, Nagios is trying to write to to the messages file but I do not know what would cause these to be missing.

I'm not sure what your loc7 system file is
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
neo_infraestructura
Posts: 61
Joined: Wed Jan 17, 2018 3:55 pm

Re: Problem Logs

Post by neo_infraestructura »

Do you know if one service state is Critical, Nagios waits 5 minutes (or some other time) to see if the service recover and if its not, then alert it? or it will alert it immediately?
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Problem Logs

Post by scottwilkerson »

It alerts after your (max check attempts X retry interval) in minutes
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
neo_infraestructura
Posts: 61
Joined: Wed Jan 17, 2018 3:55 pm

Re: Problem Logs

Post by neo_infraestructura »

Hi there, I didn't wanted to close the topic because I still can't find the reason for not informig some alerts.

I have another example, There is a service that had a CRITICAL state from 08-10-2018 at 9:24:44, but in the "Availability Report For This Service" (Nagios Core) it didn't show this state.
nagios1.png
nagios2.png
If I search for it in the /usr/local/nagios/var/nagios.log it shows logs only from today

Code: Select all

[root@neo-mng-nag-tmx ~]# cat /usr/local/nagios/var/nagios.log | grep "SFSC-ASG-01" | grep "Temperatura del dispositivo SSL card temperature"
[1534129200] CURRENT SERVICE STATE: SFSC-ASG-01;BluecoatV2 - Chequea los valores de temperatura para los distintos componentes;CRITICAL;SOFT;3;CRITICAL - Temperatura del dispositivo SSL card temperature: -960000: estado = nonoperational(3)
[1534193046] SERVICE NOTIFICATION: SOC;SFSC-ASG-01;BluecoatV2 - Chequea los valores de temperatura para los distintos componentes;CUSTOM (CRITICAL);notify-service-by-syslog;CRITICAL - Temperatura del dispositivo SSL card temperature: -960000: estado = nonoperational(3);Nagios Administrator;Prueba notificacion
[1534193046] SERVICE NOTIFICATION: SOC;SFSC-ASG-01;BluecoatV2 - Chequea los valores de temperatura para los distintos componentes;CUSTOM (CRITICAL);notify-service-by-email;CRITICAL - Temperatura del dispositivo SSL card temperature: -960000: estado = nonoperational(3);Nagios Administrator;Prueba notificacion

Why is not updating the state un the Service Log Entries?
You do not have the required permissions to view the files attached to this post.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Problem Logs

Post by scottwilkerson »

The log only updates when state changes.

For the availability issue, it only show HARD states by default.

There was a bug that was recently uncovered that can cause services to stay in a SOFT state like your is.

This is currently in the maint branch of Nagios Core and is undergoing final testing before the release.
https://github.com/NagiosEnterprises/na ... tree/maint

It will then make it into XI 5.5.3 when it is released.
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
Locked