![](https://secure.gravatar.com/avatar/01d86d32e4a72ce9ecd34dba70b74cc4.jpg?s=120&d=mm&r=g)
Hi Ken, This happens because the `/var/log/mysql` directory is in principle for error and slow logs, binary logs usually go under `/var/lib/mysql` or whatever the datadir is. You can configure a separate dir in some specific cases, but in most cases you can just specify: `log-bin` in the config without any arguments and it will create the binary logs in your datadir. Hope that helps. -GL Le sam. 17 févr. 2024 à 03:42, Ken Wright via discuss < discuss@lists.mariadb.org> a écrit :
On Fri, 2024-02-16 at 00:44 -0500, Ken Wright via discuss wrote:
On Fri, 2024-02-16 at 14:44 +1100, Daniel Black via discuss wrote:
Hi Ken,
Under what group heading are you adding log-bin? Something like [mariadb]?
Just checked. The heading is [mysqld]
If you have an explicit error-log file configured? What is the content on the restart.
I see the following error line in journalctl:
[ERROR] mariadbd: File '/var/log/mysql/master-bin.index' not found (Errcode: 13 "Permission denied")
I had to mkdir the /var/log/mysql/ directory, and it's owned by root:root, with write permission only for the owner. Should I chown to a different user?
Bad form, replying to myself. I checked, and tried chowning the /var/log/mysql/ directory to mysql:mysql. Now it works. Thanks for pointing me in the right direction!
Ken -- If you ever think international affairs make sense, remember this: because a Serb shot an Austrian in Bosnia, Germany invaded Belgium. _______________________________________________ discuss mailing list -- discuss@lists.mariadb.org To unsubscribe send an email to discuss-leave@lists.mariadb.org