find /etc/mysql
/etc/mysql
/etc/mysql/debian.cnf
/etc/mysql/my.cnf
/etc/mysql/my.cnf.fallback
/etc/mysql/mysql.cnf
/etc/mysql/mysql.conf.d
/etc/mysql/mysql.conf.d/mysqld.cnf
/etc/mysql/mysql.conf.d/mysql.cnf
/etc/mysql/mysql.conf.d/mysqld_safe_syslog.cnf
/etc/mysql/conf.d
/etc/mysql/conf.d/mysql.cnf
/etc/mysql/conf.d/mysqldump.cnf
/etc/mysql/debian-start
I see, it’s in /etc/mysql/mysql.conf.d/mysqld.cnf
. These configs really are tedious!
I updated bind-address = 127.0.0.1
→ bind-address = 0.0.0.0
in mysqld.cnf
, and restarted mysql, however I’m still running into the same error when the mattermost pod starts up:
{"timestamp":"2022-07-26 17:59:45.908 -05:00","level":"info","msg":"Pinging SQL","caller":"sqlstore/store.go:262","database":"master"}
{"timestamp":"2022-07-26 17:59:55.934 -05:00","level":"error","msg":"Failed to ping DB","caller":"sqlstore/store.go:272","error":"dial tcp REDACTED_PUBLIC_IP:3306: i/o timeout","retrying in seconds":10}