Add a documentation troubleshooting note for MySQL/MariaDB authentication errors (#399).

This commit is contained in:
Dan Helfman 2023-06-15 14:55:57 -07:00
parent bbc7f0596c
commit 9152fed249
2 changed files with 7 additions and 0 deletions

1
NEWS
View file

@ -1,4 +1,5 @@
1.7.15.dev0 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 * #697: Extract borgmatic configuration from backup via "bootstrap" action—even when borgmatic
has no configuration yet! has no configuration yet!
* #669: Add sample systemd user service for running borgmatic as a non-root user. * #669: Add sample systemd user service for running borgmatic as a non-root user.

View file

@ -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) [pg_hba.conf](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html)
file for that configuration. 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 ### MySQL table lock errors