-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I get this in the log:
<9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - ALERT exited abnormally with [1] <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - #007/usr/bin/mysqladmin: refresh failed; error: 'Unknown error' <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - /etc/logrotate.d/mysql failed, probably because <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - the root acount is protected by password. <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - See comments in /etc/logrotate.d/mysql on how to fix this <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - error: error running non-shared postrotate script for /var/log/mysql/mysqld.log of '/var/log/mysql/mysqld.log ' <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - Reload syslog service..done
Those comments say:
# If the root user has a password you have to create a # /root/.my.cnf configuration file with the following # content: # # [mysqladmin] # password = <secret> # user= root # # where "<secret>" is the password. # # ATTENTION: This /root/.my.cnf should be readable ONLY # for root !
And I do have that file with the right permissions:
Telcontar:~ # l .my.cnf - -rw------- 1 root root 202 Mar 27 2011 .my.cnf
and they have the specified contents:
[mysqladmin] password = mypassword user= root
So, what happens? This has started right after the last mysql upgrade. Another bug?
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/17/2012 06:10 PM, Carlos E. R. wrote:
I get this in the log:
<9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - ALERT exited abnormally with [1] <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - #007/usr/bin/mysqladmin: refresh failed; error: 'Unknown error' <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - /etc/logrotate.d/mysql failed, probably because <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - the root acount is protected by password. <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - See comments in /etc/logrotate.d/mysql on how to fix this <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - error: error running non-shared postrotate script for /var/log/mysql/mysqld.log of '/var/log/mysql/mysqld.log ' <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - Reload syslog service..done
Those comments say:
# If the root user has a password you have to create a # /root/.my.cnf configuration file with the following # content: # # [mysqladmin] # password = <secret> # user= root # # where "<secret>" is the password. # # ATTENTION: This /root/.my.cnf should be readable ONLY # for root !
And I do have that file with the right permissions:
Telcontar:~ # l .my.cnf -rw------- 1 root root 202 Mar 27 2011 .my.cnf
and they have the specified contents:
[mysqladmin] password = mypassword user= root
So, what happens? This has started right after the last mysql upgrade. Another bug?
-- Cheers, Carlos E. R.
Must be... I can confirm on 11.4 and I too have the proper .my.cnf entries and settings:
[18:56 alchemy:~] # cat .my.cnf [mysqladmin] password = mypasswd user = root
[mysqldump] password = mypasswd user = root
[mysql] password = mypasswd user = root
[mysqlcheck] password = mypasswd user = root
I don't even have a guess as to why this started failing. The logrotate script is trying to run under mysqladmin, so your entry and the first entry above should be sufficient -- it has been for the last "how many?" years? This seems to be opensuse specific. With mysql 5.5.24-1, I do not see the same issue on Arch.
- -- David C. Rankin, J.D.,P.E.
Am 18.05.2012 01:10, schrieb Carlos E. R.:
I get this in the log:
<9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - ALERT exited abnormally with [1] <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - #007/usr/bin/mysqladmin: refresh failed; error: 'Unknown error' <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - /etc/logrotate.d/mysql failed, probably because <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - the root acount is protected by password. <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - See comments in /etc/logrotate.d/mysql on how to fix this <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - error: error running non-shared postrotate script for /var/log/mysql/mysqld.log of '/var/log/mysql/mysqld.log ' <9.4> 2012-05-17 22:19:14 Telcontar logrotate - - - Reload syslog service..done
Those comments say:
# If the root user has a password you have to create a # /root/.my.cnf configuration file with the following # content: # # [mysqladmin] # password = <secret> # user= root # # where "<secret>" is the password. # # ATTENTION: This /root/.my.cnf should be readable ONLY # for root !
And I do have that file with the right permissions:
Telcontar:~ # l .my.cnf -rw------- 1 root root 202 Mar 27 2011 .my.cnf
and they have the specified contents:
[mysqladmin] password = mypassword user= root
So, what happens? This has started right after the last mysql upgrade. Another bug?
maybe wrong permissions on /var/log/mysql/ directory.
try to change this to # chmod 750 /var/log/mysql/ and optional # chown mysql /var/log/mysql/
ciao paolo
-- Cheers, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-05-18 02:05, Paolo Pantò wrote:
maybe wrong permissions on /var/log/mysql/ directory.
try to change this to # chmod 750 /var/log/mysql/ and optional # chown mysql /var/log/mysql/
I do that, then I get another error:
Telcontar:~ # logrotate /etc/logrotate.d/mysql error: "/var/log/mysql" has insecure permissions. It must be owned and be writable by root only to avoid security problems. Set the "su" directive in the config file to tell logrotate which user/group should be used for rotation. Telcontar:~ #
WHAT!?
Telcontar:~ # l /var/log | grep mysql drwxr-x--- 2 mysql root 4096 May 17 22:19 mysql/ lrwxrwxrwx 1 root root 23 Jan 31 2010 mysqld.log -> ../lib/mysql/mysqld.log Telcontar:~ #
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
Am 18.05.2012 03:01, schrieb Carlos E. R.:
On 2012-05-18 02:05, Paolo Pantò wrote:
maybe wrong permissions on /var/log/mysql/ directory.
try to change this to # chmod 750 /var/log/mysql/ and optional # chown mysql /var/log/mysql/
I do that, then I get another error:
Telcontar:~ # logrotate /etc/logrotate.d/mysql error: "/var/log/mysql" has insecure permissions. It must be owned and be writable by root only to avoid security problems. Set the "su" directive in the config file to tell logrotate which user/group should be used for rotation. Telcontar:~ #
add su mysql mysql to your /etc/logrotate.d/mysql file:
... /var/log/mysql/mysqld.log { su mysql mysql # create 600 mysql mysql ...
depending on your opensuse and/or mysql version the owner.group setting may vary.
WHAT!?
Telcontar:~ # l /var/log | grep mysql drwxr-x--- 2 mysql root 4096 May 17 22:19 mysql/ lrwxrwxrwx 1 root root 23 Jan 31 2010 mysqld.log -> ../lib/mysql/mysqld.log Telcontar:~ #
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-05-18 11:36, Paolo Pantò wrote:
add su mysql mysql to your /etc/logrotate.d/mysql file:
... /var/log/mysql/mysqld.log { su mysql mysql # create 600 mysql mysql ...
Thanks. It appears to work, at least it runs silently (I don't know if the logs are rotated or not).
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/18/2012 08:17 AM, Carlos E. R. wrote:
On 2012-05-18 11:36, Paolo Pantò wrote:
add su mysql mysql to your /etc/logrotate.d/mysql file:
... /var/log/mysql/mysqld.log { su mysql mysql # create 600 mysql mysql ...
Thanks. It appears to work, at least it runs silently (I don't know if the logs are rotated or not).
Does anybody have an explanation why this was required after update?
- -- David C. Rankin, J.D.,P.E.
On Fri, May 18, 2012 at 09:14:25PM -0500, David C. Rankin wrote:
On 05/18/2012 08:17 AM, Carlos E. R. wrote:
On 2012-05-18 11:36, Paolo Pantò wrote:
add su mysql mysql to your /etc/logrotate.d/mysql file:
... /var/log/mysql/mysqld.log { su mysql mysql # create 600 mysql mysql ...
Thanks. It appears to work, at least it runs silently (I don't know if the logs are rotated or not).
Does anybody have an explanation why this was required after update?
And later report the bugzilla ID here too. Thanks.
Lars
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-05-19 22:15, Lars Müller wrote:
Does anybody have an explanation why this was required after update?
And later report the bugzilla ID here too. Thanks.
Ok, done:
https://bugzilla.novell.com/show_bug.cgi?id=763150
Notice that the same update of mysql also broke amarok, several people have described the problem. I can not report it because I do not use it (it was already broken for me, unknown random motive, now using clementine instead).
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
I think I might have found the underlying cause of this. Went from 11.4 12.2 a couple of weeks ago and the flush-log option no longer worked affecting mysqldump among other things so I dug into it. I filed a bug report.
https://bugzilla.novell.com/show_bug.cgi?id=792332
-Curt
On 05/19/12 19:13, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-05-19 22:15, Lars Müller wrote:
Does anybody have an explanation why this was required after update?
And later report the bugzilla ID here too. Thanks.
Ok, done:
https://bugzilla.novell.com/show_bug.cgi?id=763150
Notice that the same update of mysql also broke amarok, several people have described the problem. I can not report it because I do not use it (it was already broken for me, unknown random motive, now using clementine instead).
Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+4NzUACgkQIvFNjefEBxqthwCfboJ8M33z2DYu3KinNKhLnGvB SGsAoNtbKzFb8G5pNnSxuxmhpEtfRmHe =MQxz -----END PGP SIGNATURE-----
Carlos E. R. wrote:
I get this in the log:
[snip]
So, what happens? This has started right after the last mysql upgrade. Another bug?
I have seen the same, but I just switch off the logrotate for mysqld.log - very little is ever written to it.
-
Carlos E. R. -
Carlos E. R. -
Curtis J Blank -
David C. Rankin -
Lars Müller -
Paolo Pantò -
Per Jessen