Hi all!
Our Kamailio (3.1.4) crashed when modifying the username-Part of a Request URI using:
$rU = $(rU{s.strip,6});
Initial Request URI: /sbin/kamailio[40658]: NOTICE: <script>: [ INVITE ] Got new Packet to sip:123456:pass@sip.custom.com
The config-script now removed the first 6 chars from the username part and would replace them in one of the following lines, but Kamailio had problems here:
/sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: NOTICE: <script>: Strip from Head: Request Username: <null> // $rU /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: ERROR: <core> [action.c:801]: ERROR: do_action: bad uri sip::passsip.custom.com, dropping packet
Is there maybe a error when modifying a uri with password this way? Do we have to change this?
Ultimately Kamailio crashed: /sbin/kamailio[40658]: ERROR: <core> [action.c:1513]: run action error at: :0 /sbin/kamailio[40658]: ERROR: pv [pv_core.c:1761]: do action failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:358]: setting pvar failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (319,10-319,34) /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI
Like 5000 lines more of /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Due to rerouting internal and trying to remove more parts of the request Uri using $rU = $(rU{s.strip,6});
Which then concluded to the following: /sbin/kamailio[40656]: ALERT: <core> [main.c:741]: child process 40660 exited by a signal 11 /sbin/kamailio[40656]: ALERT: <core> [main.c:744]: core was generated /sbin/kamailio[40656]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD /sbin/kamailio[40659]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40682]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40677]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40676]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40678]: INFO: <core> [main.c:807]: INFO: signal 15 received [...]
I will try to recreate this using the new version (4.1.6) on monday.
Kind regards
Timo Klecker
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", <value to set it to>);
If I recall correctly, our issue was that we could not pass in a variable, an avp, or a concatenated string with kamailios rewrite uri function:
http://www.kamailio.org/wiki/cookbooks/4.2.x/core#rewriteuri
The function I just gave above however may be fixed now, it was a year or 2 ago we wrote the perl script.
I hope that helps.
All the best.
Will Ferrer
Switchsoft Inc
On Fri, Nov 28, 2014 at 10:05 AM, Timo Klecker klecker@decoit.de wrote:
Hi all!
Our Kamailio (3.1.4) crashed when modifying the username-Part of a Request URI using:
$rU = $(rU{s.strip,6});
Initial Request URI: /sbin/kamailio[40658]: NOTICE: <script>: [ INVITE ] Got new Packet to sip:123456:pass@sip.custom.com
The config-script now removed the first 6 chars from the username part and would replace them in one of the following lines, but Kamailio had problems here:
/sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: NOTICE: <script>: Strip from Head: Request Username: <null> // $rU /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: ERROR: <core> [action.c:801]: ERROR: do_action: bad uri sip::passsip.custom.com, dropping packet
Is there maybe a error when modifying a uri with password this way? Do we have to change this?
Ultimately Kamailio crashed: /sbin/kamailio[40658]: ERROR: <core> [action.c:1513]: run action error at: :0 /sbin/kamailio[40658]: ERROR: pv [pv_core.c:1761]: do action failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:358]: setting pvar failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (319,10-319,34) /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI
Like 5000 lines more of /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Due to rerouting internal and trying to remove more parts of the request Uri using $rU = $(rU{s.strip,6});
Which then concluded to the following: /sbin/kamailio[40656]: ALERT: <core> [main.c:741]: child process 40660 exited by a signal 11 /sbin/kamailio[40656]: ALERT: <core> [main.c:744]: core was generated /sbin/kamailio[40656]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD /sbin/kamailio[40659]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40682]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40677]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40676]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40678]: INFO: <core> [main.c:807]: INFO: signal 15 received [...]
I will try to recreate this using the new version (4.1.6) on monday.
Kind regards
Timo Klecker
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
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 parameter.
Cheers, Daniel
On 01/12/14 23:20, Will Ferrer wrote:
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", <value to set it to>);
If I recall correctly, our issue was that we could not pass in a variable, an avp, or a concatenated string with kamailios rewrite uri function:
http://www.kamailio.org/wiki/cookbooks/4.2.x/core#rewriteuri
The function I just gave above however may be fixed now, it was a year or 2 ago we wrote the perl script.
I hope that helps.
All the best.
Will Ferrer
Switchsoft Inc
On Fri, Nov 28, 2014 at 10:05 AM, Timo Klecker <klecker@decoit.de mailto:klecker@decoit.de> wrote:
Hi all! Our Kamailio (3.1.4) crashed when modifying the username-Part of a Request URI using: $rU = $(rU{s.strip,6}); Initial Request URI: /sbin/kamailio[40658]: NOTICE: <script>: [ INVITE ] Got new Packet to sip:123456:pass@sip.custom.com <mailto:sip%3A123456%3Apass@sip.custom.com> The config-script now removed the first 6 chars from the username part and would replace them in one of the following lines, but Kamailio had problems here: /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: NOTICE: <script>: Strip from Head: Request Username: <null> // $rU /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: ERROR: <core> [action.c:801]: ERROR: do_action: bad uri <sip::passsip.custom.com <http://passsip.custom.com>>, dropping packet Is there maybe a error when modifying a uri with password this way? Do we have to change this? Ultimately Kamailio crashed: /sbin/kamailio[40658]: ERROR: <core> [action.c:1513]: run action error at: :0 /sbin/kamailio[40658]: ERROR: pv [pv_core.c:1761]: do action failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:358]: setting pvar failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (319,10-319,34) /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Like 5000 lines more of /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Due to rerouting internal and trying to remove more parts of the request Uri using $rU = $(rU{s.strip,6}); Which then concluded to the following: /sbin/kamailio[40656]: ALERT: <core> [main.c:741]: child process 40660 exited by a signal 11 /sbin/kamailio[40656]: ALERT: <core> [main.c:744]: core was generated /sbin/kamailio[40656]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD /sbin/kamailio[40659]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40682]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40677]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40676]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40678]: INFO: <core> [main.c:807]: INFO: signal 15 received [...] I will try to recreate this using the new version (4.1.6) on monday. Kind regards Timo Klecker _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
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
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 Request URI using:
$rU = $(rU{s.strip,6});
Initial Request URI: /sbin/kamailio[40658]: NOTICE: <script>: [ INVITE ] Got new Packet to sip:123456:pass@sip.custom.com
The config-script now removed the first 6 chars from the username part and would replace them in one of the following lines, but Kamailio had problems here:
/sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: NOTICE: <script>: Strip from Head: Request Username: <null> // $rU /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: ERROR: <core> [action.c:801]: ERROR: do_action: bad uri sip::passsip.custom.com, dropping packet
Is there maybe a error when modifying a uri with password this way? Do we have to change this?
Ultimately Kamailio crashed: /sbin/kamailio[40658]: ERROR: <core> [action.c:1513]: run action error at: :0 /sbin/kamailio[40658]: ERROR: pv [pv_core.c:1761]: do action failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:358]: setting pvar failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (319,10-319,34) /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI
Like 5000 lines more of /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Due to rerouting internal and trying to remove more parts of the request Uri using $rU = $(rU{s.strip,6});
Which then concluded to the following: /sbin/kamailio[40656]: ALERT: <core> [main.c:741]: child process 40660 exited by a signal 11 /sbin/kamailio[40656]: ALERT: <core> [main.c:744]: core was generated /sbin/kamailio[40656]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD /sbin/kamailio[40659]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40682]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40677]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40676]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40678]: INFO: <core> [main.c:807]: INFO: signal 15 received [...]
I will try to recreate this using the new version (4.1.6) on monday.
Kind regards
Timo Klecker
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
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.
10.10.207.20 is a server running the attached Kamailio configuration.
10.10.210.71 is a server running sipsak, sending the attached invite.
sipsak -s sip:10.10.207.20:5060 -f invite.txt
The crash seems to occur due to a missing exit of the configuration loop. So to get rid of the crash I would break the loop if $rU equals null after modification in MODIFY_NUMBER.
The issue now simplifies to:
You cannot empty $rU when a password is set, because the URI becomes invalid due to missing @: bad uri sip::pass10.10.207.20
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: ru initial: sip:123456:pass@10.10.207.20
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: rU set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:236]: pv_get_ruri(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: ru set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:805]: do_action(): ERROR: do_action: bad uri sip::pass10.10.207.20, dropping packet
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:1553]: do_action(): run action error at: :0
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:2080]: pv_set_ruri_user(): do action failed
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:363]: lval_pvar_assign(): setting pvar failed
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:416]: lval_assign(): assignment failed at pos: (49,11-49,21)
This loops:
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: rU set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:236]: pv_get_ruri(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: ru set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:356]: lval_pvar_assign(): non existing right pvar
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:805]: do_action(): ERROR: do_action: bad uri sip::pass10.10.207.20, dropping packet
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:1553]: do_action(): run action error at: :0
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:2059]: pv_set_ruri_user(): do action failed)
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:363]: lval_pvar_assign(): setting pvar failed
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:416]: lval_assign(): assignment failed at pos: (46,11-46,26)
Kind regards
Timo Klecker
Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Daniel-Constantin Mierla Gesendet: Montag, 1. Dezember 2014 23:35 An: Kamailio (SER) - Users Mailing List Betreff: Re: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 Request URI using:
$rU = $(rU{s.strip,6});
Initial Request URI: /sbin/kamailio[40658]: NOTICE: <script>: [ INVITE ] Got new Packet to sip:123456:pass@sip.custom.com
The config-script now removed the first 6 chars from the username part and would replace them in one of the following lines, but Kamailio had problems here:
/sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: NOTICE: <script>: Strip from Head: Request Username: <null> // $rU /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: ERROR: <core> [action.c:801]: ERROR: do_action: bad uri sip::passsip.custom.com sip::passsip.custom.com, dropping packet
Is there maybe a error when modifying a uri with password this way? Do we have to change this?
Ultimately Kamailio crashed: /sbin/kamailio[40658]: ERROR: <core> [action.c:1513]: run action error at: :0 /sbin/kamailio[40658]: ERROR: pv [pv_core.c:1761]: do action failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:358]: setting pvar failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (319,10-319,34) /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI
Like 5000 lines more of /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Due to rerouting internal and trying to remove more parts of the request Uri using $rU = $(rU{s.strip,6});
Which then concluded to the following: /sbin/kamailio[40656]: ALERT: <core> [main.c:741]: child process 40660 exited by a signal 11 /sbin/kamailio[40656]: ALERT: <core> [main.c:744]: core was generated /sbin/kamailio[40656]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD /sbin/kamailio[40659]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40682]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40677]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40676]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40678]: INFO: <core> [main.c:807]: INFO: signal 15 received [...]
I will try to recreate this using the new version (4.1.6) on monday.
Kind regards
Timo Klecker
_______________________________________________ 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
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 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.
10.10.207.20 is a server running the attached Kamailio configuration.
10.10.210.71 is a server running sipsak, sending the attached invite.
sipsak -s sip:10.10.207.20:5060 -f invite.txt
The crash seems to occur due to a missing exit of the configuration loop. So to get rid of the crash I would break the loop if $rU equals null after modification in MODIFY_NUMBER.
The issue now simplifies to:
You cannot empty $rU when a password is set, because the URI becomes invalid due to missing @: bad uri sip::pass10.10.207.20
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: ru initial: sip:123456:pass@10.10.207.20
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: rU set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:236]: pv_get_ruri(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: ru set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:805]: do_action(): ERROR: do_action: bad uri sip::pass10.10.207.20, dropping packet
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:1553]: do_action(): run action error at: :0
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:2080]: pv_set_ruri_user(): do action failed
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:363]: lval_pvar_assign(): setting pvar failed
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:416]: lval_assign(): assignment failed at pos: (49,11-49,21)
This loops:
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: rU set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:236]: pv_get_ruri(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: ru set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:356]: lval_pvar_assign(): non existing right pvar
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:805]: do_action(): ERROR: do_action: bad uri sip::pass10.10.207.20, dropping packet
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:1553]: do_action(): run action error at: :0
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:2059]: pv_set_ruri_user(): do action failed)
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:363]: lval_pvar_assign(): setting pvar failed
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:416]: lval_assign(): assignment failed at pos: (46,11-46,26)
Kind regards
Timo Klecker
*Von:*sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] *Im Auftrag von *Daniel-Constantin Mierla *Gesendet:* Montag, 1. Dezember 2014 23:35 *An:* Kamailio (SER) - Users Mailing List *Betreff:* Re: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 Request URI using: $rU = $(rU{s.strip,6}); Initial Request URI: /sbin/kamailio[40658]: NOTICE: <script>: [ INVITE ] Got new Packet to sip:123456:pass@sip.custom.com The config-script now removed the first 6 chars from the username part and would replace them in one of the following lines, but Kamailio had problems here: /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: NOTICE: <script>: Strip from Head: Request Username: <null> // $rU /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: ERROR: <core> [action.c:801]: ERROR: do_action: bad uri <sip::passsip.custom.com> <sip::passsip.custom.com>, dropping packet Is there maybe a error when modifying a uri with password this way? Do we have to change this? Ultimately Kamailio crashed: /sbin/kamailio[40658]: ERROR: <core> [action.c:1513]: run action error at: :0 /sbin/kamailio[40658]: ERROR: pv [pv_core.c:1761]: do action failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:358]: setting pvar failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (319,10-319,34) /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Like 5000 lines more of /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Due to rerouting internal and trying to remove more parts of the request Uri using $rU = $(rU{s.strip,6}); Which then concluded to the following: /sbin/kamailio[40656]: ALERT: <core> [main.c:741]: child process 40660 exited by a signal 11 /sbin/kamailio[40656]: ALERT: <core> [main.c:744]: core was generated /sbin/kamailio[40656]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD /sbin/kamailio[40659]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40682]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40677]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40676]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40678]: INFO: <core> [main.c:807]: INFO: signal 15 received [...] I will try to recreate this using the new version (4.1.6) on monday. Kind regards Timo Klecker _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users-- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda
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: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up!
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script
But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email.
Kind regards,
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 15:18 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 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.
10.10.207.20 is a server running the attached Kamailio configuration.
10.10.210.71 is a server running sipsak, sending the attached invite.
sipsak -s sip:10.10.207.20:5060 -f invite.txt
The crash seems to occur due to a missing exit of the configuration loop. So to get rid of the crash I would break the loop if $rU equals null after modification in MODIFY_NUMBER.
The issue now simplifies to:
You cannot empty $rU when a password is set, because the URI becomes invalid due to missing @: bad uri sip::pass10.10.207.20 sip::pass10.10.207.20
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: ru initial: sip:123456:pass@10.10.207.20
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: rU set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:236]: pv_get_ruri(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: ru set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:805]: do_action(): ERROR: do_action: bad uri sip::pass10.10.207.20 sip::pass10.10.207.20, dropping packet
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:1553]: do_action(): run action error at: :0
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:2080]: pv_set_ruri_user(): do action failed
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:363]: lval_pvar_assign(): setting pvar failed
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:416]: lval_assign(): assignment failed at pos: (49,11-49,21)
This loops:
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: rU set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:236]: pv_get_ruri(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: NOTICE: <script>: ru set to: <null>
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:356]: lval_pvar_assign(): non existing right pvar
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:805]: do_action(): ERROR: do_action: bad uri sip::pass10.10.207.20 sip::pass10.10.207.20, dropping packet
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:1553]: do_action(): run action error at: :0
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: pv [pv_core.c:2059]: pv_set_ruri_user(): do action failed)
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:363]: lval_pvar_assign(): setting pvar failed
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [lvalue.c:416]: lval_assign(): assignment failed at pos: (46,11-46,26)
Kind regards
Timo Klecker
Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Daniel-Constantin Mierla Gesendet: Montag, 1. Dezember 2014 23:35 An: Kamailio (SER) - Users Mailing List Betreff: Re: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 Request URI using:
$rU = $(rU{s.strip,6});
Initial Request URI: /sbin/kamailio[40658]: NOTICE: <script>: [ INVITE ] Got new Packet to sip:123456:pass@sip.custom.com
The config-script now removed the first 6 chars from the username part and would replace them in one of the following lines, but Kamailio had problems here:
/sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: NOTICE: <script>: Strip from Head: Request Username: <null> // $rU /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: ERROR: <core> [action.c:801]: ERROR: do_action: bad uri sip::passsip.custom.com sip::passsip.custom.com, dropping packet
Is there maybe a error when modifying a uri with password this way? Do we have to change this?
Ultimately Kamailio crashed: /sbin/kamailio[40658]: ERROR: <core> [action.c:1513]: run action error at: :0 /sbin/kamailio[40658]: ERROR: pv [pv_core.c:1761]: do action failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:358]: setting pvar failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (319,10-319,34) /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI
Like 5000 lines more of /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Due to rerouting internal and trying to remove more parts of the request Uri using $rU = $(rU{s.strip,6});
Which then concluded to the following: /sbin/kamailio[40656]: ALERT: <core> [main.c:741]: child process 40660 exited by a signal 11 /sbin/kamailio[40656]: ALERT: <core> [main.c:744]: core was generated /sbin/kamailio[40656]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD /sbin/kamailio[40659]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40682]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40677]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40676]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40678]: INFO: <core> [main.c:807]: INFO: signal 15 received [...]
I will try to recreate this using the new version (4.1.6) on monday.
Kind regards
Timo Klecker
_______________________________________________ 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
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 testing config, though. The last line in log with testing config is:
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up!
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script
But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email.
Kind regards,
Timo Klecker
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:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 16:16 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 testing config, though. The last line in log with testing config is:
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up!
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script
But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email.
Kind regards,
Timo Klecker
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 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:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:16 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 testing config, though. The last line in log with testing config is: Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up! Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email. Kind regards, Timo Klecker-- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda
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, please tell me how to get the "bt full" string out of this interactive gdb shell.
I will provide you with the output of gdb itself, I missed that in the last mail.
Greetings
Timo
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 16:47 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 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:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 16:16 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 testing config, though. The last line in log with testing config is:
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up!
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script
But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email.
Kind regards,
Timo Klecker
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/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, please tell me how to get the “bt full” string out of this interactive gdb shell.
I will provide you with the output of gdb itself, I missed that in the last mail.
Greetings
Timo
*Von:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:47 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 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:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:16 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri 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 testing config, though. The last line in log with testing config is: Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up! Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email. Kind regards, Timo Klecker -- Daniel-Constantin Mierla http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda-- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda
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 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/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, please tell me how to get the “bt full” string out of this interactive gdb shell.
I will provide you with the output of gdb itself, I missed that in the last mail.
Greetings
Timo
*Von:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:47 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 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:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:16 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri 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 testing config, though. The last line in log with testing config is: Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up! Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email. Kind regards, Timo Klecker -- Daniel-Constantin Mierla http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda-- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
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-Constantin Mierla wrote:
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 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/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, please tell me how to get the “bt full” string out of this interactive gdb shell.
I will provide you with the output of gdb itself, I missed that in the last mail.
Greetings
Timo
*Von:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:47 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 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:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:16 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri 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 testing config, though. The last line in log with testing config is: Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up! Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email. Kind regards, Timo Klecker -- Daniel-Constantin Mierla http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda-- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
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, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 010d57
compiled on 17:35:09 Dec 4 2014 with gcc 4.4.6
Compiled yesterday because I needed the right debug-rpm and had to recompile.
Kind regards
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Freitag, 5. Dezember 2014 17:40 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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-Constantin Mierla wrote:
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 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/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, please tell me how to get the "bt full" string out of this interactive gdb shell.
I will provide you with the output of gdb itself, I missed that in the last mail.
Greetings
Timo
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 16:47 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 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:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 16:16 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 testing config, though. The last line in log with testing config is:
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up!
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script
But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email.
Kind regards,
Timo Klecker
Hello,
according to the trace, the crash trace is:
#0 0x00007f544c119801 in _IO_default_xsputn_internal () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f544c0e93a9 in vfprintf () from /lib64/libc.so.6 No symbol table info available. #2 0x00007f544c0f4368 in fprintf () from /lib64/libc.so.6 No symbol table info available. #3 0x00007f544c189bc8 in __vsyslog_chk () from /lib64/libc.so.6 No symbol table info available. #4 0x00007f544c18a210 in syslog () from /lib64/libc.so.6 No symbol table info available. #5 0x00007f54479f2341 in pv_get_ruri_attr (msg=0x7f544bed9c30, param=0x7f544beb2a50, res=0x7fffe1341e88) at pv_core.c:304 __FUNCTION__ = "pv_get_ruri_attr"
Line 304 in pv_core is: LM_ERR("failed to parse the R-URI\n");
Which is a bit strange as a point of crash. I will try to see if I can spot something else...
I noticed that you seem to have somehow kind of infinite loop with calling route blocks - like calling route B from A and route A from B...
Cheers, Daniel
On 05/12/14 17:45, Timo Klecker wrote:
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, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 010d57
compiled on 17:35:09 Dec 4 2014 with gcc 4.4.6
Compiled yesterday because I needed the right debug-rpm and had to recompile.
Kind regards
Timo Klecker
*Von:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Gesendet:* Freitag, 5. Dezember 2014 17:40 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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-Constantin Mierla wrote:
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 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/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, please tell me how to get the “bt full” string out of this interactive gdb shell. I will provide you with the output of gdb itself, I missed that in the last mail. Greetings Timo *Von:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:47 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri 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 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:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:16 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri 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 testing config, though. The last line in log with testing config is: Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up! Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email. Kind regards, Timo Klecker
http://www.linkedin.com/in/miconda
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});
xlog("L_NOTICE", "rU set to: $rU\n");
xlog("L_NOTICE", "ru set to: $ru\n");
$rU = '123' + $rU;
xlog("L_NOTICE", "rU set to: $rU\n");
xlog("L_NOTICE", "ru set to: $ru\n");
route(START_ROUTING);
}
Due to the parsing Error in $rU the break of the loop is never triggered. So you are right, there is an infinite loop. When breaking this loop, no crash happens.
But still one problem remains:
Request Uri: sip:123456:pass@sip.custom.com
$rU = $(rU{s.strip,6});
Afterwards the Request Uri is set to
sip::passsip.custom.com
There is an @ missing.
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:805]: do_action(): ERROR: do_action: bad uri sip::pass10.10.207.20, dropping packet
And $rU and $ru are null due to parsing-errors.
Kind regards
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Freitag, 5. Dezember 2014 18:04 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
Hello,
according to the trace, the crash trace is:
#0 0x00007f544c119801 in _IO_default_xsputn_internal () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f544c0e93a9 in vfprintf () from /lib64/libc.so.6 No symbol table info available. #2 0x00007f544c0f4368 in fprintf () from /lib64/libc.so.6 No symbol table info available. #3 0x00007f544c189bc8 in __vsyslog_chk () from /lib64/libc.so.6 No symbol table info available. #4 0x00007f544c18a210 in syslog () from /lib64/libc.so.6 No symbol table info available. #5 0x00007f54479f2341 in pv_get_ruri_attr (msg=0x7f544bed9c30, param=0x7f544beb2a50, res=0x7fffe1341e88) at pv_core.c:304 __FUNCTION__ = "pv_get_ruri_attr"
Line 304 in pv_core is: LM_ERR("failed to parse the R-URI\n");
Which is a bit strange as a point of crash. I will try to see if I can spot something else...
I noticed that you seem to have somehow kind of infinite loop with calling route blocks - like calling route B from A and route A from B...
Cheers, Daniel
On 05/12/14 17:45, Timo Klecker wrote:
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, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 010d57
compiled on 17:35:09 Dec 4 2014 with gcc 4.4.6
Compiled yesterday because I needed the right debug-rpm and had to recompile.
Kind regards
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Freitag, 5. Dezember 2014 17:40 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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-Constantin Mierla wrote:
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 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/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, please tell me how to get the "bt full" string out of this interactive gdb shell.
I will provide you with the output of gdb itself, I missed that in the last mail.
Greetings
Timo
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 16:47 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 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:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 16:16 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 testing config, though. The last line in log with testing config is:
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up!
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script
But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email.
Kind regards,
Timo Klecker
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 kamailio can handle cases when the r-uri is broken (could be an incoming r-uri).
Cheers, Daniel
On 08/12/14 13:50, Timo Klecker wrote:
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}); xlog("L_NOTICE", "rU set to: $rU\n"); xlog("L_NOTICE", "ru set to: $ru\n"); $rU = '123' + $rU; xlog("L_NOTICE", "rU set to: $rU\n"); xlog("L_NOTICE", "ru set to: $ru\n"); route(START_ROUTING);}
Due to the parsing Error in $rU the break of the loop is never triggered. So you are right, there is an infinite loop. When breaking this loop, no crash happens.
But still one problem remains:
Request Uri: sip:123456:pass@sip.custom.com
$rU = $(rU{s.strip,6});
Afterwards the Request Uri is set to
sip::passsip.custom.com
There is an @ missing.
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:805]: do_action(): ERROR: do_action: bad uri sip::pass10.10.207.20, dropping packet
And $rU and $ru are null due to parsing-errors.
Kind regards
Timo Klecker
*Von:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Gesendet:* Freitag, 5. Dezember 2014 18:04 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
Hello,
according to the trace, the crash trace is:
#0 0x00007f544c119801 in _IO_default_xsputn_internal () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f544c0e93a9 in vfprintf () from /lib64/libc.so.6 No symbol table info available. #2 0x00007f544c0f4368 in fprintf () from /lib64/libc.so.6 No symbol table info available. #3 0x00007f544c189bc8 in __vsyslog_chk () from /lib64/libc.so.6 No symbol table info available. #4 0x00007f544c18a210 in syslog () from /lib64/libc.so.6 No symbol table info available. #5 0x00007f54479f2341 in pv_get_ruri_attr (msg=0x7f544bed9c30, param=0x7f544beb2a50, res=0x7fffe1341e88) at pv_core.c:304 __FUNCTION__ = "pv_get_ruri_attr"
Line 304 in pv_core is: LM_ERR("failed to parse the R-URI\n");
Which is a bit strange as a point of crash. I will try to see if I can spot something else...
I noticed that you seem to have somehow kind of infinite loop with calling route blocks - like calling route B from A and route A from B...
Cheers, Daniel
On 05/12/14 17:45, Timo Klecker wrote:
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, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 010d57 compiled on 17:35:09 Dec 4 2014 with gcc 4.4.6 Compiled yesterday because I needed the right debug-rpm and had to recompile. Kind regards Timo Klecker *Von:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Gesendet:* Freitag, 5. Dezember 2014 17:40 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri 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-Constantin Mierla wrote: 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 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/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, please tell me how to get the “bt full” string out of this interactive gdb shell. I will provide you with the output of gdb itself, I missed that in the last mail. Greetings Timo *Von:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:47 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri 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 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:miconda@gmail.com] *Gesendet:* Donnerstag, 4. Dezember 2014 16:16 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri 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 testing config, though. The last line in log with testing config is: Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up! Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email. Kind regards, Timo Klecker-- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda
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:
grep pv_get_ruri_attr /var/log/kamailio.log | wc -l
75472 with default settings
75436 with shared memory set to 64
75440 with shared memory set to 256
But in top I saw a massive increase in memory usage.
I don't know if this is any helpful for you.
Kind regards
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@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 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 kamailio can handle cases when the r-uri is broken (could be an incoming r-uri).
Cheers, Daniel
On 08/12/14 13:50, Timo Klecker wrote:
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});
xlog("L_NOTICE", "rU set to: $rU\n");
xlog("L_NOTICE", "ru set to: $ru\n");
$rU = '123' + $rU;
xlog("L_NOTICE", "rU set to: $rU\n");
xlog("L_NOTICE", "ru set to: $ru\n");
route(START_ROUTING);
}
Due to the parsing Error in $rU the break of the loop is never triggered. So you are right, there is an infinite loop. When breaking this loop, no crash happens.
But still one problem remains:
Request Uri: sip:123456:pass@sip.custom.com
$rU = $(rU{s.strip,6});
Afterwards the Request Uri is set to
sip::passsip.custom.com
There is an @ missing.
Dec 4 13:27:50 /sbin/kamailio[8043]: ERROR: <core> [action.c:805]: do_action(): ERROR: do_action: bad uri sip::pass10.10.207.20, dropping packet
And $rU and $ru are null due to parsing-errors.
Kind regards
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Freitag, 5. Dezember 2014 18:04 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
Hello,
according to the trace, the crash trace is:
#0 0x00007f544c119801 in _IO_default_xsputn_internal () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f544c0e93a9 in vfprintf () from /lib64/libc.so.6 No symbol table info available. #2 0x00007f544c0f4368 in fprintf () from /lib64/libc.so.6 No symbol table info available. #3 0x00007f544c189bc8 in __vsyslog_chk () from /lib64/libc.so.6 No symbol table info available. #4 0x00007f544c18a210 in syslog () from /lib64/libc.so.6 No symbol table info available. #5 0x00007f54479f2341 in pv_get_ruri_attr (msg=0x7f544bed9c30, param=0x7f544beb2a50, res=0x7fffe1341e88) at pv_core.c:304 __FUNCTION__ = "pv_get_ruri_attr"
Line 304 in pv_core is: LM_ERR("failed to parse the R-URI\n");
Which is a bit strange as a point of crash. I will try to see if I can spot something else...
I noticed that you seem to have somehow kind of infinite loop with calling route blocks - like calling route B from A and route A from B...
Cheers, Daniel
On 05/12/14 17:45, Timo Klecker wrote:
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, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 010d57
compiled on 17:35:09 Dec 4 2014 with gcc 4.4.6
Compiled yesterday because I needed the right debug-rpm and had to recompile.
Kind regards
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Freitag, 5. Dezember 2014 17:40 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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-Constantin Mierla wrote:
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 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/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, please tell me how to get the "bt full" string out of this interactive gdb shell.
I will provide you with the output of gdb itself, I missed that in the last mail.
Greetings
Timo
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 16:47 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 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:miconda@gmail.com] Gesendet: Donnerstag, 4. Dezember 2014 16:16 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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 testing config, though. The last line in log with testing config is:
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: ERROR: <core> [action.c:1572]: run_actions(): WARNING: too many recursive routing table lookups (101) giving up!
Dec 4 13:28:06 lvm-centos-kamailio1 /sbin/kamailio[8045]: WARNING: <core> [receive.c:214]: receive_msg(): WARNING: receive_msg: error while trying script
But I have 2 cores, each 52M in size from production config. I will bzip them and send them via email.
Kind regards,
Timo Klecker
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:
grep pv_get_ruri_attr /var/log/kamailio.log | wc -l
75472 with default settings
75436 with shared memory set to 64
75440 with shared memory set to 256
But in top I saw a massive increase in memory usage.
I don’t know if this is any helpful for you.
It might be that the OS kills the process due to too much memory usage. Can you check again the logs and see what was the signal that killed the process?
Btw, have you tried with latest git branch, after I did the patch for fixing empty username?
Cheers, Daniel
Hi Daniel,
The child process is terminated by signal 11 (SIGSEGV).
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: <core> [main.c:777]: handle_sigs(): child process 12003 exited by a signal 11
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: <core> [main.c:780]: handle_sigs(): core was generated
Dec 8 16:41:25 /sbin/kamailio[12000]: INFO: <core> [main.c:792]: handle_sigs(): INFO: terminating due to SIGCHLD
Maybe not relevant but the process 12003 that is killed has last logged a line to kamailio.log like 6000 lines above the SIGSEGV:
Dec 8 16:40:46 /sbin/kamailio[12003]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Have not yet tried the latest branch, will do so tomorrow.
Kind regards
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Dienstag, 9. Dezember 2014 12:46 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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:
grep pv_get_ruri_attr /var/log/kamailio.log | wc -l
75472 with default settings
75436 with shared memory set to 64
75440 with shared memory set to 256
But in top I saw a massive increase in memory usage.
I don't know if this is any helpful for you.
It might be that the OS kills the process due to too much memory usage. Can you check again the logs and see what was the signal that killed the process?
Btw, have you tried with latest git branch, after I did the patch for fixing empty username?
Cheers, Daniel
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,
The child process is terminated by signal 11 (SIGSEGV).
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: <core> [main.c:777]: handle_sigs(): child process 12003 exited by a signal 11
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: <core> [main.c:780]: handle_sigs(): core was generated
Dec 8 16:41:25 /sbin/kamailio[12000]: INFO: <core> [main.c:792]: handle_sigs(): INFO: terminating due to SIGCHLD
Maybe not relevant but the process 12003 that is killed has last logged a line to kamailio.log like 6000 lines above the SIGSEGV:
Dec 8 16:40:46 /sbin/kamailio[12003]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Have not yet tried the latest branch, will do so tomorrow.
Kind regards
Timo Klecker
*Von:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Gesendet:* Dienstag, 9. Dezember 2014 12:46 *An:* Timo Klecker; 'Kamailio (SER) - Users Mailing List' *Betreff:* Re: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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: >grep pv_get_ruri_attr /var/log/kamailio.log | wc -l 75472 with default settings 75436 with shared memory set to 64 75440 with shared memory set to 256 But in top I saw a massive increase in memory usage. I don’t know if this is any helpful for you.It might be that the OS kills the process due to too much memory usage. Can you check again the logs and see what was the signal that killed the process?
Btw, have you tried with latest git branch, after I did the patch for fixing empty username?
Cheers, Daniel
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda
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_rpc sqlops avpops siptrace snmpstats"
For your question regarding memory usage please see attached top-logfiles. Running with default settings and with -m 256.
If you need anything more, please do not hesitate to ask. I will now try the latest git-version of the 4.1.6 branch.
Kind regards Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Mittwoch, 10. Dezember 2014 11:33 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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,
The child process is terminated by signal 11 (SIGSEGV).
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: <core> [main.c:777]: handle_sigs(): child process 12003 exited by a signal 11
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: <core> [main.c:780]: handle_sigs(): core was generated
Dec 8 16:41:25 /sbin/kamailio[12000]: INFO: <core> [main.c:792]: handle_sigs(): INFO: terminating due to SIGCHLD
Maybe not relevant but the process 12003 that is killed has last logged a line to kamailio.log like 6000 lines above the SIGSEGV:
Dec 8 16:40:46 /sbin/kamailio[12003]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Have not yet tried the latest branch, will do so tomorrow.
Kind regards
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Dienstag, 9. Dezember 2014 12:46 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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:
grep pv_get_ruri_attr /var/log/kamailio.log | wc -l
75472 with default settings
75436 with shared memory set to 64
75440 with shared memory set to 256
But in top I saw a massive increase in memory usage.
I don't know if this is any helpful for you.
It might be that the OS kills the process due to too much memory usage. Can you check again the logs and see what was the signal that killed the process?
Btw, have you tried with latest git branch, after I did the patch for fixing empty username?
Cheers, Daniel
Hi Daniel,
I compiled the latest 4.1 branch and tested the same INVITE. It works. The loop ends after one loop and all goes well. The password is removed after clearing $rU and the request-uri is correct: sip:sip.custom.com so we are able to change the username part after clearing it.
Great, thank you.
Mit freundlichen Grüßen
Timo Klecker
Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Timo Klecker Gesendet: Mittwoch, 10. Dezember 2014 13:18 An: miconda@gmail.com; 'Kamailio (SER) - Users Mailing List' 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=/opt/kamailio group_include="standard mysql" include_modules="mi_fifo kex tmx pv siputils mi_rpc sqlops avpops siptrace snmpstats"
For your question regarding memory usage please see attached top-logfiles. Running with default settings and with m 256.
If you need anything more, please do not hesitate to ask. I will now try the latest git-version of the 4.1.6 branch.
Kind regards Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Mittwoch, 10. Dezember 2014 11:33 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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,
The child process is terminated by signal 11 (SIGSEGV).
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: <core> [main.c:777]: handle_sigs(): child process 12003 exited by a signal 11
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: <core> [main.c:780]: handle_sigs(): core was generated
Dec 8 16:41:25 /sbin/kamailio[12000]: INFO: <core> [main.c:792]: handle_sigs(): INFO: terminating due to SIGCHLD
Maybe not relevant but the process 12003 that is killed has last logged a line to kamailio.log like 6000 lines above the SIGSEGV:
Dec 8 16:40:46 /sbin/kamailio[12003]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI
Have not yet tried the latest branch, will do so tomorrow.
Kind regards
Timo Klecker
Von: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Gesendet: Dienstag, 9. Dezember 2014 12:46 An: Timo Klecker; 'Kamailio (SER) - Users Mailing List' Betreff: Re: AW: [SR-Users] Kamailio Crash when modifying username of Request Uri
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:
grep pv_get_ruri_attr /var/log/kamailio.log | wc -l
75472 with default settings
75436 with shared memory set to 64
75440 with shared memory set to 256
But in top I saw a massive increase in memory usage.
I dont know if this is any helpful for you.
It might be that the OS kills the process due to too much memory usage. Can you check again the logs and see what was the signal that killed the process?
Btw, have you tried with latest git branch, after I did the patch for fixing empty username?
Cheers, Daniel
-
Daniel-Constantin Mierla -
Timo Klecker -
Will Ferrer