thr3ads.net - asterisk users - [asterisk-users] Segmentation fault with 13.5.0 / PJSIP 2.4.5 [Oct 2015]

If this information is useful, please help other people find it:
Share via:

Recursive

2015-Oct-11 20:15 UTC

[asterisk-users] Segmentation fault with 13.5.0 / PJSIP 2.4.5

Dear colleagues,

I just have experienced a segmentation fault with Asterisk 13.5.0 and PJSIP
2.4.5. Both of them have been compiled on a standard Debian Wheezy 64 bit. I did
not apply any patch or alter the sources of Asterisk or PJSIP in any way. Before
compiling and installing, I removed all traces of all old Asterisk and PJSIP
versions from my system very thoroughly.

The segmentation fault occurred when I was re-registering multiple endpoints one
after another as fast as I could do it manually (by operating the respective
phones) and at the same time tried to make calls from these phones. I have
attached what was happening before the segfault in the CLI; I had started
Asterisk with -vvvvvc.

Unfortunately, I can't reproduce the situation, so if we want to know the
cause of the problem, I guess it's necessary that a developer analyzes the
attachment and the respective part of the source code. I think I am not (yet ?)
so deep in Asterisk that I could help debug the problem, but if anybody tells me
what to do I am willing to help.

I hope that the attachment won't get blocked ...

Regards,

Recursive
-------------- next part --------------
*CLI>     -- Removed contact 'sip:hFc1zQKs at
192.168.xx.yy:5060;line=cvx8p4nk' from AOR 'hFc1zQKs' due to request
 Contact hFc1zQKs/sip:hFc1zQKs at 192.168.xx.yy:5060;line=cvx8p4nk has been
deleted
 Endpoint hFc1zQKs is now Unreachable
    -- Removed contact 'sip:e5JT6VqN at
192.168.xx.yy:5060;line=7d88y4uy' from AOR 'e5JT6VqN' due to request
 Contact e5JT6VqN/sip:e5JT6VqN at 192.168.xx.yy:5060;line=7d88y4uy has been
deleted
 Endpoint e5JT6VqN is now Unreachable
    -- Attempted to remove non-existent contact 'sip:hFc1zQKs at
192.168.xx.yy:5060;line=cvx8p4nk' from AOR 'hFc1zQKs' by request
    -- Removed contact 'sip:Zyw0lsGa at
192.168.xx.yy:5060;line=it15kl8j' from AOR 'Zyw0lsGa' due to request
 Contact Zyw0lsGa/sip:Zyw0lsGa at 192.168.xx.yy:5060;line=it15kl8j has been
deleted
 Endpoint Zyw0lsGa is now Unreachable
    -- Attempted to remove non-existent contact 'sip:e5JT6VqN at
192.168.xx.yy:5060;line=7d88y4uy' from AOR 'e5JT6VqN' by request
    -- Added contact 'sip:Zyw0lsGa at 192.168.xx.yy:5060;line=vvsqirer'
to AOR 'Zyw0lsGa' with expiration of 3600 seconds
 Contact Zyw0lsGa/sip:Zyw0lsGa at 192.168.xx.yy:5060;line=vvsqirer has been
created
 Endpoint Zyw0lsGa is now Reachable
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:1]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:2]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:3]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:4]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:5]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:6]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:7]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?101") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:8]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?101") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:9]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?101") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:10]
GotoIf("PJSIP/xDHoh0oP-00000000", "1?101") in new stack
    -- Goto (guV4QKtp_inbound,0172xxxxxxx,101)
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:101]
NoOp("PJSIP/xDHoh0oP-00000000", "xDHoh0oP") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:102]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?111") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:103]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?116") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:104]
GotoIf("PJSIP/xDHoh0oP-00000000", "0?121") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:105]
Goto("PJSIP/xDHoh0oP-00000000", "forbidden,201") in new
stack
    -- Goto (guV4QKtp_inbound,forbidden,201)
    -- Executing [forbidden at guV4QKtp_inbound:201]
Hangup("PJSIP/xDHoh0oP-00000000", "21") in new stack
  == Spawn extension (guV4QKtp_inbound, forbidden, 201) exited non-zero on
'PJSIP/xDHoh0oP-00000000'
    -- Added contact 'sip:hFc1zQKs at 192.168.xx.yy:5060;line=zzizib5p'
to AOR 'hFc1zQKs' with expiration of 600 seconds
 Contact hFc1zQKs/sip:hFc1zQKs at 192.168.xx.yy:5060;line=zzizib5p has been
created
 Endpoint hFc1zQKs is now Reachable
    -- Added contact 'sip:e5JT6VqN at 192.168.xx.yy:5060;line=ydffladj'
to AOR 'e5JT6VqN' with expiration of 600 seconds
 Contact e5JT6VqN/sip:e5JT6VqN at 192.168.xx.yy:5060;line=ydffladj has been
created
 Endpoint e5JT6VqN is now Reachable
    -- Removed contact 'sip:Zyw0lsGa at
192.168.xx.yy:5060;line=vvsqirer' from AOR 'Zyw0lsGa' due to request
 Contact Zyw0lsGa/sip:Zyw0lsGa at 192.168.xx.yy:5060;line=vvsqirer has been
deleted
 Endpoint Zyw0lsGa is now Unreachable
    -- Added contact 'sip:Zyw0lsGa at 192.168.xx.yy:5060;line=hiz5vysn'
