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

Daniel-Constantin Mierla miconda at gmail.com
Tue Apr 23 08:59:13 CEST 2013


Hello,

it is on my to-do for later today to review this issue, following the 
report before.

Cheers,
Daniel

On 4/23/13 8:55 AM, Juha Heinanen wrote:
> 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
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda




More information about the sr-dev mailing list