sipxproc -m <process_alias> will provide more information on why a
process is in a given state.
ConfigurationMismatch indicates that the version of the installed
software does not match the version of the configuration files. This
can occur each month when we change sprint versions (e.g. 3.11.8 -
3.11.9). It should take care of itself after a minute or so, in that
sipXconfig will replicate new config files and update the version, and
the processes will then start up.
ResourceRequired indicates that the process is blocked because some
resource it requires does not exist or is not ready. You can see the
list of required resources using sipxproc -m <alias>. Normally this
will resolve itself as sipXconfig replicates files and tables, and
processes start up. There are still some kinks in the process def files
and in the code which are being worked out.
ConfigurationTestFailed means that the process's configtest detected
some problem in the configuration. Again, sipxproc -m <alias> will show
the output of the configtest. Configtest is run each time a process is
started or restarted. If it occurs "intermittently", it must mean that
config changes were made, then the process was restarted (perhaps by
Applying the change), and the configtest script did not like the config
changes.
Hope this help,
Carolyn
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of Ananda
Teertha
Sent: Friday, December 12, 2008 9:56 AM
To: [email protected]
Subject: Re: [sipX-dev] Regarding ConfigurationTestFailed
In addition, it will be helpful if someone can explain the terms
ConfigurationMismatch, ResourceRequired as well.
When do they occur? How to debug them..
Anand
Ananda Teertha wrote:
Hi All,
Could some one please tell me what is meant by
ConfigurationTestFailed?
We are running into this problem quite often.
When and why does this problem occur?. How to debug
this?
This issue is quite intermittent and suddenly pops up at
some random time.
Appreciate your response.
An example is,
"SipXrelay"=>"ConfigurationTestFailed",
"SIPXProxy"=>"ConfigurationTestFailed"}
Thanks,
Anand
________________________________
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive:
http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe:
http://list.sipfoundry.org/mailman/listinfo/sipx-dev
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
