[SR-Users] Kamailio Exits With: Segmentation Fault Error 4 in usrloc.so

Alexandr Dubovikov voip at start4.info
Fri Feb 17 14:34:18 CET 2012 

Hi Daniel,

ok, I will fix it in the sipcapture on this WE.

Wbr,
Alexandr

17.02.2012 14:26, Daniel-Constantin Mierla wrote:
> Hello,
>
> On 2/17/12 2:09 PM, Alexandr Dubovikov wrote:
>>
>> Hi,
>>
>> If i got it also correct:
>>
>> Simpson is getting SIP messages from a raw socket in the sipcapture 
>> module and try to save all REGISTER messages to the location table 
>> through the userloc module. (user registration audit)
>
> so sipcapture is executing the request route block from the config 
> even for packages received on the raw sockets. In this case it does 
> not set the socket and its string representation...
>
> Not sure yet the best place where it should be fixed: in usrloc (to 
> test for sock and sock_str) or in sipcapture, to set this fields as 
> most of the other config function. The second will be safer overall, 
> but might not be an usable socket for sending (if someone will attempt 
> to do lookup location and relay).
>
> Cheers,
> Daniel
>
>
>>
>> Wbr,
>> Alexandr
>>
>> 17.02.2012 13:49, Daniel-Constantin Mierla wrote:
>>> Hello,
>>>
>>> On 2/17/12 1:11 PM, Alexandr Dubovikov wrote:
>>>> Hi Daniel,
>>>>
>>>> he use raw_socket in the sipcapture module and save all REGISTER 
>>>> messages to location. (something like fraud controling for 
>>>> registration). I think in this case he have to ignore socket listener.
>>>
>>> not sure I understood -- it is on the server that saves to homer's 
>>> database? It gets the traffic over a raw socket and then executes 
>>> the config file as usual with functions from other modules?
>>>
>>> Cheers,
>>> Daniel
>>>
>>>>
>>>> Wbr,
>>>> Alexandr
>>>>
>>>>
>>>>
>>>>
>>>> 17.02.2012 09:19, Daniel-Constantin Mierla wrote:
>>>>> Hello,
>>>>>
>>>>> looks like an invalid listen socket structure, quite strange... 
>>>>> what version of kamailio do you have?
>>>>>
>>>>> Also, in gdb, frame 0, can you send the output of:
>>>>>
>>>>> p *_c
>>>>> p *_c->sock
>>>>>
>>>>> You can replace sensitive data (like IP), if you wish.
>>>>>
>>>>> Cheers,
>>>>> Daniel
>>>>>
>>>>> On 2/16/12 10:52 PM, Simpson Chua wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Kamailio is exiting with a segmentation fault when trying to do a 
>>>>>> save("location"). Here is some information I gathered.
>>>>>>
>>>>>> Feb 16 15:30:19 ubuntu /usr/local/sbin/kamailio[25721]: DEBUG: 
>>>>>> <core> [parser/msg_parser.c:103]: found end of header
>>>>>> Feb 16 15:30:19 ubuntu /usr/local/sbin/kamailio[25721]: ERROR: 
>>>>>> <core> [db.c:435]: invalid parameter value
>>>>>> Feb 16 15:30:19 ubuntu /usr/local/sbin/kamailio[25721]: ERROR: 
>>>>>> usrloc [udomain.c:564]: failed to use table location
>>>>>> Feb 16 15:30:19 ubuntu kernel: [171540.056663] kamailio[25721]: 
>>>>>> segfault at 89 ip 00007fa1f9a41452 sp 00007fff971a3af0 error 4 in 
>>>>>> usrloc.so[7fa1f9a37000+1f000]
>>>>>> Feb 16 15:30:19 ubuntu /usr/local/sbin/kamailio[25708]: ALERT: 
>>>>>> <core> [main.c:751]: child process 25720 exited by a signal 11
>>>>>> Feb 16 15:30:19 ubuntu /usr/local/sbin/kamailio[25708]: ALERT: 
>>>>>> <core> [main.c:754]: core was generated
>>>>>> Feb 16 15:30:19 ubuntu /usr/local/sbin/kamailio[25708]: INFO: 
>>>>>> <core> [main.c:766]: INFO: terminating due to SIGCHLD
>>>>>>
>>>>>> Core was generated by `kamailio -w /home/core'.
>>>>>> Program terminated with signal 11, Segmentation fault.
>>>>>> #0  db_insert_ucontact (_c=0x7f5f8f737eb0) at ucontact.c:474
>>>>>> 474                     vals[11].val.str_val = _c->sock->sock_str;
>>>>>> (gdb) bt
>>>>>> #0  db_insert_ucontact (_c=0x7f5f8f737eb0) at ucontact.c:474
>>>>>> #1  0x00007f5f916d9649 in insert_ucontact (_r=<optimized out>, 
>>>>>> _contact=<optimized out>, _ci=<optimized out>, _c=0x7fff52bbeb88) 
>>>>>> at urecord.c:473
>>>>>> #2  0x00007f5f914b785f in insert_contacts (_m=0x7f5f93d7f458, 
>>>>>> _d=0x7f5f8f72f680, _a=0x7fff52bbec00) at save.c:428
>>>>>> #3  0x00007f5f914b8d10 in add_contacts (_mode=1, 
>>>>>> _a=0x7fff52bbec00, _d=0x7f5f8f72f680, _m=0x7f5f93d7f458) at 
>>>>>> save.c:737
>>>>>> #4  save (_m=0x7f5f93d7f458, _d=0x7f5f8f72f680, _cflags=4) at 
>>>>>> save.c:790
>>>>>> #5  0x000000000041ba87 in do_action (h=0x7fff52bbf5d0, 
>>>>>> a=0x7f5f93d7f238, msg=0x7f5f93d7f458) at action.c:1128
>>>>>> #6  0x000000000041abe2 in run_actions (h=0x7fff52bbf5d0, 
>>>>>> a=0x7f5f93d7f238, msg=0x7f5f93d7f458) at action.c:1610
>>>>>> #7  0x000000000041c05b in do_action (h=0x7fff52bbf5d0, 
>>>>>> a=0x7f5f93d7fe08, msg=0x7f5f93d7f458) at action.c:1107
>>>>>> #8  0x000000000041abe2 in run_actions (h=0x7fff52bbf5d0, 
>>>>>> a=0x7f5f93d7fe08, msg=0x7f5f93d7f458) at action.c:1610
>>>>>> #9  0x0000000000422fa2 in run_top_route (a=0x7f5f93d7fe08, 
>>>>>> msg=0x7f5f93d7f458, c=<optimized out>) at action.c:1683
>>>>>> #10 0x00000000004b061e in receive_msg (buf=<optimized out>, 
>>>>>> len=<optimized out>, rcv_info=<optimized out>) at receive.c:207
>>>>>> #11 0x00007f5f91b038b0 in raw_capture_rcv_loop (rsock=5, 
>>>>>> port1=5060, port2=8933, ipip=0) at sipcapture.c:1518
>>>>>> #12 0x00007f5f91b03e1f in init_rawsock_children () at 
>>>>>> sipcapture.c:572
>>>>>> #13 0x00007f5f91b04033 in child_init (rank=<optimized out>) at 
>>>>>> sipcapture.c:542
>>>>>> #14 0x0000000000507a0f in init_mod_child (m=0x7f5f93d7b2b0, 
>>>>>> rank=0) at sr_module.c:886
>>>>>> #15 0x0000000000507974 in init_mod_child (m=0x7f5f93d7b668, 
>>>>>> rank=0) at sr_module.c:883
>>>>>> #16 0x0000000000507974 in init_mod_child (m=0x7f5f93d7c178, 
>>>>>> rank=0) at sr_module.c:883
>>>>>> #17 0x0000000000507974 in init_mod_child (m=0x7f5f93d7c4b0, 
>>>>>> rank=0) at sr_module.c:883
>>>>>> #18 0x0000000000476149 in main_loop () at main.c:1661
>>>>>> #19 0x000000000041a940 in main (argc=<optimized out>, 
>>>>>> argv=0x7fff52bbfd68) at main.c:2475
>>>>>>
>>>>>> Any idea why this is happening? Is there something in the 
>>>>>> REGISTER message that is causing this?
>>>>>>
>>>>>> Thanks,
>>>>>> Simpson
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>>>>> sr-users at lists.sip-router.org
>>>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>>> -- 
>>>>> Daniel-Constantin Mierla --http://www.asipto.com
>>>>> http://linkedin.com/in/miconda  -- http://twitter.com/miconda
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>>>> sr-users at lists.sip-router.org
>>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>
>>> -- 
>>> Daniel-Constantin Mierla --http://www.asipto.com
>>> http://linkedin.com/in/miconda  -- http://twitter.com/miconda
>>
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>> -- 
>> Daniel-Constantin Mierla --http://www.asipto.com
>> http://linkedin.com/in/miconda  -- http://twitter.com/miconda

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20120217/931efb00/attachment-0001.htm>

More information about the sr-users mailing list