I am looking at XX-6051 (sipXsupervisor to alert admin when system
services can not start) and I am proposing some new alarms.
An alarm will be raised on entry to ConfigTestFailed or ResourceRequired
state. If the process had blocked in one of these states, then the
ProcessStarted alarm (at info level, no email) will be generated when
the process gets to state Running.
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?
PROCESS_STARTED (info):
"Process '{0}' recovered from a missing resource or failed configtest.
Attempting to start the process."
<resolution>"No action required."
PROCESS_CONFIGTEST_FAILED (crit):
"Process '{0}' failed its configtest."
<resolution>"Check recent configuration changes. Do not hand-edit
configuration files. Check logs for more details."
PROCESS_RESOURCE_REQUIRED (warning):
"Process '{0}' is missing one or more required resources (list
follows)."
<resolution>"Wait for a few seconds to see if this is just a normal
startup sequence. If problem persists, try pressing Send Profiles on
the server page."
PROCESS_CONFIG_MISMATCH (warning):
"The configuration data for process '{0}' ({1}) does not match the
software version ({2})."
<resolution>"Wait for a few seconds to see if this is just a normal
startup sequence. If problem persists, try pressing Send Profiles on
the server page."
Carolyn
_______________________________________________
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/
