Debian Bug report logs - #415124
transitional package mysql-server stops server in preinst

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Jean-David Maillefer <jean-david@kesako.ch>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: mysql-server: No start after install

Date: Fri, 16 Mar 2007 11:38:53 +0100

Package: mysql-server
Version: 5.0.32-7
Severity: normal



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

Versions of packages mysql-server depends on:
ii  mysql-server-5.0              5.0.32-7   mysql database server binaries

mysql-server recommends no packages.

-- no debconf information


-- comment
The installation stops the mysql server if running, but does not restart
it after installation.

Message #10 received at 415124@bugs.debian.org (full text, mbox, reply):

From: Christian Hammers <ch@debian.org>

To: Jean-David Maillefer <jean-david@kesako.ch>, 415124@bugs.debian.org

Subject: Re: Bug#415124: mysql-server: No start after install

Date: Fri, 16 Mar 2007 14:35:08 +0100

On 2007-03-16 Jean-David Maillefer wrote:
> The installation stops the mysql server if running, but does not restart
> it after installation.

Please send me "grep mysql /etc/runlevel.conf" or "find /etc/rc* |grep mysql" depending
on which initsystem you use.

If the init system has been modified by the admin not to start mysql at boot then it's
a general dpkg behaviour not to start the daemon after upgrades.

If it looks like an error send me "grep -i mysql /var/log/syslog /var/log/messages"

bye,

-christian-

Message #15 received at 415124@bugs.debian.org (full text, mbox, reply):

From: Christian Hammers <ch@debian.org>

To: Maillefer Jean-David <jean-david@kesako.ch>, 415124@bugs.debian.org, dc <control@bugs.debian.org>

Subject: Re: Bug#415124: mysql-server: No start after install

Date: Sat, 17 Mar 2007 10:34:11 +0100

retitle 415124 transitional package mysql-server stops server in preinst
tags 415124 + confirmed
stop

Hello

On 2007-03-16 Maillefer Jean-David wrote:
> One little precision: the problem doesn't occur if installing at the
> same time other mysql-* packages, since they restart the server
> correctly.
 
The mysql server is included in the mysql-server-5.0 packages since version
5.0. In older Debian releases with mysql 3.23 and 4.0 the package was called
just mysql-server. So we needed the "empty" mysql-server package for smooth
upgrades. In a normal testing/unstable environment there is of course no need
for it to stop the server as this is done by mysql-server-5.0.preinst but
I have to think about whether this might have been necessary for certain
upgrade paths...
At least I guess that it's not a grave issue as it's unlikely that
mysql-server gets upgraded at a different time than mysql-server-5.0.

bye,

-christian-

Message #24 received at 415124@bugs.debian.org (full text, mbox, reply):

From: Roland Karch <Roland.Karch@rrze.uni-erlangen.de>

To: 415124@bugs.debian.org

Subject: Re: Bug#415124: mysql-server: No start after install

Date: Thu, 06 Nov 2008 08:38:52 +0100

This bug actually terminated by mysql server this morning. I do run
unattended-upgrades daily by cron. This upgraded all mysql packages
apart from the mysql-server-5.0 package to version 5.0.32-7etch8. I'd
assume the real server package is tagged interactive or something so
that it doesn't get touched by unattended-upgrades. Anyways, just wanted
to mention that it's not quite as unlikely that mysql-server gets
upgraded independently from mysql-server-5.0 as you assumed.

Here's the apt log of the automatic update:
(Reading database ... 131272 files and directories currently installed.)
Preparing to replace mysql-common 5.0.32-7etch6
(using .../mysql-common_5.0.32-7etch8_all.deb) ...
Unpacking replacement mysql-common ...
Preparing to replace libmysqlclient15off 5.0.32-7etch6
(using .../libmysqlclient15off_5.0.32-7etch8_i386.deb) ...
Unpacking replacement libmysqlclient15off ...
Preparing to replace mysql-client 5.0.32-7etch6
(using .../mysql-client_5.0.32-7etch8_all.deb) ...
Unpacking replacement mysql-client ...
Preparing to replace mysql-client-5.0 5.0.32-7etch6
(using .../mysql-client-5.0_5.0.32-7etch8_i386.deb) ...
Unpacking replacement mysql-client-5.0 ...
Preparing to replace mysql-server 5.0.32-7etch6
(using .../mysql-server_5.0.32-7etch8_all.deb) ...
Stopping MySQL database server: mysqld.
Unpacking replacement mysql-server ...
Setting up mysql-common (5.0.32-7etch8) ...
Setting up libmysqlclient15off (5.0.32-7etch8) ...

