Re: [SR-Users] gruu and dead-lock in registrar module

2013-05-01 Thread Andreas Granig
Hi, On 05/01/2013 10:46 AM, Daniel-Constantin Mierla wrote: looked over the code and seems ok. The domain lock is set inside ul.get_urecord_by_ruid(_d, ahash, &inst, &r, &ptr). Ok, good to know. Are you doing other operations in config with usrloc/registrar rather than save()/lookup()? Any m

Re: [SR-Users] gruu and dead-lock in registrar module

2013-05-01 Thread Daniel-Constantin Mierla
Hello, looked over the code and seems ok. The domain lock is set inside ul.get_urecord_by_ruid(_d, ahash, &inst, &r, &ptr). With temp gruu, the real aor is not present in URI, it will be discovered based on ahash (aor hash id) and ruid, which compose the temp-gruu value. If the record is dis

Re: [SR-Users] gruu and dead-lock in registrar module

2013-04-30 Thread Andreas Granig
Hi Daniel, On 04/30/2013 05:34 PM, Daniel-Constantin Mierla wrote: what version are you playing with? To look in the right branch when troubleshooting first time, then look at the others that might be affected... The affected version is latest 3.3 branch, but the same code is there in 4.0 as

Re: [SR-Users] gruu and dead-lock in registrar module

2013-04-30 Thread Daniel-Constantin Mierla
Hello, what version are you playing with? To look in the right branch when troubleshooting first time, then look at the others that might be affected... Cheers, Daniel On 4/30/13 5:07 PM, Andreas Granig wrote: Hi, We're hitting an issue in a deployment where all udp receivers are sitting

[SR-Users] gruu and dead-lock in registrar module

2013-04-30 Thread Andreas Granig
Hi, We're hitting an issue in a deployment where all udp receivers are sitting in FUTEX_WAIT caused by save() -> lock_udomain() and seem to have deadlocked themselves every couple of days. Looking at the code, enable_gruu in registrar is active by default, and in lookup there is a code path