)]}'
{"inventory/group_vars/galera_all.yml":[{"author":{"_account_id":29239,"name":"Mikael Loaec","email":"mikael.loaec@inra.fr","username":"miloa"},"change_message_id":"45872c037150f8327e170dd2587890468d7087b6","unresolved":false,"context_lines":[{"line_number":14,"context_line":"# limitations under the License."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"galera_server_bind_address: \"{{ management_address }}\""},{"line_number":17,"context_line":"galera_wsrep_cluster_bind_address: \"{{ management_address }}\""},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"galera_client_drop_config_file: true"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-yaml","patch_set":19,"id":"7faddb67_a3609b36","line":17,"updated":"2019-09-03 21:49:49.000000000","message":"I think (not 100%sure) that If you set the galera bind address to container address, when user monitoring try to connect to localhost, it can not. Because it exclusively listen on container_address not localhost.\n\nAnd in the mariadb logs there is a warning when monitoring user trying to connect to localhost.\n\nI had very similar error in ansible logs and mariadb logs when deploying without specifying (or wrongly specifying) the galera_monitoring_allowed_source. Because user monitoring could not connect. It\u0027s not exactly the same problem but seems to be similar.","commit_id":"034084a01a545e86a18f82ea2cc6ec513bd23822"}]}