ASTERISK-26162: config: Unable to load config file log level inconsistency.

[Home]

Summary: ASTERISK-26162: config: Unable to load config file log level inconsistency.

Reporter: Early Bird (earlybird) Labels:

Date Opened: 2016-06-30 02:55:29 Date Closed:

Priority: Trivial Regression?

Status: Open/New Components: Core/Configuration

Versions: 13.9.1 Frequency of
Occurrence

Related
Issues:

Environment: Asterisk 13.9.1 built by ubuntu @ ip-10-180-228-22 on a x86_64 running Linux on 2016-06-28 07:20:24 UTC Ubuntu Xenial 16.04 Bundled pjproject Attachments:

Description: When starting, Asterisk outputs some ERROR-level log messages when some configuration files are missing, e.g.

{code}
[Jun 30 16:33:13] ERROR[25721] config_options.c: Unable to load config file 'cel.conf'
[Jun 30 16:33:13] ERROR[25721] res_sorcery_config.c: Unable to load config file 'pjproject.conf'
[Jun 30 16:35:34] ERROR[25886] config_options.c: Unable to load config file 'acl.conf'
[Jun 30 16:35:34] ERROR[25886] config_options.c: Unable to load config file 'udptl.conf'
{code}

CEL modules were not even loaded; ACL configuration was not attempted; and udptl was perfectly healthy with its default configuration values and without a config file. The PBX itself was perfectly functional; the ERROR log level does not seem to be justified here (it could pointlessly trigger log monitoring tools); nothing is failing hard.

On the other hand, other modules just issue a WARNING whenever they do not find their config file which seems more reasonable:

{code}
[Jun 30 16:32:47] WARNING[25651] ccss.c: Could not find valid ccss.conf file. Using cc_max_requests default
{code}

Perhaps the ERRORs for missing config files could be cleaned up or consolidated?

Comments: By: Asterisk Team (asteriskteam) 2016-06-30 02:55:30.233-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].