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

[Sasmita Panda]

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>
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 Developerhttp://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"
> <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"
> <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 listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160106/26df0bd4/attachment.htm>