mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 06:55:53 +03:00
[GH-ISSUE #717] Mysql 8 support #515
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#515
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RonRademaker on GitHub (Oct 17, 2022).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/717
Is it possible to run healthchecks with MySQL8? When running the docker setup, it'll crash with this message:
This seems to be related to the new password hashing implementation in MySQL 8
@cuu508 commented on GitHub (Oct 18, 2022):
Yes, it should work. We're using the Django framework, and Django has official MySQL support.
Just tested the following on Ubuntu 22.04:
mysql-server-8.0)foo, created a database:DATABASESkey inlocal_settings.py:At this point I could run
manage.py migratewith no errors.@cuu508 commented on GitHub (Oct 18, 2022):
Ah, but I get the same error when using the Docker image. Will look into this!
@cuu508 commented on GitHub (Oct 18, 2022):
Looks like there isn't a quick, easy solution. The problem, as I understand it:
default-libmysqlclient-devdepends onlibmariadb-dev-compatOne experiment, to illustrate:
Here we don't have Healthchecks, Django, or mysqlclient-python in the mix, but still get the same error.
Possible fixes:
A workaround that should work for now: alter the database user to use the
mysql_native_passwordauthentication method:@cuu508 commented on GitHub (Oct 18, 2022):
I've released v2.4.1, and pushed updated docker images. It should fix the MySQL 8 connection issue.
@RonRademaker commented on GitHub (Oct 20, 2022):
Thanks for the quick response and solution!