Here is the gdb "bt full" of crash, please look into this bug... (gdb) bt full #0 core_hash (cmd_tree=<value optimized out>, param=<value optimized out>) at ../../hash_func.h:54 end = 0x0 p = 0x0 v = <value optimized out> h = 0 s2 = 0x0 #1 process_mi_params (cmd_tree=<value optimized out>, param=<value optimized out>) at dlg_hash.c:1340 node = <value optimized out> d_entry = <value optimized out> dlg = <value optimized out> p2 = <value optimized out> h_entry = 8015792 p1 = 0x7f4f49420f18 #2 mi_print_dlgs (cmd_tree=<value optimized out>, param=<value optimized out>) at dlg_hash.c:1369 rpl_tree = 0x0 rpl = 0x0 idx = 0 cnt = 0 #3 0x00007f4f4635e696 in run_mi_cmd (fifo_stream=0x134e7e0) at ../../mi/mi.h:107 ret = <value optimized out> #4 mi_fifo_server (fifo_stream=0x134e7e0) at fifo_fnc.c:578 mi_cmd = <value optimized out> mi_rpl = <value optimized out> hdl = 0x0 line_len = 29 file_sep = <value optimized out> command = <value optimized out> file = <value optimized out> f = 0x7f4f49413438 reply_stream = 0x136bb20 __FUNCTION__ = "mi_fifo_server" #5 0x00007f4f4635fef6 in fifo_process (rank=<value optimized out>) at mi_fifo.c:214 fifo_stream = 0x134e7e0 __FUNCTION__ = "fifo_process" #6 0x00000000004806d1 in start_module_procs () at sr_module.c:765 m = 0x7f4f493e4390 n = 0 l = 0 x = 0 __FUNCTION__ = "start_module_procs" #7 0x0000000000430ee5 in main_loop () at main.c:714 chd_rank = 0 rc = 32767 startup_done = 0x0 __FUNCTION__ = "main_loop" #8 0x00000000004336e9 in main (argc=9, argv=0x7fffa88ef3b8) at main.c:1277 cfg_log_stderr = 0 cfg_stream = 0x1319010 ---Type <return> to continue, or q <return> to quit--- c = -1 r = 0 tmp = 0x0 tmp_len = 0 port = 5421776 proto = 0 options = 0x5380c8 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:" ret = -1 seed = 2219233510 rfd = 4 __FUNCTION__ = "main" (gdb)
On Mon, Apr 13, 2015 at 11:30 AM, Satish Patel <satish....@gmail.com> wrote: > Thanks Jeff for reply, > > Opensips crash with error "child process 6645 exited by a signal 11" > > I have generated core dump and following is my gdb output. look like i > have to recompile it with debug support. How do i compile it with debug > support? > > (gdb) bt full > #0 0x00007f74f2962ea0 in mi_print_dlgs () from > /opt/opensips/lib64/opensips/modules/dialog.so > No symbol table info available. > #1 0x00007f74f518995c in mi_fifo_server () from > /opt/opensips/lib64/opensips/modules/mi_fifo.so > No symbol table info available. > #2 0x00007f74f518b440 in ?? () from > /opt/opensips/lib64/opensips/modules/mi_fifo.so > No symbol table info available. > #3 0x000000000047a9fe in start_module_procs () > No symbol table info available. > #4 0x0000000000431e67 in main () > No symbol table info available. > > > > > > > > On Mon, Apr 13, 2015 at 8:03 AM, Jeff Pyle <jeff.p...@fidelityvoice.com> > wrote: > >> Satish, >> >> What causes you to believe it's killing your opensips? Is opensips >> running before you run the command, but not after you run the command? If >> you can verify this is the case, you should follow the relevant steps from >> the Crash Troubleshooting >> <http://www.opensips.org/Documentation/TroubleShooting-Crash> page. >> >> Look at the *green* from your error: >> >> ERROR: /tmp/opensips_fifo does not exist >>> ERROR: >>> *Make sure you have the line 'modparam("mi_fifo", "fifo_name", >>> "/tmp/opensips_fifo")' in your config*ERROR: *and also have loaded the >>> mi_fifo module.* >> >> >> Have you done what it says? >> >> opensipsctl uses the MI interface >> <http://www.opensips.org/Documentation/Interface-MI-2-1> to manipulate >> data within opensips. You will need to configure an MI module, such as the >> mi_fifo <http://www.opensips.org/html/docs/modules/2.1.x/mi_fifo.html> one >> mentioned above, to work with opensipsctl. Then, edit opensipsctlrc for >> your particular environment. >> >> Only after all these things are done will opensipsctl produce any output. >> >> >> >> - Jeff >> >> On Sun, Apr 12, 2015 at 3:53 PM, Satish Patel <satish....@gmail.com> >> wrote: >> >>> Bump!! Please help >>> >>> -- >>> Sent from my iPhone >>> >>> > On Apr 10, 2015, at 7:56 AM, Satish Patel <satish....@gmail.com> >>> wrote: >>> > >>> > Any thought? Why that command killing my opensips? I think it's a BUG. >>> > >>> > On production it will be dangerous if it kill service with random >>> command. >>> > >>> > -- >>> > Sent from my iPhone >>> > >>> >> On Apr 9, 2015, at 11:25 PM, Satish Patel <satish....@gmail.com> >>> wrote: >>> >> >>> >> Is this a bug? or its normal behavior? >>> >> >>> >> It is very dangerous, I was just playing with command and i type >>> following command which kill my opensips process, when i restarted service >>> then it back. >>> >> >>> >> I am using opensips 2.1 >>> >> >>> >> [root@sip ~]# opensipsctl fifo dlg_list to_uri:: >>> >> >>> >> [root@sip ~]# opensipsctl fifo dlg_list >>> >> ERROR: /tmp/opensips_fifo does not exist >>> >> ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name", >>> "/tmp/opensips_fifo")' in your config >>> >> ERROR: and also have loaded the mi_fifo module. >>> >> >>> >>> _______________________________________________ >>> Users mailing list >>> Users@lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >> >> >> _______________________________________________ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users