[asterisk-bugs] [JIRA] (ASTERISK-27026) res_ari: Crash when no ari.conf configuration file exists

George Joseph (JIRA) noreply at issues.asterisk.org
Thu Jul 6 07:08:04 CDT 2017


     [ https://issues.asterisk.org/jira/browse/ASTERISK-27026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Joseph updated ASTERISK-27026:
-------------------------------------

    Target Release Version/s: 13.17.0

> res_ari: Crash when no ari.conf configuration file exists
> ---------------------------------------------------------
>
>                 Key: ASTERISK-27026
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27026
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari
>    Affects Versions: 14.5.0
>         Environment: Debian 8 Jessie / Raspberry Pi (armhf)
>            Reporter: Ronald Raikes
>            Assignee: George Joseph
>            Severity: Minor
>      Target Release: 13.17.0
>
>         Attachments: backtrace.txt, Core.zip
>
>
> Asterisk 13.16.0 and 14.5.0 cause FreePBX 13 and FreePBX 14 to repeatedly crash.  No crashes occur using any previous versions of Asterisk.  Core dump files are created at the rate of approximately 3 per minute as Asterisk restarts (core.zip attached).  During FreePBX installation using Asterisk 13.16.0 or 14.5.0, the following is reported:
> Asterisk Started
> Reloading FreePBX
> Error(s) have occured, the following is the retrieve_conf output:
> exit: 1
> Exception: Unable to connect to Asterisk Manager from /var/lib/asterisk/bin/retrieve_conf, aborting in file /var/lib/asterisk/bin/retrieve_conf on line 11
> Stack trace:
>   1. Exception->() /var/lib/asterisk/bin/retrieve_conf:11
> No problems occur using any earlier version of Asterisk.
> I first reported this to Sangoma, but was advised by Andrew Nagy:
> "This should be reported to Digium since it's their code crashing. FreePBX is not causing your crashes, if something that freepbx is writing out is crashing Asterisk then this should still be reported to Asterisk because they should stop it from happening."



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



More information about the asterisk-bugs mailing list