Well, it appears that over the course of the past several weeks i have managed to confuse myself on the issues at hand. Upon re-reading the ticket there are two issues that I had uncovered. The first issue is where a database engine goes offline at some point during normal call processing causing a kamailio crash. This issue has been addressed as per the updated Informix CSDK library which i recently confirmed. The second issue is where a database is offline at kamailio startup and crashes kamailio based on the steps below:

• leave a database offline (shut down)
• start up kamailio
• kamailio starts even though the database is offline which is good
• my test query begins to execute against the offline database and kamailio reacts gracefully to not
  being able to submit the queries to the offline database. also good.
• now, if another entirely unrelated query is executed (a query against another database server for example) the program crashes.

The gdb output is exactly the same as previously pasted even with the updated Informix CSDK libraries. I was hoping the Informix CSDK update would solve this issue also, but it didn't.

Here are the results to your inquiry about gdb output.

(gdb) frame 1
#1 0x00002aec870c59fb in sql_reconnect (sc=0x2aeb63048b98) at sql_api.c:187
187 sc->dbh = sc->dbf.init(&sc->db_url);
(gdb) p sc
$4 = (sql_con_t *) 0x2aeb63048b98
(gdb) p *sc
$5 = {name = {s = 0x2aeb63048ab0 "voip=>unixodbc://xxxxxxx:yyyyyyy@localhost/voip", len = 4}, conid = 2025152179, db_url = {
s = 0x2aeb63048ab6 "unixodbc://xxxxxxx:yyyyyyy@localhost/voip", len = 43}, dbh = 0x0, dbf = {cap = 0, use_table = 0, init = 0, init2 = 0, close = 0, query = 0,
fetch_result = 0, raw_query = 0, free_result = 0, insert = 0, delete = 0, update = 0, replace = 0, last_inserted_id = 0, insert_update = 0, insert_delayed = 0,
insert_async = 0, affected_rows = 0, start_transaction = 0, end_transaction = 0, abort_transaction = 0, query_lock = 0, raw_query_async = 0}, next = 0x0}

Thank you for looking into this.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.