31 Mar
2009
31 Mar
'09
2:08 p.m.
Hello
Can anybody please help me on how to force a core dump if a child
crashes? I see this:
/usr/sbin/kamailio[12328]: INFO:core:handle_sigs: child process 12379
exited by a signal 11
/usr/sbin/kamailio[12328]: INFO:core:handle_sigs: core was not generated
/usr/sbin/kamailio[12328]: INFO:core:handle_sigs: terminating due to SIGCHLD
/usr/sbin/kamailio[12393]: INFO:core:sig_usr: signal 15 received
And if I run with gdb, it says 'Program exited normally'
Has anybody managed to make a core dump in this case?
Thanks
Catalina
31 Mar
31 Mar
2:11 p.m.
Hello,
set: 'ulimit -c unlimited'
Cheers,
Daniel
On 03/31/2009 02:08 PM, catalina oancea wrote:
Hello
Can anybody please help me on how to force a core dump if a child
crashes? I see this:
/usr/sbin/kamailio[12328]: INFO:core:handle_sigs: child process 12379
exited by a signal 11
/usr/sbin/kamailio[12328]: INFO:core:handle_sigs: core was not generated
/usr/sbin/kamailio[12328]: INFO:core:handle_sigs: terminating due to SIGCHLD
/usr/sbin/kamailio[12393]: INFO:core:sig_usr: signal 15 received
And if I run with gdb, it says 'Program exited normally'
Has anybody managed to make a core dump in this case?
Thanks
Catalina
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
--
Daniel-Constantin Mierla
SIP Router Masterclass - Kamailio (OpenSER) Training
http://www.asipto.com/index.php/sip-router-masterclass/
3:59 p.m.
Hello
I created a new dialog, chowned it to the user running kamailio (I
have kamailio.kamailio) and started kamailio with command:
/usr/sbin/kamailio -u kamailio -g kamailio
I the log, pre-crash lines are:
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:presence:get_subs_db: found 2 dialogs
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:presence:printf_subs: [pres_uri]= sip:0003*001@192.168.12.12
[to_user]= 0003*001 [to_domain]= 192.168.12.12 [w_user]=
0003*023 [w_domain]= 192.168.12.12 [event]= dialog
[status]= active [expires]= 55 [callid]=
a27bd1480248bc7b(a)10.0.0.12 [local_cseq]=1 [to_tag]=
10.18019.1238503961.1 [from_tag]= b779b76560ee1177 [contact]=
sip:0003*023@192.168.1.26:61236;transport=udp [record_route]=
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:presence:printf_subs: [pres_uri]= sip:0003*001@192.168.12.12
[to_user]= 0003*001 [to_domain]= 192.168.12.12 [w_user]=
0003*023 [w_domain]= 192.168.12.12 [event]= dialog
[status]= active [expires]= 10 [callid]=
a27bd1480248bc7b(a)10.0.0.12 [local_cseq]=1 [to_tag]=
10.18022.1238503916.1 [from_tag]= b779b76560ee1177 [contact]=
sip:0003*023@192.168.1.26:61236;transport=udp [record_route]=
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing 16 columns
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[0] at 0x7dcc38
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[1] at 0x7d9b08
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[2] at 0x7d9bc8
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[3] at 0x7d93c0
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[4] at 0x7d9b88
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[5] at 0x7d9650
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[6] at 0x7d96e0
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[7] at 0x7d96c0
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[8] at 0x7d9510
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[9] at 0x7d9858
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[10] at 0x7d9aa0
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[11] at 0x7dcc58
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[12] at 0x7d94e0
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[13] at 0x7dce30
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[14] at 0x7dce50
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing RES_NAMES[15] at 0x7d95f0
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing result names at 0x7dcfb8
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_columns: freeing result types at 0x7dce88
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]: DBG:core:db_free_rows:
freeing 2 rows
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]: DBG:core:db_free_row:
freeing row values at 0x7dd800
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]: DBG:core:db_free_row:
freeing row values at 0x7dda10
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]: DBG:core:db_free_rows:
freeing rows at 0x7d9610
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:core:db_free_result: freeing result set at 0x7d9488
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18023]:
DBG:presence:printf_subs: [pres_uri]= sip:0003*001@192.168.12.12
[to_user]= 0003*001 [to_domain]= 192.168.12.12 [w_user]=
0003*023 [w_domain]= 192.168.12.12 [event]= dialog
[status]= active [expires]= 1238504022 [callid]=
a27bd1480248bc7b(a)10.0.0.12 [local_cseq]=1 [to_tag]=
10.18022.1238503962.3 [from_tag]= b779b76560ee1177 [contact]=
sip:0003*023@192.168.1.26:61236;transport=udp [record_route]=
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18041]:
CRITICAL:core:receive_fd: EOF on 11
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18041]:
DBG:core:handle_ser_child: dead child 4, pid 18023 (shutting down?)
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18041]: DBG:core:io_watch_del:
io_watch_del (0x747d00, 11, -1, 0x0) fd_no=17 called
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18011]: INFO:core:handle_sigs:
child process 18023 exited by a signal 11
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18011]: INFO:core:handle_sigs:
core was not generated
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18011]: INFO:core:handle_sigs:
terminating due to SIGCHLD
Still no core anywhere
If anyone has any more ideas, please share
Thanks again,
Catalina
2009/3/31 Henning Westerholt <henning.westerholt(a)1und1.de>de>:
On Tuesday 31 March 2009, Daniel-Constantin Mierla
wrote:
Hello,
set: 'ulimit -c unlimited'
Also required is that the server has the permissions to write the core dump to
its working dir, check the configuration.
Cheers,
Henning
4:06 p.m.
On Tuesday 31 March 2009, catalina oancea wrote:
Hello
I created a new dialog, chowned it to the user running kamailio (I
have kamailio.kamailio) and started kamailio with command:
/usr/sbin/kamailio -u kamailio -g kamailio
I the log, pre-crash lines are:
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18011]: INFO:core:handle_sigs:
core was not generated
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18011]: INFO:core:handle_sigs:
terminating due to SIGCHLD
Hi catalina,
try to specify a working directory:
-w dir Change the working directory to "dir" (default "/")
Cheers,
Henning
1 Apr
1 Apr
10:23 a.m.
Hi again,
The -w thing did the trick.
Thanks a lot!
Catalina
2009/3/31 Henning Westerholt <henning.westerholt(a)1und1.de>de>:
On Tuesday 31 March 2009, catalina oancea wrote:
Hello
I created a new dialog, chowned it to the user running kamailio (I
have kamailio.kamailio) and started kamailio with command:
/usr/sbin/kamailio -u kamailio -g kamailio
I the log, pre-crash lines are:
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18011]: INFO:core:handle_sigs:
core was not generated
Mar 31 15:52:46 kat2 /usr/sbin/kamailio[18011]: INFO:core:handle_sigs:
terminating due to SIGCHLD
Hi catalina,
try to specify a working directory:
-w dir Change the working directory to "dir" (default "/")
Cheers,
Henning
5717
days inactive
5718
days old
5 comments
3 participants
participants (3)
-
catalina oancea -
Daniel-Constantin Mierla -
Henning Westerholt