Woof! After being left to idle overnight from yesterday's build (with only 2 phones registering). sipXproxy has started to misbehave. It appears to be leaking FD's:
"2008-11-05T17:48:15.099824Z":56059:SIP:ERR:woof:SipRouter-11:B6CFEB90:SipXProxy:"SipProtocolServerBase[SipTcpServer-3]::getClientForDestination creating TCP client failed" "2008-11-05T17:48:23.939439Z":56187:KERNEL:ERR:woof:SipRouter-11:B6CFEB90:SipXProxy:"OsServerTaskWaitable::_ pipe() returned 1006 -> 1005, which exceeds sFdLimit = 1004" [EMAIL PROTECTED] sipxpbx]$ lsof -p 19031 | tail -10 sipXproxy 19031 woof 993r FIFO 0,6 9630193 pipe sipXproxy 19031 woof 994w FIFO 0,6 9630193 pipe sipXproxy 19031 woof 995u IPv4 9631379 TCP woof.us.nortel.com:49054->woof.us.nortel.com:sip (ESTABLISHED) sipXproxy 19031 woof 997r FIFO 0,6 9631381 pipe sipXproxy 19031 woof 998w FIFO 0,6 9631381 pipe sipXproxy 19031 woof 999r FIFO 0,6 9631382 pipe sipXproxy 19031 woof 1000w FIFO 0,6 9631382 pipe sipXproxy 19031 woof 1001u IPv4 9631384 TCP woof.us.nortel.com:57429->woof.us.nortel.com:15060 (ESTABLISHED) sipXproxy 19031 woof 1002r FIFO 0,6 9631385 pipe sipXproxy 19031 woof 1003w FIFO 0,6 9631385 pipe --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
