[asterisk-bugs] [JIRA] (ASTERISK-29846) channels: bad ao2 ref causes crash

N A (JIRA) noreply at issues.asterisk.org
Tue Mar 29 19:37:07 CDT 2022


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

N A commented on ASTERISK-29846:
--------------------------------

Ah, and t'was there the rub:

{noformat}
[976049.815002] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/cron.service,task=asterisk,pid=18565,uid=1004
[976049.818972] Out of memory: Killed process 18565 (asterisk) total-vm:842964kB, anon-rss:214332kB, file-rss:0kB, shmem-rss:0kB, UID:1004 pgtables:872kB oom_score_adj:0
[976049.973479] oom_reaper: reaped process 18565 (asterisk), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
{noformat}

So that would explain it all, as you said... Asterisk is causing the system to run out of memory, or at least is the most memory-intensive application at such a time.

I will try adding some more swap and see how that goes. In any case, at least the mystery of the missing backtraces is solved - thanks for that tip!

Back on the original subject of this thread, the PJSIP issue that causes that assert every now and then still happens occasionally. I imagine with DO_CRASH, that *would* cause a crash.
So this issue can remain open for that at this point, I think.

> channels: bad ao2 ref causes crash
> ----------------------------------
>
>                 Key: ASTERISK-29846
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29846
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 18.9.0
>         Environment: Debian 10
>            Reporter: N A
>            Assignee: N A
>         Attachments: core-asterisk-2022-02-01T17-04-52Z-brief.txt, core-asterisk-2022-02-01T17-04-52Z-full.txt, core-asterisk-2022-02-01T17-04-52Z-info.txt, core-asterisk-2022-02-01T17-04-52Z-locks.txt, core-asterisk-2022-02-01T17-04-52Z-thread1.txt, core-asterisk-2022-02-10T00-46-55Z-full.txt
>
>
> Currently, Asterisk crashes randomly every few days, not seemingly linked to anything going on at the moment. In fact, prior to this crash, the system was completely idle (no calls) for the previous 34 minutes.
> Here is a backtrace from right before the last crash, useful as it has line numbers:
> 01:35:03 ERROR[13076] : Got 10 backtrace records
> # 0: [0x55ca492928cc] asterisk utils.c:2727 __ast_assert_failed()
> # 1: [0x55ca49109db3] asterisk astobj2.c:212 log_bad_ao2()
> # 2: [0x55ca4910a73a] asterisk astobj2.c:501 __ao2_ref()
> # 3: [0x55ca4917269a] asterisk cli.c:1218 handle_chanlist()
> # 4: [0x55ca4917859f] asterisk cli.c:3020 ast_cli_command_full()
> # 5: [0x55ca49178734] asterisk cli.c:3048 ast_cli_command_multiple_full()
> # 6: [0x55ca49101e0c] asterisk asterisk.c:1424 netconsole()
> # 7: [0x55ca4928fb57] asterisk utils.c:1572 dummy_start()
> # 8: [0x7f257c305fa3] libpthread.so.0 pthread_create.c:487 start_thread()
> # 9: [0x7f257bd994cf] libc.so.6 clone.S:97 clone()



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



More information about the asterisk-bugs mailing list