[OpenSIPS-Users] Fwd: opensips is restarting after call is finished

Fri Dec 8 14:25:57 UTC 2023

I am.very interested in this case.

On Fri, Dec 8, 2023, 9:20 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Simon, I do not need the corefile, usually it is huge - as per web
> instructions (see the prev link), extract the backtrace (using gdb) and
> share it with me.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> On 08.12.2023 16:13, Simon Gajski wrote:
> > Hi Bogdan
> >
> > you were right
> > we have the core file now
> >
> > Please let me know where to send it (gzipped is approx 2MB)
> >
> >
> > BR
> > Simon
> >
> > Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
> >> Hi Simon,
> >>
> >> Maybe you have some apport service running on the machine, moving the
> >> core file.
> >>
> >> Regards,
> >>
> >> Bogdan-Andrei Iancu
> >>
> >> OpenSIPS Founder and Developer
> >>   https://www.opensips-solutions.com
> >>   https://www.siphub.com
> >>
> >> On 08.12.2023 13:35, Neven Grzancic wrote:
> >>> Dear Bogdan,
> >>>
> >>> we tried following
> >>> https://opensips.org/Documentation/TroubleShooting-Crash and trying
> >>> different things, and even though the syslog shows that the core
> >>> file was dumped:
> >>>
> >>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]:
> >>> CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
> >>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: segfault
> >>> at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 in
> >>> opensips[55816fbd0000+1f000]
> >>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400
> >>> [Warning] Aborted connection 400 to db: 'opensips' user: 'opensips'
> >>> host: 'localhost' (Got an error reading communication packets)
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]:
> >>> INFO:core:handle_sigs: child process 4363 exited by a signal 11
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]:
> >>> INFO:core:handle_sigs: core was generated
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]:
> >>> INFO:core:handle_sigs: terminating due to SIGCHLD
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: INFO:core:sig_usr:
> >>> signal 15 received
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: INFO:core:sig_usr:
> >>> signal 15 received
> >>>
> >>> the core does not get generated, or at least not in the directory
> >>> provided via options at runtime (-w /tmp). The issue is always
> >>> repeatable (the daemon crashes after every finished call), if there
> >>> are more active calls at the moment of the crash, whose calls remain
> >>> active and proceed normally until termination (which again causes a
> >>> crash). We also tried enabling debug mode, but in that case the
> >>> process does not start successfully and runs into a timeout. In any
> >>> case, any additional help or suggestion on how to successfully
> >>> generate the core dump would be much appreciated, as we seem to have
> >>> ran into a wall here...
> >>>
> >>> On 08.12.23 12:26, Simon Gajski wrote:
> >>>>
> >>>>
> >>>>
> >>>> -------- Posredovano sporočilo --------
> >>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after call
> >>>> is finished
> >>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
> >>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
> >>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users mailling
> >>>> list <users at lists.opensips.org>
> >>>>
> >>>>
> >>>>
> >>>> Hi Simon,
> >>>>
> >>>> Well, the log is very self explanatory:
> >>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]:
> >>>> INFO:core:handle_sigs: child process 28495 exited by a signal 11
> >>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]:
> >>>> INFO:core:handle_sigs: core was generated
> >>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]:
> >>>> INFO:core:handle_sigs: terminating due to SIGCHLD
> >>>>
> >>>> Or shortly, you opensips just crashed :). So see
> >>>> https://opensips.org/Documentation/TroubleShooting-Crash for how to
> >>>> report further.
> >>>>
> >>>> Regards,
> >>>>
> >>>> Bogdan-Andrei Iancu
> >>>>
> >>>> OpenSIPS Founder and Developer
> >>>>    https://www.opensips-solutions.com
> >>>>    https://www.siphub.com
> >>>>
> >>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
> >>>>>
> >>>>> Hi
> >>>>>
> >>>>> we are running opensips 3.4.2
> >>>>> on Ubuntu 22.04.3 LTS
> >>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0
> >>>>> git-master-74075f63
> >>>>>
> >>>>> Opensips acts as SBC with RTP engine enabled.
> >>>>>
> >>>>> Calls are working fine, however after each call is finished,
> >>>>> bellow action happens.
> >>>>>
> >>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we did
> >>>>> upgrade to latest stable release, and it is the same.
> >>>>>
> >>>>> Is this opensips script configuration issue or a bug? And how
> >>>>> could I fix it?
> >>>>>
> >>>>> [....]
> >>>>>
> >>>>> Thanks for all tips.
> >>>>>
> >>>>> BR
> >>>>> Simon
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Users mailing list
> >>>>> Users at lists.opensips.org
> >>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >>>>
> >>>
> >>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231208/119f07e4/attachment-0001.html>