I think in your case stunnel is working properly but there is definitely something deeper going on here. On the surface this appears to be an SSL issue or possibly a database corruption issue. It would probably help if you posted a snip of /var/log/sipxpbx/sipxconfig.log where the actual error is occurring.
Josh Patten Brazos County Network Engineer 979.361.4676 From: [email protected] [mailto:[email protected]] On Behalf Of Henry Dogger Sent: Thursday, May 26, 2011 5:32 AM To: Discussion list for users of sipXecs software Subject: [sipx-users] stunnel problems Hi all, I found a problem on the list a year ago concerning stunnel. I found a post of Josh Patten: http://list.sipfoundry.org/archive/sipx-users/msg25011.html And currently I see the following errors: http://pastebin.com/Tn4XT36z I think I encounter a similar problem since I see on my primary server that stunnel is failing: [telecats@sipxecs1 tmp]$ ps aux | grep stunnel telecats 8433 0.0 0.0 61172 756 pts/1 S+ 12:25 0:00 grep stunnel 500 8678 0.0 0.0 47216 3352 ? Sl May17 0:13 /usr/sbin/stunnel /tmp/stunnel-config.8574.0 500 8679 0.0 0.0 46380 432 ? S May17 0:00 /usr/sbin/stunnel /tmp/stunnel-config.8574.0 500 8680 0.0 0.0 46380 128 ? S May17 0:00 /usr/sbin/stunnel /tmp/stunnel-config.8574.0 500 8681 0.0 0.0 46380 128 ? S May17 0:00 /usr/sbin/stunnel /tmp/stunnel-config.8574.0 500 8682 0.0 0.0 46380 128 ? S May17 0:00 /usr/sbin/stunnel /tmp/stunnel-config.8574.0 500 8683 0.0 0.0 46380 128 ? S May17 0:00 /usr/sbin/stunnel /tmp/stunnel-config.8574.0 500 12648 0.0 0.0 0 0 ? Z May25 0:00 [stunnel] <defunct> Secondary seems running fine: [telecats@sipxecs2 ~]$ ps aux | grep stunnel 500 4762 0.0 0.0 43080 3356 ? Sl May25 0:01 /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config 500 4777 0.0 0.0 42220 876 ? S May25 0:00 /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config 500 4778 0.0 0.0 42220 628 ? S May25 0:00 /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config 500 4779 0.0 0.0 42220 628 ? S May25 0:00 /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config 500 4780 0.0 0.0 42220 628 ? S May25 0:00 /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config 500 4781 0.0 0.0 42220 628 ? S May25 0:00 /usr/sbin/stunnel /etc/sipxpbx/sipxcallresolver-agent-config telecats 19952 0.0 0.0 61200 772 pts/0 S+ 12:25 0:00 grep stunnel The primary server seems to choke on “sending profiles” sipxproc won’t respond afterwards, I don’t see any services status information in web ui and also no registrations… Any idea how to fix? I installed on CentOS 5.6 sipXecs 4.2.1 from RPM, so am using stunnel: 4.28-5.2 I noticed the fips = no was in the stunnel config file…. Kind regards, Henry Dogger Telecats BV
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
