Code: Select all
check_command check-host-aliveNagios repeated notifications with passive checks
Re: Nagios repeated notifications with passive checks
Is there a reason for your service check command to be:
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: Nagios repeated notifications with passive checks
yea i was just using 1 for testing purposes, I'll set it to 5.
I am looking at /var/log/nagios/nagios.log
I am looking at /var/log/nagios/nagios.log
Code: Select all
[1386565200] CURRENT HOST STATE: localhost;UP;HARD;1;PING OK - Packet loss = 0%, RTA = 0.03 ms
[1386565200] CURRENT SERVICE STATE: localhost;TRAP;WARNING;HARD;1;TRAP trap received
[1386568603] Auto-save of retention data completed successfully.
[1386572203] Auto-save of retention data completed successfully.
[1386575803] Auto-save of retention data completed successfully.
[1386579403] Auto-save of retention data completed successfully.
[1386583003] Auto-save of retention data completed successfully.
Re: Nagios repeated notifications with passive checks
You wouldn't by chance have any escalations configured on this host/service would you?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.