Woof! I stopped the sipXivr process via the XML-RPC inteface to sipxsupervisor. Now every 5 seconds this appears in the logs:
"2008-09-04T19:55:53.369326Z":3211:PROCESSMGR:ERR:woof::B70FEB90:WatchDog:"OsProcessMgr::getProcessByAlias non-integer pid 'STOPPED' for alias 'sipXivr'" "2008-09-04T19:55:58.367620Z":3212:PROCESSMGR:ERR:woof::B70FEB90:WatchDog:"OsProcessMgr::getProcessByAlias non-integer pid 'STOPPED' for alias 'sipXivr'" "2008-09-04T19:56:03.367614Z":3213:PROCESSMGR:ERR:woof::B70FEB90:WatchDog:"OsProcessMgr::getProcessByAlias non-integer pid 'STOPPED' for alias 'sipXivr'" ... And while on the subject of annoying log entries, this one appears everytime an XML-RPC connection closes which is normal behavior after the transaction is complete: "2008-09-04T15:44:36.097279Z":195:HTTP:WARNING:woof:HttpConnection-13:B6EFCB90:WatchDog:"HttpConnection::run read 0 bytes, indicating peer shut down" Now if the connection closed before the transaction was complete that would be worth a WARNING, but these connections closing are normal and to be expected. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
