You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll add to this that when icingaweb.config.global.config_backend is not set, the entrypoint skips initializing the database schema because the array of backend resources will be empty.
In our case, we connect to a MySQL server using user/pass, but have also set use_ssl to 1 and set ssl_ca to the path to the DB server root CA. This works fine for Icinga Web, but when icingaweb.config.global.config_backend is set, the entrypoint will crash with this error:
ERROR: ErrorException in /usr/share/icingaweb2/modules/setup/library/Setup/Utils/DbTool.php:323 with message: Undefined array key "ssl_key"
Shouldn't we be able to communicate with the database with SSL without using mTLS auth, or am I misunderstanding something?
The two separate issues here are that the container entrypoint requires config_backend to be set to initialize schema, but then Icinga Web setup seems to require every ssl option to be set.
What we're doing as a workaround for now is set icingaweb.config.global.config_resource, but skip icingaweb.config.global.config_backend and initialize the database schema manually.
The usage example lists the following line
which has been deprecated by now as far as I can tell (according to the documentation).
Result (/etc/icingaweb2/config.ini):
This seems to simply be ignored in practice. However it might also be a good idea to also get rid off it here.
The text was updated successfully, but these errors were encountered: