Hello,
I have opened an issue as suggested. However i have shared the backtrace
below too.
(gdb) bt
#0 0x in ?? ()
#1 0x7f23facf0f86 in run_create_callbacks (dlg=0x7f23ff849b18,
msg=0x7f24201ead80) at dlg_cb.c:230
#2 0x7f23fad0cedf in dlg_new_dialog (req=0x7f24201ead
Hello,
there are no backtraces in the email -- anyhow, open an issue on the bug
tracker and put the backtraces there:
- https://github.com/kamailio/kamailio/issues
Cheers,
Daniel
On 13/05/16 08:26, Sunil More wrote:
> Hello All,
>
> Kamailio instance just crashed with the following logs
>
>
Using the latest version in branch 4.1 makes sure you don't hit bug that
was fixed already. But it can be something new, which can be
troubleshooted properly when using latest version.
Cheers,
Daniel
On 08/09/15 22:44, SamyGo wrote:
> Thanks Daniel for pointing out, so if I upgrade my Kamailio it
Here is the output from gdp for fram 0 and 4.
(gdb) frame 0
#0 0x7f4d4dbc7ba9 in destroy_dlg_callbacks_list
(cb=0x353a6d6f) at dlg_cb.c:77
77 cb_t->callback_param_free(cb_t->param);
(gdb) list
72
73 while(cb) {
74 cb_t =
Thanks Daniel for pointing out, so if I upgrade my Kamailio it should all
go away , right. Will do a version upgrade and check similar calls.
I've seen very similar crashes EOF on 11, EOF of 16 etc etc in few other
situations as well, while at once such occasion it was an invalid kamctl
command an
Hello,
looks like there were updates to dialog modules in 4.1 after 4.1.4. The
code lines do not match the back trace.
You should upgrade to latest version in 4.1 branch -- there is no change
that you have to do in kamailio.cfg or database.
Meanwhile, we can see the relevant pieces of code from
Hi Daniel,
Thanks a ton for replying, please see the attached full trace.
Please note the Public IPs have been masked.
Best Regards,
Sammy
On Tue, Sep 8, 2015 at 3:01 PM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> can you give the output of 'bt full' in gdb to see where it actually
> crashed
Hello,
can you give the output of 'bt full' in gdb to see where it actually
crashed?
Cheers,
Daniel
On 08/09/15 20:20, SamyGo wrote:
> Hi,
>
> I'm randomly getting crash in my Kamailio with an error in log files
> like this:
>
> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 19
> ALE
You have to upgrade to 4.0.7 as it replaced 4.0.6 in 4.0.x series. It
could be that the backtrace will still be relevant.
It is useful to know the parameters for registrar and usrloc modules.
Cheers,
Daniel
On 16/06/15 18:45, Marc Soda wrote:
> Unfortunately, the best I can do is this:
>
> Core
Unfortunately, the best I can do is this:
Core was generated by `/usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.'.
Program terminated with signal 11, Segmentation fault.
#0 0x7fa3e65a5f3b in ?? () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/usrloc.so
(gdb)
On 06/16/2015 12:04 PM, Marc Soda wrote:
Is it normal for Kamailio to segfault
No. :-) Can you provide a GDB backtrace?
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671
...@gmail.com]
Sent: Tuesday, May 12, 2015 2:45 PM
To: Péter Barabás; Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] kamailio crash periodically in timer handler
Hi Peter,
good you mentioned the the patch, overlooked it -- is it something that you
want to be pushed on main repository or
) - Users Mailing List
Subject: Re: [SR-Users] kamailio crash periodically in timer handler
Hi Peter,
good you mentioned the the patch, overlooked it -- is it something that you
want to be pushed on main repository or some customization good for your needs?
Somehow I didn't understand pro
:255]: send_notifies(): Dialog is NULL
>
> May 12 10:44:41 ctdsip3 /usr/local/sbin/kamailio[23218]: INFO: rls
> [resource_notify.c:123]: get_dialog_from_did(): record not found in
> hash_table [rlsubs_did]=
> Xrw7Za_5mqpNuFyGbEj_5w..;1ef4503f;2b499685060cb5fb6380a8dd7f172ad6-e6e3
>
s build with different paramters in
different OS?
Thank you in advance.
Péter
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Tuesday, April 28, 2015 2:28 PM
To: Péter Barabás; Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] kamailio crash periodically in timer han
>
>
>
> *From:*Daniel-Constantin Mierla [mailto:mico...@gmail.com]
> *Sent:* Tuesday, April 28, 2015 9:03 AM
> *To:* Péter Barabás; Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] kamailio crash periodically in timer handler
>
>
>
> Hello,
>
>
Hi,
here is the svn diff of ul_publish.c attached.
Péter
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Tuesday, April 28, 2015 9:03 AM
To: Péter Barabás; Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] kamailio crash periodically in timer handler
Hello,
On 27/04
Hello,
On 27/04/15 23:59, Péter Barabás wrote:
>
> Hi,
>
>
>
> you gave me an idea where to find the error.
>
> We modified the ul_publish.c source in order to achieve the following
> results:
>
> - when client sends a REGISTER, an implicit PUBLISH is called
> so in each registration, p
oun...@lists.sip-router.org] *On
> Behalf Of *Daniel-Constantin Mierla
> *Sent:* Thursday, April 23, 2015 5:07 PM
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] kamailio crash periodically in timer handler
>
>
>
> Hello,
>
> can you get from
-boun...@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Thursday, April 23, 2015 5:07 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] kamailio crash periodically in timer handler
Hello,
can you get from gdb the output of:
p *tl
Cheers,
Daniel
On 23/04/15 17:00, P
Hello,
can you get from gdb the output of:
p *tl
Cheers,
Daniel
On 23/04/15 17:00, Péter Barabás wrote:
>
> Hi,
>
>
>
> we have a serious problem with Kamailio v4.2.3, it crashes after some
> days. We have checked the core dump and the gdb output is the
> following for bt and full backtrace:
Hello,
can you try with latest version from branch master or 4.2? I pushed a
patch with a safety check earlier today.
Cheers,
Daniel
On 22/02/15 22:14, Daniel-Constantin Mierla wrote:
> Hello,
>
> I just tried with the same invite injected with protoshot and it works
> ok. The relevant snippet o
Hello,
I just tried with the same invite injected with protoshot and it works
ok. The relevant snippet of the config I used is:
$var(codecs)="G729,PCMA,GSM,iLBC,speex,telephone-event";
sdp_keep_codecs_by_name($var(codecs));
$du = "sip:127.0.0.1:9";
t_relay();
exit;
I could see that the sdp going
7;
Betreff: Re: [SR-Users] Kamailio Crash when modifying username of Request
Uri
Hi Daniel,
yes, stock Kamilio Version 4.1.6 downloaded from
http://www.kamailio.org/pub/kamailio/4.1.6/ then built into a custom RPM,
due to signing and changing of prefix.
Built with:
make prefix=/op
Hi Daniel,
yes, stock Kamilio Version 4.1.6 downloaded from
http://www.kamailio.org/pub/kamailio/4.1.6/ then built into a custom RPM,
due to signing and changing of prefix.
Built with:
make prefix=/opt/kamailio group_include="standard mysql"
include_modules="mi_fifo kex tmx pv siputils mi_
Hello,
you said you saw an increase in memory usage -- was system memory,
right? What was the value, did it exceed shared memory size?
Just to be clear, you run stock kamailio, no patches or other modules
developed in-house?
Cheers,
Daniel
On 09/12/14 16:36, Timo Klecker wrote:
>
> Hi Daniel,
>
Hi Daniel,
Thanks a lot, we will give it a try and let you know how it goes!
On Mon, Dec 8, 2014 at 6:52 AM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> the patch to fix this should be in master, 4.2 and 4.1 git branches.
>
> Thanks for helping to troubleshoot this. Let me know if all goes fi
Hi Daniel,
The child process is terminated by signal 11 (SIGSEGV).
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: [main.c:777]:
handle_sigs(): child process 12003 exited by a signal 11
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: [main.c:780]:
handle_sigs(): core was generated
Dec 8
Hello,
On 08/12/14 16:42, Timo Klecker wrote:
>
> Hi Daniel,
>
>
>
> I tried to increase shared memory by setting a parameter in kamctlrc:
>
> STARTOPTIONS="-m 64"
>
>
>
> When recreating the crash I counted pv_get_ruri_attr in the logfile
> just to see if the shared memory changed anything:
>
:mico...@gmail.com]
Gesendet: Montag, 8. Dezember 2014 16:25
An: Timo Klecker; 'Kamailio (SER) - Users Mailing List'
Betreff: Re: [SR-Users] Kamailio Crash when modifying username of Request
Uri
Hello,
I noticed that there was an issue with the result stored in r-uri and it
should be fixe
Hello,
I noticed that there was an issue with the result stored in r-uri and it
should be fixed in the latest git branches -- you can fetch them and
try, practically, if the resulting user is empty, then the password is
removed as well.
However, I wanted to hunt the real reason of the crash, as k
Hi Daniel,
in the configuration I sent last week is a very simplified version of our
loop:
route[START_ROUTING] {
if ($rU == "123") {
xlog("L_NOTICE", "123 reached\n");
exit;
}
route(MODIFY_NUMBER);
}
route[MODIFY_NUMBER] {
$rU = $(rU{s.strip,6});
Hello,
the patch to fix this should be in master, 4.2 and 4.1 git branches.
Thanks for helping to troubleshoot this. Let me know if all goes fine
after upgrading to the latest version of one of these git branches.
Cheers,
Daniel
On 24/11/14 16:15, Daniel-Constantin Mierla wrote:
> Hello,
>
> ba
Hello,
according to the trace, the crash trace is:
#0 0x7f544c119801 in _IO_default_xsputn_internal () from
/lib64/libc.so.6
No symbol table info available.
#1 0x7f544c0e93a9 in vfprintf () from /lib64/libc.so.6
No symbol table info available.
#2 0x7f544c0f4368 in fprintf () from /
Hi Daniel,
yes, Kamailio 4.1 using syslog:
log_facility=LOG_LOCAL4
# modules
loadmodule "xlog.so"
# kamailio -v
version: kamailio 4.1.6 (x86_64/linux) 010d57
flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, P
I looked at the last gdb trace you sent and the crash is inside syslog()
function, which prints a message with static text, if I matched it with
the right version of the sources.
Is the trace from running kamailio 4.1? What is the output of:
kamailio -v
Cheers,
Daniel
On 04/12/14 17:23, Daniel-
Btw, you need to install dbg symbols package, in case you installed from
some deb/rpm.
Daniel
On 04/12/14 17:22, Daniel-Constantin Mierla wrote:
> Hello,
>
> I need the output of the 'bt full' -- I guess it will require a few
> 'more' paginations, because it is printing the values for local
> var
Hello,
I need the output of the 'bt full' -- I guess it will require a few
'more' paginations, because it is printing the values for local
variables which are important to troubleshoot.
Cheers,
daniel
On 04/12/14 17:13, Timo Klecker wrote:
>
> Hi Daniel,
>
>
>
> gdb /path/to/kamailio /path/to/
Hi Daniel,
gdb /path/to/kamailio /path/to/corefile
sent me into interactive mode. Typing
bt full
now sent me into something like "more" so I had to copy everything by hand,
like 46k lines.
So I searched the web for a non interactive method and came up with this. If
it is not ok, plea
Hello,
wondering why not simply sending what I asked for, respectively output for:
gdb /path/to/kamailio /path/to/corefile
bt full
I guess I wanted to get some useful information out of those commands...
Cheers,
Daniel
On 04/12/14 16:41, Timo Klecker wrote:
>
> Hi Daniel,
>
>
>
> sorry for s
Hi Daniel,
sorry for sending the core files, I now sent the output of:
gdb --batch --quiet -ex "thread apply all bt full" -ex "quit" /sbin/kamailio
/core.8933
Hope this is what you are looking for.
Kind regards,
Timo
Von: Daniel-Constantin Mierla [mailto:mico...@gmail.co
Hello,
corefiles themselves are useless. I need the backtrace from them,
respectively the output of:
gdb /path/to/kamailio /path/to/corefile
bt full
Cheers,
Daniel
On 04/12/14 15:56, Timo Klecker wrote:
>
> Hello Daniel,
>
>
>
> yes, with the production config I still get a core, not with the
Hello Daniel,
yes, with the production config I still get a core, not with the testing
config, though. The last line in log with testing config is:
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR:
[action.c:1572]: run_actions(): WARNING: too many recursive routing table
lo
Hello,
do you still get a core file? The easiest to troubleshoot is to get the
backtrace from the core with gdb. Setting up a testbed requires more
resources, not trivial when out of the office.
Cheers,
Daniel
On 04/12/14 14:21, Timo Klecker wrote:
>
> Hi Daniel,
>
>
>
> I was able to recreate
Hi Daniel,
I was able to recreate the Issue with the newer version (4.1.6). Please find
attached Kamailio configuration and sip-invite. (Please change modules path
according to installation)
The attached Kamailio configuration is a (very) simplified configuration we
are running in production.
Hello,
not sure I got what you tried in the past, but updating the r-uri value
was for very long time (perhaps from like 2006) possible by assigning an
expression to $ru. like:
$ru = "sip:"+$var(user) + "@" + $var(domain);
rewrite_uri() function from core worked always with static value as
para
Hello,
the version is indeed very old -- however, you got a core dump,
according to the logs, maybe you can send over the backtrace to see
where it crashed.
Cheers,
Daniel
On 28/11/14 18:05, Timo Klecker wrote:
> Hi all!
>
> Our Kamailio (3.1.4) crashed when modifying the username-Part of a Requ
Hi Timo
We had some issues changing the $rU as well.
In the end we wrote a perl function to do it:
sub rewrite_uri {
my $m = shift;
my $uri = shift;
$m->rewrite_ruri($uri);
return -1;
}
Which we call like so:
perl_exec("rewrite_uri", );
If I recall correctly, our issue was that
Hello,
back on this after rather long delay due to some unexpected situations
in the past week ...
I got the bactrace from you and I noticed as well that the version you
run had the patch for shellshock backported.
Hopefully you still have a the core file and can send to me:
frame 24
set print
Hello,
in the syslog, did you get messages like:
BUG: qm_*: fragm. ... beginning overwritten
Can you send the output of 'bt full'?
Cheers,
Daniel
On 17/11/14 16:49, Kristian Kielhofner wrote:
> Hi Daniel,
>
> It has happened at least twice, which isn't "often" considering the
> scale of our
Hi Daniel,
It has happened at least twice, which isn't "often" considering the
scale of our deployment but of course it's more often than we'd like
;).
Thanks for looking at this and please let me know what else you need!
On Mon, Nov 17, 2014 at 7:41 AM, Daniel-Constantin Mierla
wrote:
> He
Hello,
we did a patch to exec module, but iirc it was after 4.1.6, so it can be
something very old surfaced now.
I will look over it as I get a chance.
Does it happen often or it was just a case?
Cheers,
Daniel
On 15/11/14 23:55, Kristian Kielhofner wrote:
> version: kamailio 4.1.6 (x86_64/lin
Hi,
I do use SQL query in several places.
1. In the failure route to insert an event to the local DB where ACC
module does not do it. It is an insert to the local server DB and
seems to be very fast.
2. In the "event_route[*dialog:end*]" I call a procedure to delete a
row based on the callid as
Hello,
do you call any sql query in failure routes?
I want to see of worth looking at if the query is too slow for the
transaction to stay in memory after there is a final response to it.
Cheers,
Daniel
On 16/01/14 11:51, Uri Shacked wrote:
Daniel hi,
I attached the following file:
1."bt
Hello,
the backtrace shows a crash in tm module, not sqlops.
Can you tell which of the log files correspond to the instance that
produced the core file from where you took the back trace you attached?
Can you give the backtraces from all cores? You say there were 3
crashes. It is important t
Previously you said 3.2.0, but anyhow there are new releases in the
3.3.x series as well -- just upgrade to the latest 3.3.x, config file
and database are the same. Just deploy new binaries and restart.
Cheers,
Daniel
On 06/01/14 15:27, Uri Shacked wrote:
I am using 3.3.2 a91b2b-dirty
On Su
I am using 3.3.2 a91b2b-dirty
On Sun, Jan 5, 2014 at 2:19 PM, Uri Shacked wrote:
> Hi
>
> kamailio version 3.2.0
> 16M configured has private memory
> and 4G as shared memory.
> using sqlops to query the DB.
> the DB was down and kamailio crashed after some time with the following
> log under
>
Hello,
can you upgrade to latest 3.2.x? Because there were many fixes since
first release in that series (3.2.0).
If the issue persists, would be good to get a backtrace.
Not using sql_result_free() should not be a problem.
Cheers,
Daniel
On 05/01/14 13:30, Uri Shacked wrote:
And one more
And one more thing
I am not using "sql_result_free(result)"
Is it related to the problem? after all, there is no result if the DB was
down
On Sun, Jan 5, 2014 at 2:19 PM, Uri Shacked wrote:
> Hi
>
> kamailio version 3.2.0
> 16M configured has private memory
> and 4G as shared memory.
>
On 5/15/13 9:06 AM, kiran bhosale wrote:
On 05/15/2013 12:14 PM, Daniel-Constantin Mierla wrote:
[...]
we did that as well but we get these backtrace "No symbol
table info available " errors when we tried to debug the core file.
our requirement is simple . we have not used any DB
On 05/15/2013 12:14 PM, Daniel-Constantin Mierla wrote:
Hello,
On 5/15/13 6:43 AM, kiran bhosale wrote:
Hi
we have developed the custom module where in we have created
shared memory area which is not used by any other module or
process and we locked it using locks as recommended.
Hello,
On 5/15/13 6:43 AM, kiran bhosale wrote:
Hi
we have developed the custom module where in we have created
shared memory area which is not used by any other module or
process and we locked it using locks as recommended. but because
of locks the kamailio is getting crashed e
]
*Enviado el:* domingo, 25 de noviembre de 2012 18:02
*Para:* Ricardo Martinez
*CC:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
*Asunto:* Re: [SR-Users] Kamailio crash
Hello,
it seems that either callid parameter was not provided or couldn't be read
from t
icardo Martinez
*CC:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
Users Mailing List
*Asunto:* Re: [SR-Users] Kamailio crash
Hello,
ahh, my mistake - the frame number is 1, do:
frame 1
p callid
p *callid
Cheers,
Daniel
On 11/22/12 3:06 PM, Ricardo Martinez wrote:
Hi Dani
id
$2 = {s = 0x0, len = 0}
(gdb)
Thanks
Ricardo.-
*De:* Daniel-Constantin Mierla [mailto:mico...@gmail.com]
*Enviado el:* jueves, 22 de noviembre de 2012 11:57
*Para:* Ricardo Martinez
*CC:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
*Asunto:* Re:
mbre de 2012 19:01
*Para:* Ricardo Martinez
*CC:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
Users Mailing List
*Asunto:* Re: [SR-Users] Kamailio crash
On 11/21/12 10:40 PM, Ricardo Martinez wrote:
Yes.
Every 5 minutes we run a script to drop calls in state “3”.
Could
ilto:mico...@gmail.com]
*Enviado el:* miércoles, 21 de noviembre de 2012 19:01
*Para:* Ricardo Martinez
*CC:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
*Asunto:* Re: [SR-Users] Kamailio crash
On 11/21/12 10:40 PM, Ricardo Martinez wrote:
Yes.
Every 5 mi
r (SER) -
Users Mailing List
*CC:* Ricardo Martinez
*Asunto:* Re: [SR-Users] Kamailio crash
Hello,
do you have any external application sending MI commands to terminate
active calls?
Just checking to be sure it is not a core file overwrite situation.
Cheers,
Daniel
On 11/21/12 10:20 PM, R
(SER) -
Users Mailing List
*CC:* Ricardo Martinez
*Asunto:* Re: [SR-Users] Kamailio crash
Hello,
do you have any external application sending MI commands to terminate
active calls?
Just checking to be sure it is not a core file overwrite situation.
Cheers,
Daniel
On 11/21/12 10:20 PM, Ricardo
Hello,
do you have any external application sending MI commands to terminate
active calls?
Just checking to be sure it is not a core file overwrite situation.
Cheers,
Daniel
On 11/21/12 10:20 PM, Ricardo Martinez wrote:
Hello
In the last three days my kamailio process has crashed two tim
Hi Bou,
You are right, those columns were added this year and the schema was not
updated in the cassandra file also. I have committed the fix for that file.
I will investigate also why it crashed in this case, as it shouldn't
crash in any case.
Thanks and regards,
Anca Vamanu
On 08/24/2012
An update on this issue:
The schema that is used by the cassandra module seems to be missing a few
fields, the correct schema for location should be:
*
callid(string) cflags(int) contact(string) cseq(int) expires(timestamp)
flags(int) last_modified(int) methods(int) path
72 matches
Mail list logo
