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

Kevin Harwell (JIRA) noreply at issues.asterisk.org
Thu Mar 24 11:01:07 CDT 2022


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

Kevin Harwell commented on ASTERISK-29846:
------------------------------------------

{quote}
I have a cron job that runs every 5 minutes that executes asterisk -rx "core show channels", and if it fails, it runs cd /var/crash && asterisk -g (the g is theoretically redundant, since I have the dump core option in asterisk.conf, but I'm not taking any chances...)
{quote}
Just trying to think of anything here, but how does the script know the call fails? And if it does recognize some failure how does it know Asterisk itself is not running/executing still? Guessing it's checking for the PID?

Before starting Asterisk does the script check to see if Asterisk is not actually running (still running or restarted by something else)? Could it be possible the script is messing up and starting multiple instances of Asterisk? That could potentially cause odd behavior if so.

> 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: Unassigned
>         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