<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 27, 2018 at 8:54 AM, mayamatakeshi <span dir="ltr"><<a href="mailto:mayamatakeshi@gmail.com" target="_blank">mayamatakeshi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div>I am seeing this issue with some of our FS deployments.</div><div>We use Debian 8 </div><div>with FS commit 5a4d2496f1b9256fe19cd90cc99ad8<wbr>780c7998bc.</div><div><br></div><div>However, this doesn't happen with an older FS machine using the same OS and FS commit.</div><div><br></div><div>Checking for differences between them, we ended up finding that</div><div>  ldd freeswitch</div><div>reports they differ here:</div><div><br></div><div>OK:</div><div> <span style="white-space:pre-wrap">  </span>libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/<wbr>libcurl-gnutls.so.4 </div><div><br></div><div>NG:</div><div> <span style="white-space:pre-wrap">        </span>libcurl.so.4 => /usr/lib/x86_64-linux-gnu/<wbr>libcurl.so.4 </div><div><br></div><div><br></div><div>I was wondering if this might be the cause of the issue and would like to test by forcing use of libcurl-gnutls on the NG machines but I am not sure if I can force FS build to use one instead of the other.</div><div><br></div><div>I can see both OK and NG machines have both </div><div>  libcurl-gnutls.so.4 </div><div>and</div><div>  libcurl.so.4</div><div>so I am not sure why they ended up with FS linked differently.</div><div><br></div><div>I searched the FS source code and eventually found that there is this flag HAVE_GNUTLS.</div><div><br></div><div>However, it seems this is not set as the code that would set it seems to be disabled (line commented with "#" in libs/iskemel/<a href="http://configure.ac" target="_blank">configure.ac</a>):</div><div><br></div><div><div>[root@lab002141 freeswitch]$ find . -type f|xargs grep -i HAVE_GNUTLS 2> /dev/null</div><div>./libs/win32/iksemel/config.h:<wbr>//#define HAVE_GNUTLS </div><div>./libs/iksemel/configure.ac:#<wbr>AX_PATH_LIBGNUTLS(,AC_DEFINE(<wbr>HAVE_GNUTLS,,"Use libgnutls"))</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:} // HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/src/stream.c:#<wbr>ifdef HAVE_GNUTLS</div><div>./libs/iksemel/configure:#AX_<wbr>PATH_LIBGNUTLS(,AC_DEFINE(<wbr>HAVE_GNUTLS,,"Use libgnutls"))</div><div>./libs/iksemel/tools/<wbr>iksroster.c:#ifndef HAVE_GNUTLS</div></div><div><br></div><div>So I am not sure why the build decided to link against <span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">libcurl-gnutls.so.4 on the OK machine.</span></div><div><span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Does anyone have some idea?</span></div><div><span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div></div></blockquote><div><br></div><div>I just had to do this before building FS:<br></div><div>  apt-get remove -y libcurl4-openssl-dev</div><div>  apt-get install -y libcurl4-gnutls-dev</div><div>  ldconfig</div><div><br></div><div>After that FS linked with libcurl4-gnutls</div><div><br></div><div>However, after updating the production FS server, memory behavior didn't change. So the issue is not related to libcurl.</div><div><br></div><div><br></div><div><br></div></div></div></div>