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 >> us...@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > > _______________________________________________ > Users mailing list > us...@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel