Bug#922018: [debian-mysql] Bug#922018: mariadb-server-10.3: Logs are not in /var/lib/mysql
Hello! If this issue is still relevant, and you have a suggestion how to fix it, please file a Merge Request on Salsa as a proposal. Thanks! https://wiki.debian.org/Teams/MySQL/patches
Bug#922018: [debian-mysql] Bug#922018: mariadb-server-10.3: Logs are not in /var/lib/mysql
Hi Olaf! Since there has not been any change on the mysql_install_db.sh script regarding this for long, I thought that such output message was normal and that the error log would be as it says in /var/lib/mysql. But on Debian it is not and you are right, error log goes to /var/log/mysql/error.log. The following permits to confirm this behavior (WARNING this delete mariadb data): 1/ in a first terminal: $ sudo rm -rf /var/lib/mysql/* $ sudo -u mysql mysql_install_db 2/ in a second terminal (quickly after this last command): $ sudo chown -R root:root /var/lib/mysql/mysql The last command makes the creation of MariaDB Server system table fail because mysql_install_db can't write into /var/lib/mysql/mysql and error log goes to /var/log/mysql/error.log I will open an issue on Jira and link this bug report to it. Thanks again, Faustin
Bug#922018: [debian-mysql] Bug#922018: mariadb-server-10.3: Logs are not in /var/lib/mysql
Op di 12 feb. 2019 om 18:13 schreef Faustin Lammler : > > Olaf, > It seems that in this case, the error log should indeed be in the > datadir ($ldata -> /var/lib/mysql). > > I have double checked and this behavior is the same since 10.1 (Debian > or upstream). > > See: > https://salsa.debian.org/mariadb-team/mariadb-10.1/blob/master/scripts/mysql_install_db.sh#L489 > https://salsa.debian.org/mariadb-team/mariadb-10.3/blob/master/scripts/mysql_install_db.sh#L511 > https://github.com/MariaDB/server/blob/10.1/scripts/mysql_install_db.sh#L499 > https://github.com/MariaDB/server/blob/10.3/scripts/mysql_install_db.sh#L511 Hi Faustin, I'm sure not what point you're trying to make. What does `ls -l /var/log/mysql` return on your system? # ls -l /var/log/mysql total 28 -rw-r- 1 mysql adm0 Feb 15 00:00 error.log -rw-r- 1 mysql adm 20 Feb 14 12:09 error.log.1.gz -rw-r- 1 mysql adm 978 Feb 14 12:09 error.log.2.gz -rw-r- 1 mysql adm 20 Feb 12 00:00 error.log.3.gz -rw-r- 1 mysql adm 20 Feb 11 09:39 error.log.4.gz -rw-r- 1 mysql adm 933 Feb 11 09:39 error.log.5.gz -rw-r- 1 mysql adm 20 Feb 4 12:05 error.log.6.gz -rw-r- 1 mysql adm 1117 Feb 4 12:05 error.log.7.gz -- Olaf
Bug#922018: [debian-mysql] Bug#922018: mariadb-server-10.3: Logs are not in /var/lib/mysql
Olaf, It seems that in this case, the error log should indeed be in the datadir ($ldata -> /var/lib/mysql). I have double checked and this behavior is the same since 10.1 (Debian or upstream). See: https://salsa.debian.org/mariadb-team/mariadb-10.1/blob/master/scripts/mysql_install_db.sh#L489 https://salsa.debian.org/mariadb-team/mariadb-10.3/blob/master/scripts/mysql_install_db.sh#L511 https://github.com/MariaDB/server/blob/10.1/scripts/mysql_install_db.sh#L499 https://github.com/MariaDB/server/blob/10.3/scripts/mysql_install_db.sh#L511 Faustin
Bug#922018: [debian-mysql] Bug#922018: mariadb-server-10.3: Logs are not in /var/lib/mysql
Olaf, yes this is true but your output comes from the mysql_install_db.sh install script (not from mariadb server itself). I can't see any change between 10.1 and 10.3 version (and 10.4 upstream version) regarding this behavior, let me dig a bit more and check if this is normal. Faustin
Bug#922018: [debian-mysql] Bug#922018: mariadb-server-10.3: Logs are not in /var/lib/mysql
Hi Olaf! Thanks for your report. Can I ask you what steps leads to this? Regards, Faustin
Bug#922018: [debian-mysql] Bug#922018: mariadb-server-10.3: Logs are not in /var/lib/mysql
Hi again, I have just checked and this seems to be the default directory for the error log: https://mariadb.com/kb/en/library/overview-of-mariadb-logs/ > The error log > > - Always enabled > - Usually a file in the data directory, but some distributions may > move this to other locations. - All critical errors are logged > here. > - One can get warnings to be logged by setting log_warnings. > - With the mysqld_safe --syslog option one can duplicate the > messages to the system's syslog. Faustin
Bug#922018: [debian-mysql] Bug#922018: mariadb-server-10.3: Logs are not in /var/lib/mysql
Op ma 11 feb. 2019 om 16:06 schreef Faustin Lammler : > I have just checked and this seems to be the default directory > for the error log: > https://mariadb.com/kb/en/library/overview-of-mariadb-logs/ Debian has log_error = /var/log/mysql/error.log -- Olaf
Bug#922018: [debian-mysql] Bug#922018: mariadb-server-10.3: Logs are not in /var/lib/mysql
Op ma 11 feb. 2019 om 16:02 schreef Faustin Lammler : > Can I ask you what steps leads to this? apt upgrade I think, from 10.1 to 10.3, with enable-large-prefix in a conf file. Note it's not about the failure itself, it's about the text being wrong about the location of logs. -- Olaf