On Fri, 2008-08-29 at 00:39 +0100, Brian WG wrote: > Thanks for your reply. Please find attached the results of top > commands immediately after the crash took place. The screenshots > reflect "top"sults of both servers. I do notice a lot of swaps. It > also appeared that sipproxy and sipauthproxy is using 97-98% cpu.
Ouch! A screenshot, with colors dark read on dark grey, is really hard to read. Can't you copy-and-paste this as text? I see that the registrars, though they're not taking a large percentage of the CPU currently, have a large accumulated CPU time and a large memory consumption. But what is in the logs? Have you taken a sipx-snapshot? Are you running with the logging at debug level (for the proxy, authproxy, and registrar)? > The system has two server and was installed by a Pingtel engineer. If you have the commercial product, why don't you contact Pingtel support? They can spend a lot more effort helping you than we can. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
