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