[asterisk-bugs] [JIRA] (ASTERISK-29134) app_mixmonitor: Crash in AMI StopMixMonitor

Joshua Elson (JIRA) noreply at issues.asterisk.org
Mon Nov 16 17:02:16 CST 2020


    [ https://issues.asterisk.org/jira/browse/ASTERISK-29134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252783#comment-252783 ] 

Joshua Elson edited comment on ASTERISK-29134 at 11/16/20 5:01 PM:
-------------------------------------------------------------------

So got a bunch more crashes with malloc_debug on. Here's what appears in kernel logs:

Dmesg:

[34021.798540] asterisk[77363]: segfault at 7feffffffffe ip 0000000000462bc5 sp 00007fefe2df6980 error 4 in asterisk[400000+2ee000]
[34168.186284] asterisk[77517]: segfault at 10 ip 00007fab000e60d5 sp 00007faa887676b8 error 4 in libpthread-2.17.so[7fab000da000+17000]
[34338.317698] asterisk[86112]: segfault at 7f16fffffffe ip 0000000000462bc5 sp 00007f179abf9980 error 4 in asterisk[400000+2ee000]
[36186.976858] traps: asterisk[2394] general protection ip:4e0164 sp:7f671db686e0 error:0 in asterisk[400000+2ee000]
[36392.238229] asterisk[2521]: segfault at fffffffc ip 000000000046233b sp 00007f8fc80e4690 error 4 in asterisk[400000+2ee000]

Messages:

]2020-11-16 15:45:24.694 ubluprdasv32v asterisk[2521]: segfault at fffffffc ip 000000000046233b sp 00007f8fc80e4690 error 4 in asterisk[400000+2ee000]
2020-11-16 15:45:24.694 ubluprdasv32v node=ubluprdasv32v type=ANOM_ABEND msg=audit(1605566724.693:4323): auid=4294967295 uid=1001 gid=1001 ses=4294967295 pid=2496 comm="asterisk" reason="memory violation" sig=11
2020-11-16 15:45:24.723 ubluprdasv32v Process 9 (asterisk) of user 1001 killed by SIGSEGV - dumping core

2020-11-16 15:08:20.338 ubluprdasv32v node=ubluprdasv32v type=ANOM_ABEND msg=audit(1605564500.335:4040): auid=4294967295 uid=1001 gid=1001 ses=4294967295 pid=77483 comm="asterisk" reason="memory violation" sig=11
2020-11-16 15:08:20.338 ubluprdasv32v asterisk[77517]: segfault at 10 ip 00007fab000e60d5 sp 00007faa887676b8 error 4 in libpthread-2.17.so[7fab000da000+17000]
2020-11-16 15:08:20.366 ubluprdasv32v Process 9 (asterisk) of user 1001 killed by SIGSEGV - dumping core

If a whole core file tarball is needed for any of these, let me know.


was (Author: joshelson):
So got a bunch more crashes with malloc_debug on. Here's what appears in kernel logs:

Dmesg:

```
[34021.798540] asterisk[77363]: segfault at 7feffffffffe ip 0000000000462bc5 sp 00007fefe2df6980 error 4 in asterisk[400000+2ee000]
[34168.186284] asterisk[77517]: segfault at 10 ip 00007fab000e60d5 sp 00007faa887676b8 error 4 in libpthread-2.17.so[7fab000da000+17000]
[34338.317698] asterisk[86112]: segfault at 7f16fffffffe ip 0000000000462bc5 sp 00007f179abf9980 error 4 in asterisk[400000+2ee000]
[36186.976858] traps: asterisk[2394] general protection ip:4e0164 sp:7f671db686e0 error:0 in asterisk[400000+2ee000]
[36392.238229] asterisk[2521]: segfault at fffffffc ip 000000000046233b sp 00007f8fc80e4690 error 4 in asterisk[400000+2ee000]
```

Messages:

```
2020-11-16 15:45:24.694 ubluprdasv32v asterisk[2521]: segfault at fffffffc ip 000000000046233b sp 00007f8fc80e4690 error 4 in asterisk[400000+2ee000]
2020-11-16 15:45:24.694 ubluprdasv32v node=ubluprdasv32v type=ANOM_ABEND msg=audit(1605566724.693:4323): auid=4294967295 uid=1001 gid=1001 ses=4294967295 pid=2496 comm="asterisk" reason="memory violation" sig=11
2020-11-16 15:45:24.723 ubluprdasv32v Process 9 (asterisk) of user 1001 killed by SIGSEGV - dumping core

2020-11-16 15:08:20.338 ubluprdasv32v node=ubluprdasv32v type=ANOM_ABEND msg=audit(1605564500.335:4040): auid=4294967295 uid=1001 gid=1001 ses=4294967295 pid=77483 comm="asterisk" reason="memory violation" sig=11
2020-11-16 15:08:20.338 ubluprdasv32v asterisk[77517]: segfault at 10 ip 00007fab000e60d5 sp 00007faa887676b8 error 4 in libpthread-2.17.so[7fab000da000+17000]
2020-11-16 15:08:20.366 ubluprdasv32v Process 9 (asterisk) of user 1001 killed by SIGSEGV - dumping core
```

If a whole core file tarball is needed for any of these, let me know.

> app_mixmonitor: Crash in AMI StopMixMonitor
> -------------------------------------------
>
>                 Key: ASTERISK-29134
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29134
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_mixmonitor
>    Affects Versions: 17.7.0
>            Reporter: Joshua Elson
>            Assignee: Unassigned
>            Severity: Minor
>         Attachments: asterisk-core-20201019-112326-brief.txt, asterisk-core-20201019-112326-full.txt, asterisk-core-20201019-112326-info.txt, asterisk-core-20201019-112326-locks.txt, asterisk-core-20201019-112326-thread1.txt, asterisk-core-20201110-154106-brief.txt, asterisk-core-20201110-154106-full.txt, asterisk-core-20201110-154106-info.txt, asterisk-core-20201110-154106-locks.txt, asterisk-core-20201110-154106-thread1.txt, mmlog, mmlog.txt
>
>
> Seeing a new crash that is occurring occasionally when issuing an out of band StopMixMonitor via AMI on a channel that is recording a call.
> Don't have a complete repro scenario, but looking to see if I can generate one.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list