On Wed, 2009-07-29 at 11:01 -0400, Beeton, Carolyn (CAR:9D60) wrote: > > -----Original Message----- > > From: Lawrence, Scott (BL60:9D30) > > Sent: Wednesday, July 29, 2009 10:18 AM > > To: Beeton, Carolyn (CAR:9D60) > > Cc: [email protected] > > Subject: Re: [sipX-dev] Alarm for ConfigMismatch? > > > > > > > > Question: should I also create an alarm for ConfigMismatch? > > I think I > > > probably should... I am just concerned that it is a normal part of > > > upgrade. How does this sound? > > > > > In answer to your original question, I'm not sure about > > alerting on these conditions that should be ephemeral... I > > don't like sending warnings that we _know_ will happen under > > perfectly ordinary conditions about things that should just > > go away all by themselves. If we could detect that the > > conditions are not those where we expect this, then the > > warnings would certainly be justified... not sure how to do that. > > > > > > Would it be too kludgey a solution to not raise an alarm the first time > these states are encountered (i.e. the first time after every time > supervisor - and hence everything else - starts). That way, processes > can sit in ResourceRequired or ConfigMismatch while sipXconfig does its > initial replication, but if they are still there after sipXconfig > restarts them, an alarm will be raised.
I was going to suggest some such possibility, but didn't want to make trouble for you by adding a state :-) I think that alarming only if the process start was initiated by an explicit restart command probably works fairly well. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
