<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We’re in the process of migrating to our new build on Debian 8, but this will take a few more weeks to complete. This gives me some confidence that we’ve made
the right decision.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Shaun<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org]
<b>On Behalf Of </b>Michael Jerris<br>
<b>Sent:</b> 20 September 2015 01:46<br>
<b>To:</b> FreeSWITCH Users Help<br>
<b>Subject:</b> Re: [Freeswitch-users] FreeSWITCH - Segmentation fault in libcrypto.so.1.0.0<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There are known issues with OpenSSL on <span style="font-size:10.0pt">Ubuntu 12.04 LTS being broken by some patches that Ubuntu broke in that library. It is STRONGLY recommend not to use 12.04, as it is known to be broken, specifically
a history of causing segfaults in OpenSSL. We reccomend using Debian 8, it will be the most stable platform is it is our primary development platform, so it will get the best testing. </span><br>
<br>
On Saturday, September 19, 2015, Shaun Stokes <<a href="mailto:shaun.stokes@itec-support.co.uk">shaun.stokes@itec-support.co.uk</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Hi,<br>
<br>
We use FreeSWITCH in a production enviroment and this morning experienced an outage caused by a segmentation fault (error 4 in libcrypto.so.1.0.0). Based on this error I'm geussing this is linked to the OpenSSL module? We have TLS disabled in all of our SIP
profiles, how can we stop FreeSWITCH from using libcrypto, or is anyone able to advise on another method to fix this?<br>
<br>
Our system:<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Ubuntu 12.04 LTS<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">FreeSwitch 1.4.15<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">PostgreSQL 9.3.6<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">OpenSSL 1.0.1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><br>
Please see below for a copy of the kernal log, I've replaced server names and IP addresses with xxxx for security purposes.<br>
<br>
Sep 19 00:21:13 xxxx kernel: [1276167.422451] show_signal_msg: 57 callbacks suppressed<br>
Sep 19 00:21:13 xxxx kernel: [1276167.422456] freeswitch[53622]: segfault at 7f4590c6b000 ip 00007f45908fb6e3 sp 00007f453f50dfc0 error 4 in libcrypto.so.1.0.0[7f4590890000+1b2000]<br>
<br>
This isn't the first time we've seen this error, but it has been many months since this last occured. The last time we expeirenced this type of segmentation fault (libcrypto) in FreeSWITCH we installed all available updates. On this occasion the segmentation
fault happened overnight when we only have the occasional call. This happened approx 37 seconds after the last call had ended (see below).<br>
<br>
d89ff492-5e5b-11e5-90c5-d74017d9130d 2015-09-19 00:20:36.601890 [NOTICE] sofia.c:952 Hangup sofia/internal/3303@xxxx [CS_EXECUTE] [NORMAL_CLEARING]<br>
<br>
da61a97e-5e5b-11e5-90f6-d74017d9130d 2015-09-19 00:20:36.621841 [NOTICE] switch_ivr_bridge.c:754 Hangup sofia/external/+xxxx@xxxx [CS_EXCHANGE_MEDIA] [NORMAL_CLEARING]<br>
<br>
There doesn't seem to be any connection with the time or any events on the server, there were no authentication attempts or logs that we can find which could be linked to segmentation fault.<br>
<br>
Hope someone here can advise.<br>
<br>
Many Thanks,<br>
Shaun<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><br>
______________________________________________________________________<br>
This message has been checked for all known viruses by MessageLabs Virus Scanning Service.<br>
______________________________________________________________________<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
______________________________________________________________________<br>
This message has been checked for all known viruses by MessageLabs Virus Scanning Service.<br>
______________________________________________________________________<o:p></o:p></p>
</div>
<br clear="both">
______________________________________________________________________<BR>
This message has been checked for all known viruses by MessageLabs Virus Scanning Service.<BR>
______________________________________________________________________<BR>
</body>
</html>