Hi Daniel, Thanks for the response.
Reviewing the logs again, the first occurrence was on 25Sep, after upgrading to 4.1.6+precise on 24Sep. Previous upgrades were to: 4.1.5+precise 18Aug 4.1.4+precise June Traffic patterns are fairly uniform over that period. I've installed the nightly (4.1.6+0~20141004025841.74+precise) and we'll see how that goes until the next release. Cheers, Dave > Date: Thu, 02 Oct 2014 09:02:14 +0200 > From: Daniel-Constantin Mierla <mico...@gmail.com> > To: "Kamailio (SER) - Users Mailing List" > <sr-users@lists.sip-router.org> > Subject: Re: [SR-Users] Segfault in 4.1.6 > Message-ID: <542cf876.6060...@gmail.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hello, > > I see it crashed in dialog, it was a fix for it after 4.1.6 for the > cleanup timer procedure, affecting some particular cases with dialog > states (e.g., dialogs not answered even after many minutes since > creation). It was there before 4.1.6 (most probably from 4.1.0), not > introduced by that version. What you were using before 4.1.6? > > You can get latest version from branch 4.1 either via GIT or via debian > nightly builds of 4.1 (if using debian). > > Otherwise, yes, a coredump with a gdb backtrace will be very helpful. > > Cheers, > Daniel > > On 02/10/14 08:31, David Wilson wrote: > > Hi all, > > > > 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. > > > > The log shows: > > > > Oct 2 11:28:03 localhost /usr/sbin/kamailio[1222]: : <core> > > [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 23 > > 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] > > 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 > > Oct 2 11:28:03 localhost /usr/sbin/kamailio[1175]: ALERT: <core> > > [main.c:780]: handle_sigs(): core was not generated > > Oct 2 11:28:03 localhost /usr/sbin/kamailio[1175]: INFO: <core> > > [main.c:792]: handle_sigs(): INFO: terminating due to SIGCHLD > > Oct 2 11:28:03 localhost /usr/sbin/kamailio[1220]: INFO: <core> > > [main.c:843]: sig_usr(): INFO: signal 15 received > > ?. > > > > 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: > > > > Oct 1 20:39:12 localhost /usr/sbin/kamailio[1219]: : <core> > > [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 23 > > 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] > > > > I?m trying to catch a core next time it occurs, no core is available yet. > > > > Is this a new issue in 4.1.6? > > Any suggestions about the likely cause? > > > > Cheers, > > Dave. > >
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
