[asterisk-bugs] [JIRA] (ASTERISK-26162) config: Unable to load config file log level inconsistency.

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-26162:
-----------------------------------

    Summary: config: Unable to load config file log level inconsistency.  (was: config_options.c: needless use of ERROR log level in some cases)

> config: Unable to load config file log level inconsistency.
> -----------------------------------------------------------
>
>                 Key: ASTERISK-26162
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26162
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Configuration
>    Affects Versions: 13.9.1
>         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
>            Reporter: Early Bird
>            Severity: Trivial
>
> 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?



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