Bug#326427:

[sdbteam]

We still get this email every day :

/etc/cron.daily/mysql-server:
ERROR 1381 (HY000) at line 1: You are not using binary logging

By the way 

echo 'SHOW MASTER LOGS;' | mysql -s --skip-column-names 21  /dev/null

actually outputs ERROR 1381 (HY000) at line 1: You are not using binary 
logging


ii  libmysqlclient144.1.14-4  mysql 
database client library
ii  libmysqlclient155.0.12beta-4  mysql 
database client library
ii  libmysqlclient15-dev5.0.12beta-4  mysql 
database development files
ii  mysql-client-5.05.0.12beta-4  mysql 
database client binaries
ii  mysql-common5.0.12beta-4  mysql 
database common files (e.g. /etc/mysql/my.cnf)
ii  mysql-server-5.05.0.12beta-4  mysql 
database server binaries




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#326427: patch for the cron.daily-script

[Christian Hammers]

tags 326427 + pending
thanks

Hello Martin

On 2005-09-05 Martin Krüger wrote:
 It appears that the SHOW MASTER LOGS; prints also the filesize of the
 binlogs into the tempfile. And since the whole line is used as the filename
 for the PURGE, the server discards the command as it can not find the file.
 Therefor we just use the first column as filename. (see the diff)

Indeed, the output looks different now. Thanks for pointing that out and
providing a fix!

bye,

-christian-

Bug#326427: patch for the cron.daily-script

[Martin Krüger]

It appears that the SHOW MASTER LOGS; prints also the filesize of the binlogs 
into the tempfile.
And since the whole line is used as the filename for the PURGE, the server 
discards the command as it can not find the file.
Therefor we just use the first column as filename.
(see the diff)


Thanks and have a nice day.
-- 

MK
49c49
   filename=`tail -n $KEEP_BINARY_LOGS $tmp | head -n 1`
---
   filename=`tail -n $KEEP_BINARY_LOGS $tmp | head -n 1 | cut -f1`

Bug#326427: mysql-server-5.0: cron script /etc/cron.daily/mysql-server fails

[Anders Ellenshøj Andersen]

Package: mysql-server-5.0
Version: 5.0.11beta-3
Severity: normal


The daily rotation of binary log files which this script handles always fails 
with this error, which I 
get in my mail daily:

/etc/cron.daily/mysql-server:
ERROR 1373 (HY000) at line 1: Target log not found in binlog index
run-parts: /etc/cron.daily/mysql-server exited with return code 1

The package seems to work fine beside of this.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12via-1
Locale: LANG=da_DK, LC_CTYPE=da_DK (charmap=ISO-8859-1)

Versions of packages mysql-server-5.0 depends on:
ii  adduser  3.67Add and remove users and groups
ii  debconf [debconf 1.4.58  Debian configuration management sy
ii  libc62.3.5-6 GNU C Library: Shared libraries an
ii  libdbi-perl  1.48-1  Perl5 database interface by Tim Bu
ii  libgcc1  1:4.0.1-6   GCC support library
ii  libmysqlclient15 5.0.11beta-3mysql database client library
ii  libncurses5  5.4-9   Shared libraries for terminal hand
ii  libreadline4 4.3-15  GNU readline and history libraries
ii  libstdc++6   4.0.1-6 The GNU Standard C++ Library v3
ii  libwrap0 7.6.dbs-8   Wietse Venema's TCP wrappers libra
ii  mailx1:8.1.2-0.20050715cvs-1 A simple mail user agent
ii  mysql-client-5.0 5.0.11beta-3mysql database client binaries
ii  mysql-common 5.0.11beta-3mysql database common files (e.g. 
ii  passwd   1:4.0.3-39  change and administer password and
ii  perl 5.8.7-4 Larry Wall's Practical Extraction 
ii  psmisc   21.6-1  Utilities that use the proc filesy
ii  zlib1g   1:1.2.3-4   compression library - runtime

mysql-server-5.0 recommends no packages.

-- debconf information:
  mysql-server-5.0/really_downgrade: false
  mysql-server-5.0/start_on_boot: true
  mysql-server-5.0/mysql_update_hints1:
  mysql-server-5.0/nis_warning:
  mysql-server-5.0/postrm_remove_databases: false
* mysql-server-5.0/mysql_install_db_notes:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]