[sr-dev] location table expire/ruid problem again

Juha Heinanen jh at tutpro.com
Tue Apr 23 08:55:29 CEST 2013


i was again hit by the problem of non-expiring location table entries.
this time it happened without any mi commands when pjsua crashed right
after registration.  15 minutes after expiring, that registration is
still in location table, but not in memory cash.

related to this location entry, i also got to syslog:

Apr 23 09:32:30 siika /usr/sbin/sip-proxy[14304]: ERROR: db_mysql [km_dbase.c:122]: driver error on query: Duplicate entry 'uloc-51761da3-37fb-e' for key 'ruid_idx'
Apr 23 09:32:30 siika /usr/sbin/sip-proxy[14304]: ERROR: <core> [db_query.c:235]: error while submitting query
Apr 23 09:32:30 siika /usr/sbin/sip-proxy[14304]: ERROR: usrloc [ucontact.c:615]: inserting contact in db failed
Apr 23 09:32:30 siika /usr/sbin/sip-proxy[14304]: ERROR: usrloc [urecord.c:363]: updating contact in db failed

that update was triggered by some timer, because it was not related to
any sip request. i haven't checked from the code what update is in
question, but unless ruid field itself is updated, i don't see how it
can result in duplicate entry.

-- juha



More information about the sr-dev mailing list