<div dir="ltr">I think I've found part of it. On line 536 of modules/db_text/dbt_file.c it reads 'bigint'. 'bigint' is read as a blob; it seems 'long' is the correct word to read the 'l' for DB_BIGINT (line 198).<div>
<br></div><div>Making that change helps, but now there is a new problem:</div><div><br></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><div>ERROR:dialog:load_dialog_info_from_db: inconsistent hash data in the dialog database: you may have restarted opensips using a different hash_size: please erase dialog database and restart</div>
</div><div><div>db : 869, dlg : 1919252015</div></div></blockquote><div><br></div><div class="gmail_extra"><div><div dir="ltr"><div>Obviously 869 != 1919252015, but I haven't found where those numbers come from. And the hash_size hasn't actually changed. Line 565 of modules/dialog/dbt_db_handler.c is the complainer.<br>
<br></div></div></div>
Perhaps another misbehaving column type in the db_text table?</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">- Jeff</div><div class="gmail_extra"><br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Oct 22, 2013 at 11:24 AM, Jeff Pyle <span dir="ltr"><<a href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">Bogdan and team,<div><br></div><div>This is on a 1.9 build from October 17, plus the recently committed change to the dialog table schema in dbtext.</div><div><br></div><div>Here's the scenario... After a fresh Opensips start, I place a call through it. A dialog is established. I stop Opensips after about five seconds and verify the contents of the dialog table file:<br>
</div><div><br></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><div>dlg_id(bigint) callid(string) from_uri(string) from_tag(string) to_uri(string) to_tag(string) mangled_from_uri(string,null) mangled_to_uri(string,null) caller_cseq(string) callee_cseq(string) caller_ping_cseq(int) callee_ping_cseq(int) caller_route_set(string,null) callee_route_set(string,null) caller_contact(string) callee_contact(string) caller_sock(string) callee_sock(string) state(int) start_time(int) timeout(int) vars(string,null) profiles(string,null) script_flags(int) flags(int)</div>
</div><div><div>8672076440446:662bbb7a-8f52-4c26-adaa-6f2f5f870751:.....remaining fields for dialog record.....</div></div></blockquote><div><br></div><div>I again start Opensips. I see this in the log (debug=3):</div><div>
<br></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div>ERROR:dialog:load_dialog_info_from_db: column dlg_id cannot be null/has wrong type 6 -> skipping</div></blockquote><div><br></div><div>
One interesting note, when Opensips starts the dlg_id column is defined with 'long'. After Opensips exits, it has 'bigint' type. I don't know if that's relevant.</div><span class=""><font color="#888888">
<div><br></div><div><br></div><div>- Jeff</div><div><br></div><div><br></div><div><br></div></font></span></div>
</blockquote></div><br></div></div>