Hello
I checked again based on the talks in #opsv...@irc.freenode.net channel with
you last night.
Sending nsca notify to all slaves instead of master still has the same
problem.
So I changed configuration as per Ton Voon's advice.
After that, state revert problem was solved.
2009/6/15 Duncan
On 15 Jun 2009, at 03:13, Kang wrote:I checked this again.Changing State is repeats of the last manual state change to OK.Service Ok[15-06-2009 10:57:44] SERVICE ALERT: hostname;syslog_event;OK;HARD;1;WILL THIS REPEAT? <--- AUTOMATIC STATE REVERT( This should not happen ) Service Critical[15-
On 12 Jun 2009, at 15:11, Kang wrote:
> We have centeralized syslog server which collects logs from all
> servers for matching patterns with SEC
> and notify to master mointoring server(passive check) by nsca_send
> command.
>
> (master) <-notify---
> / \ |
> (
I checked this again.
Changing State is repeats of the last manual state change to OK.
Service Ok[15-06-2009 10:57:44] SERVICE ALERT:
hostname;syslog_event;OK;HARD;1;WILL THIS REPEAT? <--- AUTOMATIC STATE
REVERT( This should not happen )
Service Critical[15-06-2009 10:40:48] SERVICE ALERT:
Hello.
We have centeralized syslog server which collects logs from all servers for
matching patterns with SEC
and notify to master mointoring server(passive check) by nsca_send command.
(master) <-notify---
/ \ |
(slave) (slave)(log server)
Master doesn't do
