There is a test in sipxcallresolver.sh{.in} to see if two copies of
sipXproxy are running:
procs=`ps -U dworley`
if expr match "$procs" '.*sipXproxy.*' >/dev/null; then
# At least one sipXproxy is running, check for another one
if expr match "$procs" '.*sipXproxy.*sipXproxy.*' >/dev/null; then
But I've seen it fail in practice:
Starting httpd: Multiple proxy check failed:
Found at least two running sipXproxy processes.
This is a potential cause of CSE logging failures!
302 pts/9 00:00:00 sipXproxy.sh
608 pts/9 00:00:00 sipXproxy.sh
Confirm Stop: sipxpark Confirm Stop: sipxacd Confirm Stop: sipxrls Conf\
irm Stop: sipxpresence Confirm Stop: sipstatus Multiple proxy check failed:
Found at least two running sipXproxy processes.
This is a potential cause of CSE logging failures!
1331 pts/9 00:00:00 sipXproxy
2117 pts/9 00:00:00 sipXproxy.sh
It looks to me that the problem is that the pattern matches detect
"sipXproxy.sh" as well as "sipXproxy". We could fix that by changing
the tests to:
procs=`ps -U dworley`
if expr match "$procs" '.*sipXproxy[^.].*' >/dev/null; then
# At least one sipXproxy is running, check for another one
if expr match "$procs" '.*sipXproxy[^.].*sipXproxy[^.].*' >/dev/null; then
Dale
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
