Just wondering if it’s normal to have a completely empty MySQL error.log file?
I thought it may have just been a slow day, but it appears to always be empty. I haven’t seen anything written to that file for weeks and the logrotate gz files are also empty.
The log file is here: /var/log/mysql/error.log
Looking at the mariadb config file from the HestiaCP (it uses this file: /etc/mysql/my.cnf) I can see the following line in that file:
log_error=/var/log/mysql/error.log
So as far as I can tell, I’m checking the correct log file, and that log file is empty, and the archived logrotate files are also showing empty.
Do I have some issue with the configuration for the log files or is it really running with 0 errors.
I waited for a while before posting this question, hoping to see some activity in those logs, but after several weeks, still empty.
Working as expected? Or anyway I can trigger an error to confirm it’s writing it?