[asterisk-bugs] [JIRA] (ASTERISK-25424) asterisk.conf syntax error causes inscrutable crash

[Rusty Newton (JIRA)]

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

Rusty Newton edited comment on ASTERISK-25424 at 9/30/15 5:46 PM:
------------------------------------------------------------------

{quote}
(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.
{quote}
Template syntax is documented here: https://wiki.asterisk.org/wiki/display/AST/Templates

I believe it also documented in a few sample configuration files.

{quote}
(2) Config file syntax errors should provide a meaningful error message; this is a basic principle of system design.
{quote}

For sure and typically they do. Obviously a crash like the one you encountered was not by design.


Unfortunately I cannot reproduce your crash and I don't understand the report exactly.

In the Asterisk 13.5.0 source the asterisk.conf sample file first line shows as:
{noformat}
[directories](!)
{noformat}

I cannot reproduce a crash with this line or by using the line you describe having after your installation.

Do you have any further detail on how the crash can be reproduced?




was (Author: rnewton):
{quote}
(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.
{quote}
Template syntax is documented here: https://wiki.asterisk.org/wiki/display/AST/Templates

I believe it also documented in a few sample configuration files.

{quote}
(2) Config file syntax errors should provide a meaningful error message; this is a basic principle of system design.
{quote}

For sure and typically they do. Obviously a crash like the one you encountered was not by design.


Unfortunately I cannot reproduce your crash and I don't understand the report exactly.

In the Asterisk 13.5.0 source the asterisk.conf sample file first line shows as:
{noformat}
[directories](!)
{nofromat}

I cannot reproduce a crash with this line or by using the line you describe having after your installation.

Do you have any further detail on how the crash can be reproduced?



> 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: Norman Henderson
>            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)