Re: lsof +L1 - mysql.err.1 unlinked ...
Hello On Tue, Jan 07, 2003 at 11:25:18PM +0100, Christian Jaeger wrote: I have always these mysql.err.1 files not unlinked in all my mysqlservers, and only a mysqld restart resolve these (nor reload neither mysqladmin refresh doesn't unlink them). The err file is created by safe_mysqld to catch the output mysqld produces when it cannot start. As mysqld outputs to stderr on errors, too, everything is appended to that file in the nohup line, too. So there's currently the problem whether never to rotate it or to loose the errors messages. I change the behaviour of the Debian package to not rotating now. A better fix is coming hopefully, I already proposed some possible solutions to the [EMAIL PROTECTED] list (reopening the file in flush-logs or using syslog). bye, -christian- (maintainer of Debian mysql package) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
lsof +L1 - mysql.err.1 unlinked ...
Hi everybody, I have always these mysql.err.1 files not unlinked in all my mysqlservers, and only a mysqld restart resolve these (nor reload neither mysqladmin refresh doesn't unlink them). Does anybody in the list encounter this problem ? Am I obliged to add a mysql restart in my logrotate config (the debian default contain only flush-logs which doesn't unlink the mysql.err.1 log) ? or is there another way to avoid this ? Of course, it's not critical, but it bothers. Thanks in advance, ntpaymaster:~# lsof +L1 | grep mysql mysqld 13026 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 13026 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 17811 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 17811 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 17894 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 17894 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 17948 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 17948 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 17982 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 17982 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 18035 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 18035 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 18161 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 18161 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 20025 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 20025 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 20175 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 20175 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 22853 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 22853 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 22855 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 22855 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 22856 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 22856 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 22857 root1w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) mysqld 22857 root2w REG8,6548 0 245 /var/log/mysql.err.1 (deleted) ntpaymaster:~# -- Do-Risika RAFIEFERANTSIARONJY, SysAdmin mailto:[EMAIL PROTECTED] Simicro Internet, mailto:[EMAIL PROTECTED], http://internet.simicro.mg Tel : (+261) 20 22 648 83 (GMT +3), Fax : (+261) 20 22 661 83 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lsof +L1 - mysql.err.1 unlinked ...
At 15:11 Uhr +0300 07.01.2003, Do-Risika RAFIEFERANTSIARONJY wrote: Hi everybody, I have always these mysql.err.1 files not unlinked in all my mysqlservers, and only a mysqld restart resolve these (nor reload neither mysqladmin refresh doesn't unlink them). Does anybody in the list encounter this problem ? I'm seeing the same with lsof (I'm on Debian, too). But when I stop mysql, it writes the mysqld ended message to mysql.err, not mysql.err.1. If I'm correctly assuming that this message is written by the mysqld process, then it looks like it does reopen the file as soon as it has something to write to it (instead of immediately after getting the flush-logs command). Am I obliged to add a mysql restart in my logrotate config (the debian default contain only flush-logs which doesn't unlink the mysql.err.1 log) ? or is there another wa Looks like it's no problem at all. Christian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lsof +L1 - mysql.err.1 unlinked ...
Sorry, I've restarted mysql again and am seeing that it normally does not only write mysql ended but a whole bunch of other lines to the logs. So yes it is a problem. Christian. At 15:11 Uhr +0300 07.01.2003, Do-Risika RAFIEFERANTSIARONJY wrote: Hi everybody, I have always these mysql.err.1 files not unlinked in all my mysqlservers, and only a mysqld restart resolve these (nor reload neither mysqladmin refresh doesn't unlink them). Does anybody in the list encounter this problem ? I'm seeing the same with lsof (I'm on Debian, too). But when I stop mysql, it writes the mysqld ended message to mysql.err, not mysql.err.1. If I'm correctly assuming that this message is written by the mysqld process, then it looks like it does reopen the file as soon as it has something to write to it (instead of immediately after getting the flush-logs command). Am I obliged to add a mysql restart in my logrotate config (the debian default contain only flush-logs which doesn't unlink the mysql.err.1 log) ? or is there another wa Looks like it's no problem at all. Christian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
