[sr-dev] location table expire/ruid problem again
Juha Heinanen
jh at tutpro.com
Tue Apr 23 09:34:33 CEST 2013
daniel,
i can now repeat the ruid conflict issue at will:
1) start sip proxy with empty location table
2) start pjsua that registers itself causing location entry to appear
both in memory and location table:
# sip-proxy_ctl mi ul_dump | grep -E -i -w 'AOR|Ruid'
AOR:: jh at test.fi
Ruid:: uloc-5176382e-3ed4-1
3) kill pjsua (if you are lucky and it does not crash on its own) with
killall -KILL pjsua
4) restart pjsua, which again registers itself and causes the error:
Apr 23 10:31:14 siika /usr/sbin/sip-proxy[16084]: INFO: REGISTER <sip:jh at test.fi> by <jh at test.fi> from <192.98.102.10> is authorized
##
Apr 23 10:31:14 siika /usr/sbin/sip-proxy[16084]: ERROR: db_mysql [km_dbase.c:122]: driver error on query: Duplicate entry 'uloc-5176382e-3ed4-1' for key 'ruid_idx'
Apr 23 10:31:14 siika /usr/sbin/sip-proxy[16084]: ERROR: <core> [db_query.c:235]: error while submitting query
Apr 23 10:31:14 siika /usr/sbin/sip-proxy[16084]: ERROR: usrloc [ucontact.c:615]: inserting contact in db failed
Apr 23 10:31:14 siika /usr/sbin/sip-proxy[16084]: ERROR: usrloc [ucontact.c:998]: failed to update database
Apr 23 10:31:14 siika /usr/sbin/sip-proxy[16084]: ERROR: registrar [save.c:739]: failed to update contact
-- juha
More information about the sr-dev
mailing list