Hi, Upgrading stunnel did help for my processes count, but today sipxecs crashed again... It is now in a state where all xml/rpc calls seem to time-out...
"2011-06-01T12:04:01.052000Z":3427:JAVA:INFO:caiwsipxecs-test1.voip.offi ce.caiw.intern:P1-17:00000000:XmlRpcClientInterceptor:"XML/RPC ZoneAdminRpc.generateDns with [caiwsipxecs-test1.voip..., caiwsipxecs-test1.voip...] on https://caiwsipxecs-test1.voip.office.caiw.intern:8092/RPC2"; "2011-06-01T12:04:06.002000Z":3428:JAVA:ERR:caiwsipxecs-test1.voip.offic e.caiw.intern:background:00000000:XmlRpcClientInterceptor:"Timeout in XML/RPC call" I checked the link, and it indeed time-out in my browser, where normally I believe I should get a reply of a certificate? I also checked netstat: tcp 100 0 192.168.39.2:8092 192.168.39.2:53983 ESTABLISHED tcp 100 0 192.168.39.2:8092 192.168.39.2:37342 ESTABLISHED tcp 100 0 192.168.39.2:8092 192.168.39.2:53981 ESTABLISHED tcp 100 0 192.168.39.2:8092 192.168.39.2:55004 ESTABLISHED tcp 100 0 192.168.39.2:8092 192.168.39.2:53979 ESTABLISHED tcp 106 0 192.168.39.2:8092 192.168.39.2:55003 CLOSE_WAIT tcp 100 0 192.168.39.2:8092 192.168.39.2:54999 ESTABLISHED And noticed this line is stuck on state CLOSE_WAIT... it never changes... Send profiles, registrations page, every XML/RPC call times out. Sipxproc also does not respond... When I restarted sipXecs, these ports where (obviously) all gone [root@caiwsipxecs-test1 sipxpbx]# netstat -lan | grep 8092 tcp 0 0 0.0.0.0:8092 0.0.0.0:* LISTEN I see no weird errors, in sipxstunnel or sipxcallresolver, other then the cdr unique error I see every time I do a send profiles. Any other ideas what this problem could be? Henry -----Original Message----- From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Henry Dogger Sent: maandag 30 mei 2011 9:47 To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] weird log problem on snapshots Hi, Cypromis proposed to update stunnel to a newer version (the one used in sipx 4.4.0) I tried this and installed stunnel.x86_64 4.33-1. I rebooted, and after reboot I noticed only one stunnel process was running instead of 6. I still see some errors on boot of stunnel, but after a send profiles my server seems to stay alive :) I will monitor to see if this update of stunnel fixes my problem, and will report back with my findings. Henry _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
