<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""></div><div class=""></div><div class=""><div class="">Hi Daniel,</div><div class=""><br class=""></div><div class="">Thanks for the response.</div><div class=""><br class=""></div><div class="">Reviewing the logs again, the first occurrence was on 25Sep, after upgrading to 4.1.6+precise on 24Sep.</div><div class=""><br class=""></div><div class="">Previous upgrades were to:</div><div class=""><span style="color: rgb(51, 51, 51); line-height: 20px; background-color: rgb(255, 255, 255);" class="">4.1.5+precise<span class="Apple-tab-span" style="white-space: pre;"> </span>18Aug</span></div><div class=""><span style="color: rgb(51, 51, 51); line-height: 20px; background-color: rgb(255, 255, 255);" class="">4.1.4+precise<span class="Apple-tab-span" style="white-space: pre;"> </span>June</span></div><div class=""><br class=""></div><div class="">Traffic patterns are fairly uniform over that period.</div><div class=""><br class=""></div><div class="">I've installed the nightly (4.1.6+0~20141004025841.74+precise) and we'll see how that goes until the next release.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Dave</div><div class=""><br class=""></div><div class=""><br class=""></div></div><blockquote type="cite" class=""><div class=""><div class="">Date: Thu, 02 Oct 2014 09:02:14 +0200</div><div class="">From: Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" class="">miconda@gmail.com</a>></div><div class="">To: "Kamailio (SER) - Users Mailing List"</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><<a href="mailto:sr-users@lists.sip-router.org" class="">sr-users@lists.sip-router.org</a>></div><div class="">Subject: Re: [SR-Users] Segfault in 4.1.6</div><div class="">Message-ID: <<a href="mailto:542CF876.6060900@gmail.com" class="">542CF876.6060900@gmail.com</a>></div><div class="">Content-Type: text/plain; charset=utf-8; format=flowed</div><div class=""><br class=""></div><div class="">Hello,</div><div class=""><br class=""></div><div class="">I see it crashed in dialog, it was a fix for it after 4.1.6 for the </div><div class="">cleanup timer procedure, affecting some particular cases with dialog </div><div class="">states (e.g., dialogs not answered even after many minutes since </div><div class="">creation). It was there before 4.1.6 (most probably from 4.1.0), not </div><div class="">introduced by that version. What you were using before 4.1.6?</div><div class=""><br class=""></div><div class="">You can get latest version from branch 4.1 either via GIT or via debian </div><div class="">nightly builds of 4.1 (if using debian).</div><div class=""><br class=""></div><div class="">Otherwise, yes, a coredump with a gdb backtrace will be very helpful.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Daniel</div><div class=""><br class=""></div><div class="">On 02/10/14 08:31, David Wilson wrote:</div><div class="">> Hi all,</div><div class="">></div><div class="">> I?ve had Kamailio running nicely for nearly a year, but have hit a segfault twice since upgrading to 4.1.6 earlier this week.</div><div class="">></div><div class="">> The log shows:</div><div class="">></div><div class="">> Oct 2 11:28:03 localhost /usr/sbin/kamailio[1222]: : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 23</div><div class="">> Oct 2 11:28:03 localhost kernel: [11259.904645] kamailio[1206]: segfault at 58 ip 00007fa56fba0f86 sp 00007fffea594ca0 error 4 in dialog.so[7fa56fb63000+54000]</div><div class="">> Oct 2 11:28:03 localhost /usr/sbin/kamailio[1175]: ALERT: <core> [main.c:777]: handle_sigs(): child process 1206 exited by a signal 11</div><div class="">> Oct 2 11:28:03 localhost /usr/sbin/kamailio[1175]: ALERT: <core> [main.c:780]: handle_sigs(): core was not generated</div><div class="">> Oct 2 11:28:03 localhost /usr/sbin/kamailio[1175]: INFO: <core> [main.c:792]: handle_sigs(): INFO: terminating due to SIGCHLD</div><div class="">> Oct 2 11:28:03 localhost /usr/sbin/kamailio[1220]: INFO: <core> [main.c:843]: sig_usr(): INFO: signal 15 received</div><div class="">> ?.</div><div class="">></div><div class="">> The first two lines above seem to be the important parts. Nothing was logged for about 10s prior to this extract. An earlier instance of the issue showed almost the same details:</div><div class="">></div><div class="">> Oct 1 20:39:12 localhost /usr/sbin/kamailio[1219]: : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 23</div><div class="">> Oct 1 20:39:12 localhost kernel: [554502.639227] kamailio[1207]: segfault at 58 ip 00007fd62c5c6f86 sp 00007fffd77c9890 error 4 in dialog.so[7fd62c589000+54000]</div><div class="">></div><div class="">> I?m trying to catch a core next time it occurs, no core is available yet.</div><div class="">></div><div class="">> Is this a new issue in 4.1.6?</div><div class="">> Any suggestions about the likely cause?</div><div class="">></div><div class="">> Cheers,</div><div class="">> Dave.</div><div class="">></div></div></blockquote></body></html>