[debian-mysql] Bug#664639: mysql and logging

Bjoern Boschman bjoern at boschman.de
Mon Jul 16 10:26:15 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Nicholas,

the basic problem can be reproduced as follows:

configure error logging:

[mysqld]
log-error = /var/log/mysql/error.log

and restart mysql-server

chown root /var/log/mysql/error.log
mysqladmin --defaults-file=/etc/mysql/debian.cnf flush-logs
mysqladmin: refresh failed; error: 'Unknown error'


The problem seems to be related in mysqld_safe which under some
circumstances creates the log-error file with root as file owner.

I definately did not do this on purpose, but it might come from on
older 5.1 installation.

When you manually fix the file-owner (chown mysql
/var/log/mysql/error.log ) the problem disappers.

- -snip-
regarding mysqld startup:

the SVN/experimental fix is basically :ugly:
from some discussion on the #mysql.de channel I very likely believe we
should not be using mysqld_safe at all, but start the mysqld process
directly.
Unfortunatelly I did not find the time to write a proposal for an
updated init-script yet :(

- -snip_
regarding logrotate:

problem with logrotate basically is that we do not have any clue which
logfiles will be created as this information comes from the mysqld config.
- From the distributed my.cnf no logging is done at all.

I'll get back to you @IRC as soon as my employee will leave me some
time to do so ;-)


Cheers
B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAD7EcACgkQABMWRpwdNulOwACfQjwRrVf5FoVHNd9YE58g0pX8
O1cAoMvqld1iAgq7lhE0soh++q2NDdSc
=IqZp
-----END PGP SIGNATURE-----



More information about the pkg-mysql-maint mailing list