From 9152fed249322f06343bda93984bac262d2012db Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Thu, 15 Jun 2023 14:55:57 -0700 Subject: [PATCH] Add a documentation troubleshooting note for MySQL/MariaDB authentication errors (#399). --- NEWS | 1 + docs/how-to/backup-your-databases.md | 6 ++++++ 2 files changed, 7 insertions(+) diff --git a/NEWS b/NEWS index 8c5480fe..6f230e43 100644 --- a/NEWS +++ b/NEWS @@ -1,4 +1,5 @@ 1.7.15.dev0 + * #399: Add a documentation troubleshooting note for MySQL/MariaDB authentication errors. * #697: Extract borgmatic configuration from backup via "bootstrap" action—even when borgmatic has no configuration yet! * #669: Add sample systemd user service for running borgmatic as a non-root user. diff --git a/docs/how-to/backup-your-databases.md b/docs/how-to/backup-your-databases.md index 3aeea9b1..fea3f350 100644 --- a/docs/how-to/backup-your-databases.md +++ b/docs/how-to/backup-your-databases.md @@ -410,6 +410,12 @@ authenticated. For instance, with PostgreSQL, check your [pg_hba.conf](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html) file for that configuration. +Additionally, MySQL/MariaDB may be picking up some of your credentials from a +defaults file like `~/.my.cnf`. If that's the case, then it's possible +MySQL/MariaDB ends up using, say, a username from borgmatic's configuration +and a password from `~/.my.cnf`. This may result in authentication errors if +this combination of credentials is not what you intend. + ### MySQL table lock errors