Setting up mysql-client-5.0 (5.0.32-7etch8) ...
Setting up mysql-client (5.0.32-7etch8) ...
Setting up mysql-server (5.0.32-7etch8) ...

Message #29 received at 415124@bugs.debian.org (full text, mbox, reply):

From: Lonnie Olson <olsonl@sosstaffing.com>

To: 415124@bugs.debian.org

Subject: unattended-upgrade causes MySQL to stop

Date: Mon, 24 Nov 2008 15:29:48 -0700

I can confirm that this bug *is* a grave issue.  I had 3 servers stop
MySQL services during an unattended upgrade.

2008-11-22 06:46:03,870 INFO Initial blacklisted packages: 
2008-11-22 06:46:03,870 INFO Starting unattended upgrades script
2008-11-22 06:46:03,870 INFO Allowed origins are: ["['Ubuntu',
'hardy-security']"]
2008-11-22 06:46:14,226 WARNING pkg 'mysql-common' has conffile prompt
and needs to be upgraded manually
2008-11-22 06:46:15,321 INFO package 'mysql-common' not upgraded
2008-11-22 06:46:16,038 INFO package 'mysql-client-5.0' not upgraded
2008-11-22 06:46:16,752 INFO package 'libmysqlclient15off' not upgraded
2008-11-22 06:46:17,470 INFO package 'mysql-server-5.0' not upgraded
2008-11-22 06:46:18,182 INFO Packages that are upgraded: mysql-server
2008-11-22 06:46:18,182 INFO Writing dpkg log to
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2008-11-22_06:46:18.182579.log'
2008-11-22 06:46:22,840 INFO All upgrades installed

and the actual dpkg log

(Reading database ... 53756 files and directories currently installed.)
Preparing to replace mysql-server 5.0.51a-3ubuntu5.1 (using
.../mysql-server_5.0.51a-3ubuntu5.4_all.deb) ...
 * Stopping MySQL database server mysqld
   ...done.
Unpacking replacement mysql-server ...
Setting up mysql-server (5.0.51a-3ubuntu5.4) ...


Hence, since mysql-server-5.0 is held back due to conffile prompt, it
causes MySQL to stop.  Very grave indeed.

Solutions may include:
* Remove the preinst script from "mysql-server"
or 
* Add a postinst script to start mysql in "mysql-server"

--lonnie

Message #34 received at 415124@bugs.debian.org (full text, mbox, reply):

From: Jochen Pawletta <jochen@hin.de>

To: 415124@bugs.debian.org

Subject: Possible solution

Date: Sun, 31 Jan 2010 11:18:07 +0100

Hi

> Solutions may include:
> * Remove the preinst script from "mysql-server"
> or 
> * Add a postinst script to start mysql in "mysql-server"

What about only stopping the server if mysql-server-5.0 is not
installed?


Jochen

-- 
ZX81 - C64 - Amiga - x86-Linux - iMac (OS X)

Message #39 received at 415124@bugs.debian.org (full text, mbox, reply):

From: Lonnie Olson <olsonl@sosstaffing.com>

To: 415124@bugs.debian.org

Subject: unattended-upgrade causes MySQL to stop *AGAIN?*

Date: Thu, 11 Feb 2010 10:22:51 -0700

Hello?!  Is this thing on?

My unattended upgrade killed the server yet again!  Please fix this bug.

It can't be that hard to simply remove the stopping of mysql in this
package.  The real package, mysql-server-5.0 already handles the
stopping itself.

--lonnie

Message #44 received at 415124-done@bugs.debian.org (full text, mbox, reply):

From: Norbert Tretkowski <norbert@tretkowski.de>

To: Lonnie Olson <olsonl@sosstaffing.com>, 415124-done@bugs.debian.org

Subject: Re: [debian-mysql] Bug#415124: unattended-upgrade causes MySQL to stop *AGAIN?*

Date: Fri, 12 Feb 2010 15:38:01 +0100

Version: 5.1.11beta-1

Am Donnerstag, den 11.02.2010, 10:22 -0700 schrieb Lonnie Olson:
> Hello?!  Is this thing on?
> 
> My unattended upgrade killed the server yet again!  Please fix this bug.

It's fixed already in testing.

	Norbert

Send a report that this bug log contains spam.