Closed cjohnston1158 closed 1 week ago
@cjohnston1158 Thanks for the report - I can't reproduce it locally still. But i think that's a transient issue and the solution is two fold:
While I am at it, if you see it again, please capture the /var/log/mysql/error.log
inside the mysql
container for the pod. I just wan't to be sure the daemon is starting correctly and it's a matter of time.
-> Start:
2024-06-28T19:01:38.801074Z mysqld_safe Logging to '/var/log/mysql/error.log'.
--> ready:
2024-06-28T19:02:13.139958Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.36-0ubuntu0.22.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu).
Currently we are waiting 30s to have socket connection. From the logs it's clear that it's taking longer (~35s) which is triggering the initial hook failure. Fix is on the way
Steps to reproduce
Deploying sunbeam using the multi-node maas instructions.
Expected behavior
No error
Actual behavior
Versions
cinder-mysql-0-charm.log cinder-mysql-0-describe.txt cinder-mysql-0-mysql.log