[asterisk-bugs] [Asterisk 0018124]: Non-existent include in extensions.conf halts processing of conf file
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Oct 12 16:38:08 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=18124
======================================================================
Reported By: n8ideas
Assigned To: qwell
======================================================================
Project: Asterisk
Issue ID: 18124
Category: Core/Configuration
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Asterisk Version: 1.6.2.13
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2010-10-12 16:24 CDT
Last Modified: 2010-10-12 16:38 CDT
======================================================================
Summary: Non-existent include in extensions.conf halts
processing of conf file
Description:
Reproduced on Asterisk 1.6.2.13:
An invalid include in the extensions.conf file will halt processing of the
file. Includes below the non-existent one will not be included. I'll
include a reproducible example on a FreePBX installation.
For example:
extensions_custom.conf (itself an include of extensions.conf) contains:
#include /opt/isymphony/server/isymphony.conf
#include extensions_dynagents.conf
[from-internal-custom]
exten => 1234,1,Answer()
exten => 1234,n,Milliwatt()
On this box, the isymphony.conf file does not exist. The
extensions_dynagents.conf does exist.
In this case, config will simply ignore everything below the invalid
include.
In the full log, the following error is thrown:
ERROR[8818] config.c: The file '/opt/isymphony/server/isymphony.conf' was
listed as a #include but it does not exist.
None of the code below the invalid include is processed, including the
contexts and the include below it.
Barring I use case I haven't considered, I would expect the error should
be thrown as it is currently, but I would prefer that the configuration
file continues to be processed assuming it is valid syntactically.
I haven't investigated a fix, but if people concur, I would be willing to
produce a patch.
======================================================================
----------------------------------------------------------------------
(0127917) qwell (administrator) - 2010-10-12 16:38
https://issues.asterisk.org/view.php?id=18124#c127917
----------------------------------------------------------------------
This is intentional. There could be serious damage done if there is a typo
in your config and we continue as if nothing happened.
Issue History
Date Modified Username Field Change
======================================================================
2010-10-12 16:38 qwell Note Added: 0127917
2010-10-12 16:38 qwell Status new => resolved
2010-10-12 16:38 qwell Resolution open => fixed
2010-10-12 16:38 qwell Assigned To => qwell
2010-10-12 16:38 qwell Status resolved => closed
======================================================================
More information about the asterisk-bugs
mailing list