[SR-Users] segfault in siptrace module using setflag?

[samuel]

Hi all,

I had some problems with git (was it git fetch to update the local copy
from the "main" reposiory?) and I manually changed siptrace.c with the
addition of the len pointer in case it was using version 2 of HEP.
So far the server has not crashed. Before with just a few calls (less than
10) the pointer got lost but now, with almost a hundred calls, kamailio is
solid as a rock.

Thanks a lot, specially to Daniel and Dragos, for the attention received!

Samuel.

On 16 October 2012 13:02, samuel <samu60 at gmail.com> wrote:

> I'll try the last branch to see whether it solves the issue.
>
> thanks a lot indeed for the fast attention and reaction!
>
> Samuel.
>
>
> On 16 October 2012 12:12, Dragos Dinu <dragos.dinu at 1and1.ro> wrote:
>
>> Hi Samuel,
>>
>> Could you try to test again with the updated siptrace sources from 3.3
>> branch? I had a patch recently commited for a crash in siptrace, so I'm
>> pretty sure you have the same issue.
>> Please tell us if your problem was fixed.:)
>>
>> Dragos
>>
>>
>> On 10/09/2012 12:00 PM, samuel wrote:
>>
>>> Hi folks,
>>>
>>> I was making some tests with kamailio (both 3.3.0 and 3.3.1 tgz) with
>>> siptrace module sending "homer" packets to a remote central agent where the
>>> data is stored and presented to the user.
>>>
>>> The related config is:
>>> # ----- siptrace params from HOMER -----
>>> modparam("siptrace", "duplicate_uri", "sip:A.B.C.D:9060")
>>> modparam("siptrace", "trace_to_database", 0)
>>> modparam("siptrace", "trace_flag", 22)
>>> modparam("siptrace", "trace_on", 1)
>>> #HEPv2 == timestamp will be included to HEP header
>>> modparam("siptrace", "hep_version", 2)
>>> modparam("siptrace", "hep_mode_on", 1)
>>> modparam("siptrace", "hep_capture_id", 1)
>>>
>>> basically for all incoming messages, a route is called with the
>>> following actions:
>>>
>>> route[HOMER] {
>>>         setflag(22);
>>>         sip_trace();
>>> }
>>>
>>> I've been making some tests and if I disable the setflag action, there
>>> is no problem (well, no transaction messages are sent to the central
>>> agent), but as soon as I activated setflag, kamailio crashes with the
>>> following error:
>>>
>>> <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 28
>>>
>>> There's no concrete point in the config file where it fails so I think
>>> the problem is more tm-internals related. I can provide further information
>>> in case you need it.
>>>
>>> Just for adding information, and without any intention to start a
>>> flame-war, with opensips 1.8.0-tls the server does not crash...
>>>
>>> Thanks in advance!
>>> Samuel.
>>>
>>
>>
>> ______________________________**_________________
>> 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<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20121016/3f3f30e4/attachment-0001.htm>