[SR-Users] Kamailio Unexpectedly Terminating

[Daniel-Constantin Mierla]

Hello,

On 5/30/12 4:26 AM, Akan wrote:
> Sorry. To make sure I got the right versions, I removed all of the 
> previous files, reloaded and re-compiled Kamailio from git and ran the 
> test again.
is it git master branch? Because the branch 3.2 does not have all 
patches backported, as I wanted to test them first, 3.2 is a stable 
branch used in production.

It does not seem the latest as the line of crash is reporting to be:

102                     realm_prefix.s = cfg_get(registrar, registrar_cfg, realm_pref);

And the last source code is:

realm_prefix.s = cfg_get(registrar, registrar_cfg, realm_pref).s;

Can you try with latest git master branch? At least will be sure it is 
the right source code.

Cheers,
Daniel


> I have included the full trace files from the core dump. Here is my 
> setting for use_domain parameter:
>
> #!define MULTIDOMAIN 1
> modparam("usrloc", "db_url", DBURL)
> modparam("usrloc", "db_mode", 2)
> modparam("usrloc", "use_domain", MULTIDOMAIN)
>
>
> Thanks
>
> Nathaniel L Keeling
>
> On 5/29/2012 4:15 AM, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> is this with use_domain parameter set?
>>
>> Also, from the backtrace, the condition is not
>>
>> 104                     if (realm_prefix.len>0 && 
>> realm_prefix.len<puri.host.len &&
>>
>> but
>>
>> 104                     if (realm_prefix.len && 
>> realm_prefix.len<puri.host.len &&
>>
>>
>> It looks it is without the last recommendation I made - now I pushed 
>> the change also in master branch.
>>
>> Cheers,
>> Daniel
>>
>> On 5/29/12 10:55 AM, Akan wrote:
>>> I am still getting a core dump with Kamailio v3.2. I loaded Kamailio 
>>> on a new server, applied the patch and started testing. I was able 
>>> to register successfully which previously I was not, but now when I 
>>> try to make a call, kamailio will take a core dump. I also loaded 
>>> Kamailio v3.1 just to make sure that it is not a memory issue and I 
>>> was able to place a call successfully without Kamailio taking a core 
>>> dump. I have included the full backtrace from the dump and it looks 
>>> like it is in the same place as previously.  I loaded Kamailio v3.2 
>>> on 3 different servers with the same results of producing a core 
>>> dump. I have not tried the new development version yet.
>>>
>>>
>>> Thanks
>>>
>>> Nathaniel
>>>
>>> On 5/23/2012 1:44 AM, Akan wrote:
>>>> I'd setup another solaris server with kamailio v3.2, applied the 
>>>> patch and tested the change. Kamailio did not crash nor took a core 
>>>> dump. So it looks like it might be a hardware problem now.
>>>>
>>>> Thanks
>>>>
>>>> Nathaniel
>>>>
>>>> On 5/9/2012 1:52 PM, Akan wrote:
>>>>> I changed the use_domain parameter for usrloc to 0 and retried. 
>>>>> Kamailio did not crash and I was able to get registered. I have 
>>>>> another server with the same configurations as the one having the 
>>>>> problem. I will apply the patch there and see if the problem still 
>>>>> occurs. Also, setting the use_domain to 0 for usrloc, does this 
>>>>> limit me to not being able to use other domains within the SIP 
>>>>> message?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Nathaniel
>>>>>
>>>>> On 5/9/2012 3:05 AM, Daniel-Constantin Mierla wrote:
>>>>>> Hello,
>>>>>>
>>>>>> I see no reason why it crashes at line 104 when realm_prefix.len==0.
>>>>>>
>>>>>> Might be a memory problem (hardware). Can you try with use_domain 
>>>>>> parameter set to 0 for usrloc module?
>>>>>>

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw