| Summary: | ASTERISK-28844: samples: Start and Reload are blathering. | ||
| Reporter: | Alexander Traud (traud) | Labels: | |
| Date Opened: | 2020-04-19 07:31:39 | Date Closed: | |
| Priority: | Trivial | Regression? | |
| Status: | Open/New | Components: | Configs/Samples |
| Versions: | 13.32.0 16.9.0 17.3.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Ubuntu 20.04 LTS | Attachments: | |
| Description: | After installing the minimum dependencies, configuring, building and installing the samples on Ubuntu 20.04 LTS, Asterisk gives me at start:
{code} NOTICE: loader.c:2377 int load_modules(void): 251 modules will be loaded. [ Initializing Custom Configuration Options ] NOTICE: cdr.c:4504 int cdr_toggle_runtime_options(void): CDR simple logging enabled. NOTICE: res_smdi.c:1424 int load_module(void): No SMDI interfaces are available to listen on, not starting SMDI listener. WARNING: res_phoneprov.c:1232 struct varshead *get_defaults(void): Unable to find a valid server address or name. NOTICE: chan_skinny.c:8451 int config_load(void): Configuring skinny from skinny.conf SIP channel loading... ERROR: ari/config.c:312 int process_config(int): No configured users for ARI NOTICE: confbridge/conf_config_parser.c:2342 int verify_default_profiles(void): Adding default_menu menu to app_confbridge NOTICE: cel_custom.c:95 int load_config(void): No mappings found in cel_custom.conf. Not logging CEL to custom CSVs. {code} and on reload: {code} NOTICE: cdr.c:4504 int cdr_toggle_runtime_options(void): CDR simple logging enabled. WARNING: res_phoneprov.c:1232 struct varshead *get_defaults(void): Unable to find a valid server address or name. NOTICE: chan_skinny.c:8451 int config_load(void): Configuring skinny from skinny.conf ERROR: ari/config.c:312 int process_config(int): No configured users for ARI NOTICE: cel_custom.c:95 int load_config(void): No mappings found in cel_custom.conf. Not logging CEL to custom CSVs. NOTICE: app_queue.c:9119 int reload_queue_rules(int): queuerules.conf has not changed since it was last loaded. Not taking any action. {code} Although a lot was done in the past, that is still too much and is going to confuse novice users. This is a report for the Software Usability Engineer at Sangoma / Digium. Please, take over and negotiate with the module owners whether lowering (ERROR → WARNING → NOTICE → VERBOSE → DEBUG) is not possible. The behavior is not uniform over the various modules although from the point of Asterisk in general many are equal and should report in the same manner, for example if every module would be have like _app_queue_ … | ||
| Comments: | By: Asterisk Team (asteriskteam) 2020-04-19 07:31:39.918-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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Joshua C. Colp (jcolp) 2020-04-19 08:20:52.663-0500 There is no individual at Sangoma whose role is that. As well only a few modules have owners, the rest are maintained by us all based on the changes and contributions we make. This is reflected in the log level usage. This has evolved over time and also can sometimes depend on the opinion of the individual who wrote or added code to the module. We try for new code to ensure it makes sense, but few have gone back to old modules to try to improve or alter them. By: Joshua C. Colp (jcolp) 2020-04-19 08:21:31.491-0500 If you'd like to take this on as a project then that is certainly possible, otherwise it will go into the Sangoma team queue but there is no time frame on when such a thing would get looked into. | ||