Won't start if old_passwords=1 is in my.cnf

Bug #23664 reported by Debian Bug Importer
6
Affects Status Importance Assigned to Milestone
mysql-dfsg-4.1 (Debian)
Fix Released
Unknown
mysql-dfsg-4.1 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Automatically imported from Debian bug report #333132 http://bugs.debian.org/333132

Revision history for this message
In , Christian Hammers (ch) wrote : Re: Bug#333132: Won't start if old_passwords=1 is in my.cnf

Hello Martin

On 2005-10-10 Martin Sarsale wrote:
> I upgraded some days ago and, after rebooting, I found that my mysql was
> not running. This was printed on the daemon log

Please upgrade to mysql-server-4.1. The problem should vanish in a few
days when the next version enters "testing".

bye,

-christian-

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #333132 http://bugs.debian.org/333132

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Mon, 10 Oct 2005 13:08:22 -0300
From: Martin Sarsale <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: Won't start if old_passwords=1 is in my.cnf

Package: mysql-server
Version: 4.0.24-10
Severity: serious

I upgraded some days ago and, after rebooting, I found that my mysql was
not running.
This was printed on the daemon log

Oct 10 13:04:11 runa mysqld[8490]: 051010 13:04:11 /usr/sbin/mysqld:
unknown variable 'old_passwords=1'

I removed that line from my.cnf and it started ok.

I've no idea what package added that line to my.cnf but Im (almost) sure
that I didn't

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12ck
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mysql-server depends on:
ii adduser 3.67 Add and remove users and groups
ii debconf 1.4.58 Debian configuration management sy
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
ii libdbi-perl 1.48-2 Perl5 database interface by Tim Bu
ii libgcc1 1:4.0.1-2 GCC support library
ii libmysqlclient12 4.0.24-10 mysql database client library
ii libstdc++5 1:3.3.6-7 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra
ii mailx 1:8.1.2-0.20050715cvs-1 A simple mail user agent
ii mysql-client 4.0.24-10 mysql database client binaries
ii mysql-common 5.0.12beta-2 mysql database common files (e.g.
ii passwd 1:4.0.3-35 change and administer password and
ii perl 5.8.7-3 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 recommends no packages.

-- debconf information:
  mysql-server/skip_networking: false
  mysql-server/really_downgrade_from_41: false
  mysql-server/want_chroot: false
* mysql-server/start_on_boot: true
  mysql-server/postrm_remove_databases: false
* mysql-server/mysql_install_db_notes:
  mysql-server/nis_warning:
  mysql-server/mysql_update_hints1:
* mysql-server/postrm_remove_database: false
  mysql-server/fix_privileges_warning:

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 10 Oct 2005 18:05:42 +0200
From: Christian Hammers <email address hidden>
To: Martin Sarsale <email address hidden>, <email address hidden>
Subject: Re: Bug#333132: Won't start if old_passwords=1 is in my.cnf

Hello Martin

On 2005-10-10 Martin Sarsale wrote:
> I upgraded some days ago and, after rebooting, I found that my mysql was
> not running. This was printed on the daemon log

Please upgrade to mysql-server-4.1. The problem should vanish in a few
days when the next version enters "testing".

bye,

-christian-

Revision history for this message
Carthik Sharma (carthik) wrote :

Bug has been fixed in latest version of package in Dapper. Closing.

Changed in mysql-dfsg-4.1:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.