Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mysql issue #80

Open
abhinavsharma95 opened this issue May 16, 2024 · 1 comment
Open

Mysql issue #80

abhinavsharma95 opened this issue May 16, 2024 · 1 comment

Comments

@abhinavsharma95
Copy link

It has issue while connecting with mysql -

2024-05-16T06:16:55.954289Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-05-16T06:16:56.255807Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.3.0) starting as process 1
2024-05-16T06:16:56.276267Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-05-16T06:16:56.497781Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
mysqld: Table 'mysql.plugin' doesn't exist
2024-05-16T06:16:56.644462Z 0 [ERROR] [MY-010735] [Server] Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.
2024-05-16T06:16:56.644913Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-05-16T06:16:56.645155Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-05-16T06:16:56.645392Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-05-16T06:16:56.645723Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-05-16T06:16:56.645920Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-05-16T06:16:56.646115Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-05-16T06:16:56.646379Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-05-16T06:16:56.700666Z 0 [Warning] [MY-010015] [Repl] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2024-05-16T06:16:56.731789Z 0 [Warning] [MY-010015] [Repl] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2024-05-16T06:16:56.736290Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-05-16T06:16:56.736331Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-05-16T06:16:56.739345Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2024-05-16T06:16:56.739779Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-05-16T06:16:56.740062Z 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001146 - Table 'mysql.component' doesn't exist

@arnediekmann
Copy link
Member

Hi @abhinavsharma95, I just pushed a fix that should triage the problem. Before upgrading the helm release, make sure that the MySQL PVC is deleted. I.e.

$ kubectl scale sts mgnl-mysql --replicas=0
$ kubectl delete pvc mysql-persistent-storage-mgnl-mysql-0
$ kubectl scale sts mgnl-mysql --replicas=1

However, there also seems to be a problem with some dependencies in the CE builds, as far as I can tell. I created the issue #82 to track that, and will close that one once the Docker images have been updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants