These lines are always showing even if log_level is set to INFO

[goldyfruit]

2023-05-13 20:57:05.191 - OVOS - ovos_config.models:load_local:105 - DEBUG - Configuration /home/ovos/.venv/lib/python3.11/site-packages/ovos_config/mycroft.conf loaded
2023-05-13 20:57:05.213 - OVOS - ovos_config.models:load_local:111 - DEBUG - Configuration '/etc/mycroft/mycroft.conf' not defined, skipping
2023-05-13 20:57:05.246 - OVOS - ovos_config.models:load_local:105 - DEBUG - Configuration /home/ovos/.config/mycroft/web_cache.json loaded
2023-05-13 20:57:05.278 - OVOS - ovos_config.models:load_local:111 - DEBUG - Configuration '/home/ovos/.config/mycroft/mycroft.conf' not defined, skipping
2023-05-13 20:57:05.307 - OVOS - ovos_config.models:load_local:111 - DEBUG - Configuration '/etc/xdg/mycroft/mycroft.conf' not defined, skipping
2023-05-13 20:57:05.337 - OVOS - ovos_config.models:load_local:111 - DEBUG - Configuration '/home/ovos/.mycroft/mycroft.conf' not defined, skipping

[j1nx]

Saw them as well, but guess we will always see them as it is the code that opens and reads the config files. It needs them to read and set the log level so guess they will always been shown as it does not know the log level yet at that point.

think removing the DEBUG word from it is all they can do.

[goldyfruit]

The thing is that we see these messages as well when running any ovos-* command, example with ovos-speak:

2023-05-13 20:57:02.533 - OVOS - ovos_config.models:load_local:105 - DEBUG - Configuration /home/ovos/.venv/lib/python3.11/site-packages/ovos_config/mycroft.conf loaded
2023-05-13 20:57:02.557 - OVOS - ovos_config.models:load_local:111 - DEBUG - Configuration '/etc/mycroft/mycroft.conf' not defined, skipping
2023-05-13 20:57:02.585 - OVOS - ovos_config.models:load_local:105 - DEBUG - Configuration /home/ovos/.config/mycroft/web_cache.json loaded
2023-05-13 20:57:02.617 - OVOS - ovos_config.models:load_local:111 - DEBUG - Configuration '/home/ovos/.config/mycroft/mycroft.conf' not defined, skipping
2023-05-13 20:57:02.638 - OVOS - ovos_config.models:load_local:111 - DEBUG - Configuration '/etc/xdg/mycroft/mycroft.conf' not defined, skipping
2023-05-13 20:57:02.660 - OVOS - ovos_config.models:load_local:111 - DEBUG - Configuration '/home/ovos/.mycroft/mycroft.conf' not defined, skipping
2023-05-13 20:57:02.816 - OVOS - ovos_bus_client.conf:load_message_bus_config:19 - INFO - Loading message bus configs
2023-05-13 20:57:02.819 - OVOS - ovos_bus_client.session:reset_default_session:186 - INFO - New Default Session Start: 90a516a4-3d6a-4880-92b5-818609bc48b2
2023-05-13 20:57:02.821 - OVOS - ovos_bus_client.client.client:on_open:85 - INFO - Connected

[NeonDaniel]

Yeah; those logs print before configuration is loaded, so they aren't yet accounting for that config value.. Not sure the best answer here because they are useful/necessary for debugging configuration issues

[JarbasAl]

We can add a env var to allow setting this before launch for default value