<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Bogdan,<br>
<br>
yes, we do use CDR via AAA.<br>
Here are used modparams:<br>
<br>
<font size="1" face="Courier New, Courier, monospace">####
ACCounting module<br>
loadmodule "acc.so"<br>
modparam("acc", "early_media", 0)<br>
modparam("acc", "report_cancels", 0)<br>
modparam("acc", "detect_direction", 1)<br>
modparam("acc", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips")<br>
#modparam("acc", "db_table_missed_calls", "acc")<br>
modparam("acc", "service_type", 15)<br>
modparam("acc", "leg_fields", "db:
CALLER->Anum;CALLEE->Bnum;TYPE->leg_type;SRCIP->srcIP;DESTIP->destIP;DIRECTION->direction")<br>
<br>
</font>and we do receive CDR in mysql acc table<br>
</p>
<p>gdb returns<br>
<font size="1" face="Courier New, Courier, monospace">Core was
generated by `/usr/sbin/opensips -P /run/opensips/opensips.pid
-f /etc/opensips/opensips.cfg'.
<br>
Program terminated with signal SIGSEGV, Segmentation fault.
<br>
#0 0x0000000000000000 in ?? ()
<br>
(gdb) f 1
<br>
#1 0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized
out>, msg=<optimized out>, ctx=0x7f334fcc52c8) at
/build/opensips-3.4.2/modules/acc/acc.c:965
<br>
965 /build/opensips-3.4.2/modules/acc/acc.c: No such file or
directory.
<br>
(gdb) p proto
<br>
$1 = {init_prot = 0x0, create_aaa_message = 0x0,
destroy_aaa_message = 0x0, send_aaa_request = 0x0,
dictionary_find = 0x0, avp_add = 0x0, avp_get = 0x0}
</font><br>
<br>
<br>
BR<br>
Simon<br>
</p>
<div class="moz-cite-prefix">Bogdan-Andrei Iancu je 08.12.2023 ob
16:38 napisal:<br>
</div>
<blockquote type="cite"
cite="mid:4fd3bcf4-a3b4-4cf3-8664-eb002090c486@opensips.org">It
looks you are using (or trying to) the CDR support via AAA.
<br>
<br>
Could you share the full modparam's for the acc module and the
radius/diameter support?
<br>
<br>
Also, in using GDB, just do:
<br>
f 1
<br>
p proto
<br>
<br>
Regards,
<br>
<br>
Bogdan-Andrei Iancu
<br>
<br>
OpenSIPS Founder and Developer
<br>
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a>
<br>
<br>
On 08.12.2023 16:30, Neven Grzancic wrote:
<br>
<blockquote type="cite">Hi Bogdan,
<br>
<br>
good hit on the apport service - thanks!
<br>
<br>
here's the trace we get from one such crash:
<br>
<br>
[New LWP 1130]
<br>
[Thread debugging using libthread_db enabled]
<br>
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
<br>
Core was generated by `/usr/sbin/opensips -P
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
<br>
Program terminated with signal SIGSEGV, Segmentation fault.
<br>
#0 0x0000000000000000 in ?? ()
<br>
(gdb) bt full
<br>
#0 0x0000000000000000 in ?? ()
<br>
No symbol table info available.
<br>
#1 0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized
out>, msg=<optimized out>, ctx=0x7f334fcc52c8)
<br>
at /build/opensips-3.4.2/modules/acc/acc.c:965
<br>
i = <optimized out>
<br>
j = <optimized out>
<br>
ret = 6
<br>
res = -1
<br>
nr_leg_vals = <optimized out>
<br>
start_time = {tv_sec = 1702044564, tv_usec = 417047}
<br>
core_s = {s = 0x7f33705e9878 "\006", len = 101}
<br>
leg_s = {s = 0x0, len = <optimized out>}
<br>
extra_s = {s = 0x0, len = <optimized out>}
<br>
send = 0x0
<br>
offset = <optimized out>
<br>
av_type = 32563
<br>
r_stat = <optimized out>
<br>
locked = 0
<br>
duration = 1338791072
<br>
ms_duration = 0
<br>
extra = <optimized out>
<br>
error = <optimized out>
<br>
__FUNCTION__ = "acc_aaa_cdrs"
<br>
#2 0x00007f334e078ade in acc_cdr_cb (t=0x0, type=5,
ps=0x7ffdb12e09e0)
<br>
at /build/opensips-3.4.2/modules/acc/acc_logic.c:986
<br>
ctx = 0x7f334fcc52c8
<br>
dlg = 0x7f334fcc54e0
<br>
__FUNCTION__ = "acc_cdr_cb"
<br>
[...]
<br>
<br>
<br>
On 08.12.23 15:16, Bogdan-Andrei Iancu wrote:
<br>
<blockquote type="cite">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.
<br>
<br>
Regards,
<br>
<br>
Bogdan-Andrei Iancu
<br>
<br>
OpenSIPS Founder and Developer
<br>
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a>
<br>
<br>
On 08.12.2023 16:13, Simon Gajski wrote:
<br>
<blockquote type="cite">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>
<blockquote type="cite">Hi Simon,
<br>
<br>
Maybe you have some apport service running on the machine,
moving the core file.
<br>
<br>
Regards,
<br>
<br>
Bogdan-Andrei Iancu
<br>
<br>
OpenSIPS Founder and Developer
<br>
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a>
<br>
<br>
On 08.12.2023 13:35, Neven Grzancic wrote:
<br>
<blockquote type="cite">Dear Bogdan,
<br>
<br>
we tried following
<a class="moz-txt-link-freetext" href="https://opensips.org/Documentation/TroubleShooting-Crash">https://opensips.org/Documentation/TroubleShooting-Crash</a>
and trying different things, and even though the syslog
shows that the core file was dumped:
<br>
<br>
Dec 8 12:25:13 sbc2 /usr/sbin/opensips[4363]:
CRITICAL:core:sig_usr: segfault in process pid: 4363,
id: 7
<br>
Dec 8 12:25:13 sbc2 kernel: [ 3394.269733]
opensips[4363]: segfault at 0 ip 0000000000000000 sp
00007ffdc458f6a8 error 14 in
opensips[55816fbd0000+1f000]
<br>
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)
<br>
Dec 8 12:25:18 sbc2 /usr/sbin/opensips[4356]:
INFO:core:handle_sigs: child process 4363 exited by a
signal 11
<br>
Dec 8 12:25:18 sbc2 /usr/sbin/opensips[4356]:
INFO:core:handle_sigs: core was generated
<br>
Dec 8 12:25:18 sbc2 /usr/sbin/opensips[4356]:
INFO:core:handle_sigs: terminating due to SIGCHLD
<br>
Dec 8 12:25:18 sbc2 /usr/sbin/opensips[4359]:
INFO:core:sig_usr: signal 15 received
<br>
Dec 8 12:25:18 sbc2 /usr/sbin/opensips[4360]:
INFO:core:sig_usr: signal 15 received
<br>
<br>
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...
<br>
<br>
On 08.12.23 12:26, Simon Gajski wrote:
<br>
<blockquote type="cite">
<br>
<br>
<br>
-------- Posredovano sporočilo --------
<br>
Zadeva: Re: [OpenSIPS-Users] opensips is
restarting after call is finished
<br>
Datum: Thu, 7 Dec 2023 17:52:37 +0200
<br>
Od: Bogdan-Andrei Iancu
<a class="moz-txt-link-rfc2396E" href="mailto:bogdan@opensips.org"><bogdan@opensips.org></a>
<br>
Za: Simon Gajski <a class="moz-txt-link-rfc2396E" href="mailto:simon@softnet.si"><simon@softnet.si></a>,
OpenSIPS users mailling list
<a class="moz-txt-link-rfc2396E" href="mailto:users@lists.opensips.org"><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]:
INFO:core:handle_sigs: child process 28495 exited by a
signal 11
<br>
Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]:
INFO:core:handle_sigs: core was generated
<br>
Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]:
INFO:core:handle_sigs: terminating due to SIGCHLD
<br>
<br>
Or shortly, you opensips just crashed :). So see
<a class="moz-txt-link-freetext" href="https://opensips.org/Documentation/TroubleShooting-Crash">https://opensips.org/Documentation/TroubleShooting-Crash</a>
for how to report further.
<br>
<br>
Regards,
<br>
<br>
Bogdan-Andrei Iancu
<br>
<br>
OpenSIPS Founder and Developer
<br>
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a>
<br>
<br>
On 07.12.2023 17:17, Simon Gajski via Users wrote:
<br>
<blockquote type="cite">
<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 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, bellow action happens.
<br>
<br>
We had same problem with opensips 3.2 and Ubuntu 20.
So we did upgrade to latest stable release, and it
is the same.
<br>
<br>
Is this opensips script configuration issue or a
bug? And how 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 class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
</body>
</html>