to AOR 'Zyw0lsGa' with expiration of 3600 seconds
 Contact Zyw0lsGa/sip:Zyw0lsGa at 192.168.xx.yy:5060;line=hiz5vysn has been
created
 Endpoint Zyw0lsGa is now Reachable
    -- Removed contact 'sip:xDHoh0oP at
192.168.xx.yy:5060;line=ic86ajbw' from AOR 'xDHoh0oP' due to request
 Contact xDHoh0oP/sip:xDHoh0oP at 192.168.xx.yy:5060;line=ic86ajbw has been
deleted
 Endpoint xDHoh0oP is now Unreachable
    -- Added contact 'sip:xDHoh0oP at 192.168.xx.yy:5060;line=9ajux7vg'
to AOR 'xDHoh0oP' with expiration of 600 seconds
 Contact xDHoh0oP/sip:xDHoh0oP at 192.168.xx.yy:5060;line=9ajux7vg has been
created
 Endpoint xDHoh0oP is now Reachable
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:1]
GotoIf("PJSIP/hFc1zQKs-00000001", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:2]
GotoIf("PJSIP/hFc1zQKs-00000001", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:3]
GotoIf("PJSIP/hFc1zQKs-00000001", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:4]
GotoIf("PJSIP/hFc1zQKs-00000001", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:5]
GotoIf("PJSIP/hFc1zQKs-00000001", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:6]
GotoIf("PJSIP/hFc1zQKs-00000001", "0?forbidden,201") in new
stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:7]
GotoIf("PJSIP/hFc1zQKs-00000001", "0?101") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:8]
GotoIf("PJSIP/hFc1zQKs-00000001", "0?101") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:9]
GotoIf("PJSIP/hFc1zQKs-00000001", "0?101") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:10]
GotoIf("PJSIP/hFc1zQKs-00000001", "1?101") in new stack
    -- Goto (guV4QKtp_inbound,0172xxxxxxx,101)
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:101]
NoOp("PJSIP/hFc1zQKs-00000001", "hFc1zQKs") in new stack
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:102]
GotoIf("PJSIP/hFc1zQKs-00000001", "1?111") in new stack
    -- Goto (guV4QKtp_inbound,0172xxxxxxx,111)
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:111]
Dial("PJSIP/hFc1zQKs-00000001", "PJSIP/0172xxxxxxx at
GgYPIyX3") in new stack
    -- Called PJSIP/0172xxxxxxx at GgYPIyX3
  == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing [0172xxxxxxx at guV4QKtp_inbound:112]
Hangup("PJSIP/hFc1zQKs-00000001", "") in new stack
  == Spawn extension (guV4QKtp_inbound, 0172xxxxxxx, 112) exited non-zero on
'PJSIP/hFc1zQKs-00000001'
Segmentation fault

Joshua Colp

2015-Oct-11 20:21 UTC

head link

[asterisk-users] Segmentation fault with 13.5.0 / PJSIP 2.4.5

Recursive wrote:> Dear colleagues,
>
> I just have experienced a segmentation fault with Asterisk 13.5.0 and
> PJSIP 2.4.5. Both of them have been compiled on a standard Debian
> Wheezy 64 bit. I did not apply any patch or alter the sources of
> Asterisk or PJSIP in any way. Before compiling and installing, I
> removed all traces of all old Asterisk and PJSIP versions from my
> system very thoroughly.
>
> The segmentation fault occurred when I was re-registering multiple
> endpoints one after another as fast as I could do it manually (by
> operating the respective phones) and at the same time tried to make
> calls from these phones. I have attached what was happening before
> the segfault in the CLI; I had started Asterisk with -vvvvvc.
>
> Unfortunately, I can't reproduce the situation, so if we want to know
> the cause of the problem, I guess it's necessary that a developer
> analyzes the attachment and the respective part of the source code. I
> think I am not (yet ?) so deep in Asterisk that I could help debug
> the problem, but if anybody tells me what to do I am willing to
> help.
Information is on the wiki[1] which details how to get a backtrace from 
a core dump which may be present. Otherwise it's unlikely that the 
problem can be located without exact details for reproducing it. If you 
can get a backtrace though you can file an issue on the issue tracker[2].

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
[2] https://issues.asterisk.org/jira

-- 
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org

Recursive

2015-Oct-12 05:44 UTC

head link

[asterisk-users] Segmentation fault with 13.5.0 / PJSIP 2.4.5

> 
> Information is on the wiki[1] which details how to get a backtrace from a
core dump which may be present. Otherwise it's unlikely that the problem can
be located without exact details for reproducing it. If you can get a backtrace
though you can file an issue on the issue tracker[2].
> 
> [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
> [2] https://issues.asterisk.org/jira
> 
Thanks for the references. I am playing around with Asterisk several months now
and never have experienced a segfault until yesterday. I always thought the
software would be stable (because I have heard that even large companies use it)
and haven't compiled with the options for a core dump, so it looks like that
we'll never know what was happening.

But I am planning to upgrade to 13.6.0 anyway, and when doing so, I'll
enable the core dumps like shown in [1].

Regards,

Recursive

Maybe Matching Threads

Search for more apparently analagous threads

asterisk users - Oct 2015 - Segmentation fault with 13.5.0 / PJSIP 2.4.5

[asterisk-users] Segmentation fault with 13.5.0 / PJSIP 2.4.5

[asterisk-users] Segmentation fault with 13.5.0 / PJSIP 2.4.5

[asterisk-users] Segmentation fault with 13.5.0 / PJSIP 2.4.5

Maybe Matching Threads