[OpenSIPS-Users] Query for opensips-1.11 crash due to mongodb connection break .

Bogdan-Andrei Iancu bogdan at opensips.org
Thu Jan 7 09:36:08 CET 2016


Hi Sasmita,

Thanks for all the info. Right now, the only step forward is to try to 
reproduce it on my side (so I can debug and investigate). Of course, 
unless getting access to your machine where the crash setup is in place 
is an option.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 06.01.2016 15:53, Sasmita Panda wrote:
> Hi Andrei ,
>
>    Opensips version is : 1.11.2-notls
>      Bellow is the back trace .
>
>
> GNU gdb (GDB) 7.6.1-ubuntu
> Copyright (C) 2013 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 "x86_64-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /root/opensips-1.11/sbin/opensips...done.
> [New LWP 16965]
>
> warning: Can't read pathname for load map: Input/output error.
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/root/opensips-1.11//sbin/opensips -m 1024 -f 
> /root/opensips-1.11//etc/opensips'.
> Program terminated with signal 11, Segmentation fault.
> #0  bson_iterator_next (i=i at entry=0x7ffff0fca8d0) at src/bson.c:346
> 346             return ( bson_type )( *i->cur );
> (gdb) bt
> #0  bson_iterator_next (i=i at entry=0x7ffff0fca8d0) at src/bson.c:346
> #1  0x00007f077dd56244 in mongo_db_insert_trans (con=<optimized out>, 
> table=<optimized out>, _k=<optimized out>, _v=<optimized out>, 
> _n=<optimized out>)
>     at cachedb_mongodb_dbase.c:1704
> #2  0x00007f077d722e60 in db_cachedb_insert (_h=<optimized out>, 
> _k=<optimized out>, _v=<optimized out>, _n=<optimized out>) at dbase.c:149
> #3  0x00007f077aef3407 in insert_siptrace_flag (keys=0x7f077b10bd20 
> <db_keys>, vals=0x7f077b10be20 <db_vals>, msg=0x7f077b10b710 <db_con>) 
> at siptrace.c:468
> #4  save_siptrace (avp=avp at entry=0x0, 
> first_val=first_val at entry=0x7ffff0fcacc0, msg=0x7f0739db73d0, 
> vals=0x7f077b10be20 <db_vals>, keys=0x7f077b10bd20 <db_keys>)
>     at siptrace.c:560
> #5  0x00007f077aef97af in trace_onreply_in (t=<optimized out>, 
> type=<optimized out>, ps=<optimized out>) at siptrace.c:1212
> #6  0x00007f077d2cabbd in run_trans_callbacks (type=type at entry=2, 
> trans=0x7f073a1606d8, req=<optimized out>, 
> rpl=rpl at entry=0x7f077ee222c0, code=<optimized out>)
>     at t_hooks.c:212
> #7  0x00007f077d2d1e2c in t_reply_matching 
> (p_msg=p_msg at entry=0x7f077ee222c0, p_branch=<optimized out>) at 
> t_lookup.c:827
> #8  0x00007f077d2d25bf in t_check (p_msg=p_msg at entry=0x7f077ee222c0, 
> param_branch=param_branch at entry=0x7ffff0fcaee0) at t_lookup.c:898
> #9  0x00007f077d2f1ec6 in reply_received (p_msg=0x7f077ee222c0) at 
> t_reply.c:1525
> #10 0x0000000000437af6 in forward_reply (msg=msg at entry=0x7f077ee222c0) 
> at forward.c:575
> #11 0x0000000000486da6 in receive_msg (buf=<optimized out>, 
> len=<optimized out>, rcv_info=rcv_info at entry=0x7ffff0fcb0b0) at 
> receive.c:214
> #12 0x0000000000501f8d in udp_rcv_loop () at udp_server.c:424
> #13 0x0000000000414b01 in main_loop () at main.c:942
> #14 main (argc=<optimized out>, argv=<optimized out>) at main.c:1634
>
>
>
> Actually , I am not getting anything from this . What else you want to 
> find the problem let me know .
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
> On Wed, Jan 6, 2016 at 2:49 PM, Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Hi Sasmita,
>
>     If mysql server is down, opensips will continue to work, failing
>     to perform any DB operation (of course) - definitely it will not
>     stop or so.
>
>     Now, back to the mongo issue - you have siptrace configured to
>     insert into mongo via db_cachedb ; and if you stop the mondo
>     daemon, the next insert it will crash opensips.
>     I see in your logs that a core file was generated - can you
>     extract and post here the backtrace ?
>
>     Also, what is the exact version of opensips (do opensips -V)
>
>     Best regards,
>
>     Bogdan-Andrei Iancu
>     OpenSIPS Founder and Developer
>     http://www.opensips-solutions.com
>
>     On 06.01.2016 07:59, Sasmita Panda wrote:
>>     Hi ,
>>
>>         Yes , it seems like this .
>>
>>               My concern is , If I am stopping mysql of the machine
>>     and my opensips is using mysql , then also opensips is not
>>     getting stopped . But why this is happening with mongodb  ?
>>
>>     This is the logs I am getting during opensips get stopped .
>>
>>      translated to  2
>>      request domain,<null>
>>      translated to  2
>>      ACC: transaction answered:
>>     timestamp=1452059689;method=BYE;from_tag=as2a07e122;to_tag=85d3d0e795bb4a57ab6a76dd95d7ec4e;call_id=8f01c197bf4f498ab9379a4f589a4d6b;code=200;reason=OK
>>      ERROR:cachedb_mongodb:mongo_db_insert_trans: Failed to run
>>     query. Err = 2, 32 , 0
>>      opensips segfault at 4 ip 00007fb1eb1c3fbc sp 00007fff267b0660
>>     error 4 in libmongoc.so.0.6.0[7fb1eb1bd000+13000]
>>      ACC: transaction answered:
>>     timestamp=1452059690;method=BYE;from_tag=as45b598fe;to_tag=988c2c314cc545cabb60b0c7c09c1aed;call_id=751c426ebacc4a03aba5ea3e326dcb91;code=200;reason=OK
>>      ERROR:cachedb_mongodb:mongo_db_insert_trans: Failed to run
>>     query. Err = 2, 32 , 0
>>      segfault at 4 ip 00007fb1eb1c3fbc sp 00007fff267b0660 error 4 in
>>     libmongoc.so.0.6.0[7fb1eb1bd000+13000]
>>      CRITICAL:core:receive_fd: EOF on 15
>>     INFO:core:handle_sigs: child process 20023 exited by a signal 11
>>     INFO:core:handle_sigs: core was generated
>>     INFO:core:handle_sigs: terminating due to SIGCHLD
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:sig_usr: signal 15 received
>>     INFO:core:cleanup: cleanup
>>      NOTICE:db_cachedb:destroy: destroy module db_cachedb ...
>>      NOTICE:cachedb_mongodb:destroy: destroy module cachedb_mongodb ...
>>
>>
>>      Please help me if I am doing something wrong . Thank you in
>>     advance .
>>
>>
>>     */Thanks & Regards/*
>>     /Sasmita Panda/
>>     /Network Testing and Software Engineer/
>>     /3CLogic , ph:07827611765/
>>
>>     On Tue, Jan 5, 2016 at 7:22 PM, Bogdan-Andrei Iancu
>>     <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>>
>>         Hi Sasmita,
>>
>>         you say when your mongos daemon is stopped then opensips is
>>         crashing (on the next attempt of a db query) ?
>>
>>         Regards,
>>
>>         Bogdan-Andrei Iancu
>>         OpenSIPS Founder and Developer
>>         http://www.opensips-solutions.com
>>
>>         On 30.12.2015 14:28, Sasmita Panda wrote:
>>>         Hi All,
>>>
>>>                   I am using opensips-1.11 with cachedb_mongodb and
>>>         db_cachedb integrated on it . Mongodb and Opensips is
>>>         running in different machines .
>>>
>>>                   Whenever mongodb is getting stopped opensips used
>>>         to crash . Is this a drawback or I am doing any mistake in
>>>         my configuration .
>>>
>>>         Bellow is the configuration I have done :
>>>         loadmodule "cachedb_mongodb.so"
>>>         loadmodule "db_cachedb.so"
>>>
>>>         modparam("cachedb_mongodb",
>>>         "cachedb_url","mongodb:instance1://opensips:opensipsmongo@x.x.x.x:27017/db.CCinfo"
>>>         <mailto:mongodb:instance1://opensips:opensipsmongo@x.x.x.x:27017/db.CCinfo>)
>>>
>>>         modparam("db_cachedb","cachedb_url","mongodb:instance1://opensips:opensipsmongo@x.x.x.x:27017/db.db"
>>>         <mailto:mongodb:instance1://opensips:opensipsmongo@x.x.x.x:27017/db.db>)
>>>
>>>         modparam("siptrace","db_url","cachedb://mongodb:instance1")
>>>
>>>
>>>                I am using it for siptrace module and storing some
>>>         data through cache_store function . Please let me know if I
>>>         can overcome this problem or also let me know if connection
>>>         with  mongodb is always needed for successful running of
>>>         opensips or what .
>>>
>>>
>>>                 Any kind of information is really appreciated .
>>>
>>>         */Thanks & Regards/*
>>>         /Sasmita Panda/
>>>         /Network Testing and Software Engineer/
>>>         /3CLogic , ph:07827611765/
>>>
>>>
>>>         _______________________________________________
>>>         Users mailing list
>>>         Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160107/03c4f7e7/attachment-0001.htm>


More information about the Users mailing list