[SR-Users] DRouting cause Kamailio 3.2 to stop

Fatima Chahrour~Vanrise Support fchahrour at vanrise.com
Thu Mar 1 09:05:32 CET 2012


I also tried : #gdb /usr/local/sbin/kamailio  /var/log/core.file
                         (gdb) bt

And got No Stack..

 

BR,

F.Chahrour

 

From: sr-users-bounces at lists.sip-router.org
[mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of Fatima
Chahrour~Vanrise Support
Sent: Wednesday, February 29, 2012 6:15 PM
To: 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List'
Cc: sr-users-bounces at lists.sip-router.org
Subject: Re: [SR-Users] DRouting cause Kamailio 3.2 to stop

 

Hi again,

 

I have read about core dump and most mentioned that I have to do a backtrace
to get the reason behind the crash. 

As a newbie in this field am not able to generate Where do I should stand
and reproduce the gdb command, all my trials resulted with 'No Stack' as
below!

 

I did the following:

 

debian:/usr/local/sbin/kamailio# gdb $kamailio_binary $core_file

GNU gdb 6.8-debian

Copyright (C) 2008 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.  Type "show copying"

and "show warranty" for details.

This GDB was configured as "i486-linux-gnu".

(gdb) bt full

No stack.

(gdb)

 

Where is my mistake?

 

Again if needed syslog output before Kamailio crash!

Feb 29 06:44:42 debian /usr/local/sbin/kamailio[4280]: INFO: usrloc
[hslot.c:53]: locks array size 512

Feb 29 06:44:42 debian /usr/local/sbin/kamailio[4280]: INFO: drouting
[drouting.c:272]: DRouting - initializing

Feb 29 06:44:42 debian /usr/local/sbin/kamailio[4280]: INFO: <core>
[udp_server.c:179]: INFO: udp_init: SO_RCVBUF is initially 111616

Feb 29 06:44:42 debian /usr/local/sbin/kamailio[4280]: INFO: <core>
[udp_server.c:230]: INFO: udp_init: SO_RCVBUF is finally 262142

Feb 29 06:44:42 debian /usr/local/sbin/kamailio[4280]: INFO: <core>
[udp_server.c:179]: INFO: udp_init: SO_RCVBUF is initially 111616

Feb 29 06:44:42 debian /usr/local/sbin/kamailio[4280]: INFO: <core>
[udp_server.c:230]: INFO: udp_init: SO_RCVBUF is finally 262142

Feb 29 06:44:42 debian /usr/local/sbin/kamailio[4294]: INFO: ctl
[io_listener.c:225]: io_listen_loop:  using epoll_lt io watch method
(config)

Feb 29 06:45:03 debian kernel: [17504.541952] kamailio[4296]: segfault at
bf7e3ee4 ip b6cc2c38 sp bf7e3e70 error 6 in drouting.so[b6cb7000+1d000]

Feb 29 06:45:03 debian /usr/local/sbin/kamailio[4304]: : <core>
[pass_fd.c:293]: ERROR: receive_fd: EOF on 5

Feb 29 06:45:03 debian /usr/local/sbin/kamailio[4280]: ALERT: <core>
[main.c:751]: child process 4296 exited by a signal 11

Feb 29 06:45:03 debian /usr/local/sbin/kamailio[4280]: ALERT: <core>
[main.c:754]: core was generated

Feb 29 06:45:03 debian /usr/local/sbin/kamailio[4280]: INFO: <core>
[main.c:766]: INFO: terminating due to SIGCHLD

Feb 29 06:45:03 debian /usr/local/sbin/kamailio[4281]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 29 06:45:03 debian /usr/local/sbin/kamailio[4282]: INFO: <core>
[main.c:817]: INFO: signal 15 received

 

Thanks in advance.

BR,

F.Chahrour

 

From: sr-users-bounces at lists.sip-router.org
[mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of Stoyan Mihaylov
Sent: Sunday, February 26, 2012 7:37 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
Subject: Re: [SR-Users] DRouting cause Kamailio 3.2 to stop

 

You can start kamailio from prompt directly  - of course logged as root:

kamailio {parameters - including cfg file}

If you are using ubuntu - it is more tricky - first you should create root
user, or may be you can start with:

sudo kamailio {parameters}

I never started kamailio using kamctrl. I am starting it through little
modified init script.

 

On Sun, Feb 26, 2012 at 1:10 PM, Fatima Chahrour~ Vanrise Technical Support
<fchahrour at vanrise.com> wrote:

Stayon, start kamailio as root means using kamctrl start?

 

Regards,

Fatima

From: sr-users-bounces at lists.sip-router.org
[mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of Stoyan Mihaylov
Sent: Friday, February 24, 2012 5:05 PM


To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
Subject: Re: [SR-Users] DRouting cause Kamailio 3.2 to stop

 

I am working with kamailio from 3 months or so. And we use it only as
registrar and load balance. All routing is done from Asterisks which are
behind kamailio. I only "route" using ds_select_dst - to select Asterisk
where to forward call.

 

I dont like signal 15 - looks like crash from wrong arguments or something
alike (but same signal you will see if you manually shut down kamailio). I
have no experience with module you use.

Next steps you can do are - to increase debug level, and again to look at
tail, especially in moment of dial - when kamailio crashes. You can check
also core dumps - how you can do it - there is discussion now about it -
important thing is may be you should start kamailio as root.

 

 

On Fri, Feb 24, 2012 at 4:40 PM, Fatima Chahrour~Vanrise Support
<fchahrour at vanrise.com> wrote:

Hi,

 

Thanks for your reply.

I have checked, and I have one question, from analyzing two points:

 

-          1st point is that before adding the drouting scripts no problem
with kamailio and no crash, but after adding the script in the routing logic
kamailio app dies

-          2nd point if I have have any wrong data in the database and try
to call, I get the  ("503", "No Rules matching the URI") on the x-lite

 

So both points doesn't mean that the problem lies in the scripts I have in
the routing logic area? (Also please note that I have got these scripts
after checking the kamailio doc and other google doc that applied drouting
scenario using kamailio 1.5.0).

 

Following your advice, I have check the syslog file before and after
performing the call and am getting the below

 

1)When I start kamailio I have the following in syslog :

 

an:/usr/local/etc/kamailio# kamctl start

 

INFO: Starting Kamailio : 

INFO: started (pid: 19296)

debian:/usr/local/etc/kamailio# tail -f /var/lo

local/ lock/  log/   

debian:/usr/local/etc/kamailio# tail -f /var/log/syslog

Feb 24 05:57:30 debian kamailio: WARNING: <core> [socket_info.c:1275]:
WARNING: fix_hostname: could not rev. resolve 192.168.111.139

Feb 24 05:57:30 debian kamailio: WARNING: <core> [socket_info.c:1275]:
WARNING: fix_hostname: could not rev. resolve 192.168.111.139

Feb 24 05:57:30 debian kamailio: INFO: <core> [tcp_main.c:4727]: init_tcp:
using epoll_lt as the io watch method (auto detected)

Feb 24 05:57:30 debian /usr/local/sbin/kamailio[19296]: INFO: usrloc
[hslot.c:53]: locks array size 512

Feb 24 05:57:30 debian /usr/local/sbin/kamailio[19296]: INFO: drouting
[drouting.c:272]: DRouting - initializing

Feb 24 05:57:30 debian /usr/local/sbin/kamailio[19296]: INFO: <core>
[udp_server.c:179]: INFO: udp_init: SO_RCVBUF is initially 111616

Feb 24 05:57:30 debian /usr/local/sbin/kamailio[19296]: INFO: <core>
[udp_server.c:230]: INFO: udp_init: SO_RCVBUF is finally 262142

Feb 24 05:57:30 debian /usr/local/sbin/kamailio[19296]: INFO: <core>
[udp_server.c:179]: INFO: udp_init: SO_RCVBUF is initially 111616

Feb 24 05:57:30 debian /usr/local/sbin/kamailio[19296]: INFO: <core>
[udp_server.c:230]: INFO: udp_init: SO_RCVBUF is finally 262142

Feb 24 05:57:31 debian /usr/local/sbin/kamailio[19310]: INFO: ctl
[io_listener.c:225]: io_listen_loop:  using epoll_lt io watch method
(config)

 

2) When I do the call from x-lite by dialing 961222222, after few seconds I
get Call Failed: Request Timeout on x-lite, and the syslog  shows:

 

an:/usr/local/etc/kamailio# tail -f /var/log/syslog

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19305]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19309]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19310]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19314]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19312]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19316]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19307]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19320]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19318]: INFO: <core>
[main.c:817]: INFO: signal 15 received

Feb 24 06:00:39 debian /usr/local/sbin/kamailio[19301]: INFO: <core>
[main.c:817]: INFO: signal 15 received

 

There is no error raised; So, shall I consider this as Kamailio crash and
focus my search on this as you mentioned previously? Or I need help in
achieving correct route script in the routing logic?

 

Thanks,

F.Chahrour

 

From: sr-users-bounces at lists.sip-router.org
[mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of Stoyan Mihaylov
Sent: Friday, February 24, 2012 2:48 PM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
Subject: Re: [SR-Users] DRouting cause Kamailio 3.2 to stop

 

I suppose - kamailio crashes. You can run in console on same server:

tail -f /var/log/syslog

or you can tail file where sys logs are stored.

There - you can see some debugs, and you can check discussion about kamailio
crashes and how to get dump file.

This way you will identify problem and then either you will fix your cfg
file, or you can report bug.

On Thu, Feb 23, 2012 at 6:01 PM, Fatima Chahrour~Vanrise Support
<fchahrour at vanrise.com> wrote:

Hi,

 

I am newly experiencing kamailio 3.2. I have installed kamailio and MySQL
and tried the test call from 1 PC(x-lite) to another PC(x-lite) and ended
successfully.

 

Now moving further, I have configured dynamic routing module and applied
needed parameters and scripts to finally be able to start kamailio without
any issue. Also I set a testing scenario in the related database tables

BUT my problem is that whenever am trying to call the predefined prefix
(961) from x-lite am getting a 'calling' message on it and then request
timeout where I find that kamailio has stopped running. I kamctrl start
again and call 961 then get calling so I wait and kamailio stps again. Below
is the script used in the routing logic and database record.

 

Any help to achieve a successful call is highly appreciated.

 

dr_gatways:       3, 1, '192.168.111.15', 0, '', '', 2, 'PC1'

 

dr_groups:          2, '.*', '.*', 0, 'Anyone'

 

dr_gw_lists:       2, '3', 'Test Call'

 

dr_rules:              2, '0', '961', '', 0, '1', '#2', 'Lebanon Fix'

 

 

####### Routing Logic ########

# main request routing logic

route{

 

  if (is_method("INVITE")) {

    setflag(1); # do accounting

    route(4); # Call our dynamic route.

  }

}

..

..

..

                

route[4] {
  if (!do_routing("0")) {
    send_reply("503", "No Rules matching the URI");
 
 
    exit;
  }
  if (is_method("INVITE")) {
    t_on_failure("4");
  }
route(RELAY);
 
}

..

..

..

 
 
failure_route[4] {
    if (use_next_gw()) {
        t_relay();
        exit;
    } else {
 
        t_reply ("503", "Service not available");
        exit;
    }
 
}

 

Thanks in Advance,

F.Chahrour

 


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users at 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 at 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 at lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20120301/ffac1b71/attachment-0001.htm>


More information about the sr-users mailing list