Alerted when I shouldn't have been
Re: Alerted when I shouldn't have been
Yeah, sure seems that way. Got any clues?
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
Re: Alerted when I shouldn't have been
We think this is probably related to your other issue: http://support.nagios.com/forum/viewtop ... 298#p91298
Former Nagios employee
Re: Alerted when I shouldn't have been
Do you have freshness checking enabled on the destination server? That might explain the multiple checks for that service, but still not sure about the 10-second gap.
Former Nagios employee
Re: Alerted when I shouldn't have been
Nope, only place I ever use freshness is with SNMP traps so i can reset back to OK.
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
Re: Alerted when I shouldn't have been
It's been a while on this one so refresh me: Are you using gearman on the server doing the forwarding? I'm thinking that the server doing the forwarding, if it is using gearman, is getting results from gearman at a faster interval that it is supposed to, but since the results are the same it is not updating, but is still forwarding the results every 10 seconds. I'm not a gearman expert so this is just a guess, but this is a weird issue so I don't want to rule anything out.
Former Nagios employee