hi thomas, On Sun, Oct 23, 2005 at 08:20:06PM +0200, Thomas Renard wrote: > Hm, wrong mysql-common?
no, that's intentional. i believe now we have one mysql-common package
across all versions of mysql in unstable.
> + echo 'PURGE MASTER LOGS TO '\''mysql-bin.000007 3377'\'';'
> ERROR at line 1: Target log not found in binlog index
hmm... that looks kind of strange... i believe it "should" be
'PURGE MASTER LOGS TO '\''mysql-bin.000007'\'';'
and somehow that extra field snuck into the variable. istr seeing
this same problem a months or two back and thought it was already
fixed... in 4.1.14-1 to be exact:
mysql-dfsg-4.1 (4.1.14-1) unstable; urgency=high
<snip>
- Applied fix for changed output format of SHOW MASTER LOGS for
binary log rotation (thanks to Martin Krueger). Closes: #326427, #326427
<snip>
perhaps you still have the old version of the cron script?
unfortunately i don't have access to the svn repository right now,
but i'll send you a copy of the the "default" version to see
if there are any differences as soon as i do, probably this
evening. in the meantime, there has just been another update
to mysql-dfsg-4.1 that includes another binary log-related problem.
while i don't think it's the same issue, maybe upgrading will let you
know if the file has changed (giving you the standard "this file has
changed" warning), or maybe the problem will otherwise go away :)
sean
--
signature.asc
Description: Digital signature
