[asterisk-bugs] [JIRA] (ASTERISK-25424) asterisk.conf syntax error causes inscrutable crash
Boris Rybalkin (JIRA)
noreply at issues.asterisk.org
Sun Mar 27 14:41:56 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230041#comment-230041 ]
Boris Rybalkin commented on ASTERISK-25424:
-------------------------------------------
OK, found a problem.
After running 'make basic-pbx' and checking what config it generates, I have found that the right format is to use arrows (=>).
{code}
[directories]
astetcdir => /opt/app/talk/config/asterisk
...
{code}
And the other problem was that astdatadir was pointing to wrong dir.
After fixing that everything worked as expected.
> asterisk.conf syntax error causes inscrutable crash
> ---------------------------------------------------
>
> Key: ASTERISK-25424
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25424
> Project: Asterisk
> Issue Type: Improvement
> Security Level: None
> Components: Core/Sorcery
> Affects Versions: 13.5.0
> Environment: Ubuntu 14.04. Freepbx 2.11.0.43. Previous system had been 12.04 and Asterisk 1.8.
> Reporter: Norman Henderson
> Assignee: Unassigned
> Severity: Minor
>
> After upgrade, I installed Asterisk 13.5.0 from source. I ended up with the following first line in asterisk.conf:
> {noformat}
> [directories];(!) ; remove the (!) to enable this
> This appears to have caused Asterisk to crash during startup with:
> == Parsing '/etc/asterisk/asterisk.conf': Found
> == Sorcery registered wizard 'bucket'
> == Sorcery registered wizard 'bucket_file'
> Cannot update type 'bucket' in module 'core' because it has no existing documentation!
> Failed to register 'bucket' object type in Bucket sorcery
> Failed: ast_bucket_init
> {noformat}
> Apparently the correct syntax from 13.5.0 asterisk.conf.dpkg-dist is
> {noformat}
> [directories](!)
> {noformat}
> (1) This syntax and its meaning or effect does not appear to be documented. Nor is there much relevant to the Sorcery / bucket issue in extensive searching - eventually I found one IRC comment in which an unrelated asterisk.conf error caused a similar crash.
> (2) Config file syntax errors should provide a meaningful error message; this is a basic principle of system design.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list