Thanks Liviu. To give you some feedback, i ended up writing a sync query to "solve" the crash when ran into with this link --> https://www.opensips.org/Documentation/Script-Async-2-4 In general terms, it says that i shouldn't use async queries with Mysql (MariaDB in this Case) and recommend to code that logic in an external script launched asynchronously.
Regards Exequiel On Wed, Feb 19, 2020 at 8:44 AM Liviu Chircu <[email protected]> wrote: > On 17.02.2020 17:24, Exequiel leite wrote: > > CRITICAL:core:db_store_async_con: #012>>> DB con 0x7fb857f4d178 not > > found#012It seems you have hit a programming bug.#012Please help us > > make OpenSIPS better by reporting it at > > https://github.com/OpenSIPS/opensips/issues > > > > BTW I'm using Opensips 2.4.5 with a cluster of MariaDB DBs in the same > > network. I couldn´t relate it with a DB issue, the databases are > > working fine. > > > > Could anyone give me any clues about this? > > Hi Exequiel, > > That is some safety check I built into the async DB code during > development, since I never expected > (hence the abort()) that flow to trigger (a reconnect on a connection > that cannot be looked up > anymore). Let me try to re-evaluate that logic in the next days and see > if I can come up with > an explanation / fix. > > Regards, > > -- > Liviu Chircu > www.twitter.com/liviuchircu | www.opensips-solutions.com > > OpenSIPS Summit, Amsterdam, May 2020 > www.opensips.org/events > OpenSIPS Bootcamp, Miami, March 2020 > www.opensips.org/training > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
