mysql-server preinst script stops running mysql

Bug #107224 reported by Razvan Gavril
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mysql-dfsg-5.0 (Debian)
Fix Released
Unknown
mysql-dfsg-5.0 (Ubuntu)
Fix Released
Low
Unassigned
Declined for Feisty by Mathias Gug
Declined for Hardy by Mathias Gug

Bug Description

Package: mysql-server
Release: feisty
Version: 5.0.38-0ubuntu1

Description:
Preinstall script for this meta packages stops the mysql server without ever starting it again.

Steps to Reproduce:
install mysql-server-5.0 on feisty
start mysql server
install the mysql-server meta package

Mathias Gug (mathiaz)
Changed in mysql-dfsg-5.0:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Soren Hansen (soren) wrote : Re: [Bug 107224] Re: mysql-server preinst script stops running mysql

The mysql-server package is meant to depend on the current "best" mysql
server as determined by the Debian maintainers. In my opinion the
maintainer scripts of e.g. mysql-server-5.0 should handle the upgrades
properly, so the mysql-server (the not-quite-meta-package) should really
just be a proper meta-package. I'll discuss it with the Debian people
later today. They must have had some sort of reason for creating the
package like that in the first place.

--
Soren Hansen
Ubuntu Server Team
http://www.ubuntu.com/

Mathias Gug (mathiaz)
Changed in mysql-dfsg-5.0:
importance: Medium → Low
Changed in mysql-dfsg-5.0:
status: Unknown → Confirmed
Revision history for this message
Mark Goldfinch (mark-goldfinch) wrote :

Is there some recent progress on this bug to report?

The release of 5.0.51a-3ubuntu5.5 for Hardy today caused a number of machines I help maintain to kill their running MySQL servers.

unattented-upgrades (for some reason still unknown to me) had the believe that mysql-common had a conffile prompt so wouldn't install mysql-server-5.0, however mysql-server did install and promptly shutdown the running MySQL instance.

--
Thanks,
Mark.

Revision history for this message
Hark (ubuntu-komkommerkom) wrote :

IMHO opinion this is a very important bug. Like Mark Goldfinch also reported unattended-upgraded caused a mysql shutdown on serveral of our servers. On several other servers where the meta package mysql-server was not installed this didn't happen.

2010-02-11 06:31:30,282 WARNING pkg 'mysql-common' has conffile prompt and needs to be upgraded manually
2010-02-11 06:31:31,735 INFO package 'mysql-common' not upgraded
2010-02-11 06:31:32,093 INFO package 'libmysqlclient15off' not upgraded
2010-02-11 06:31:32,598 INFO package 'mysql-server-5.0' not upgraded
2010-02-11 06:31:32,905 INFO Packages that are upgraded: mysql-server mysql-client

Result: mysql shutdown, without being started again. That certainly deserves more than a low bug priority!

Also see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415124

Revision history for this message
Lonnie Olson (fungussn) wrote :

Gah! This is the second time this package has killed my MySQL Server without restarting it.

You *must* change the importance from Low to High.

Revision history for this message
Hark (ubuntu-komkommerkom) wrote :

@Lonnie Olson: a workaround is to remove the meta-package mysql-server.

Revision history for this message
Mark Goldfinch (mark-goldfinch) wrote :

Removing mysql-server does solve this problem, however it can create the following undesirable output when using apt-get:

The following packages were automatically installed and are no longer required:
  libdbi-perl libdbd-mysql-perl mysql-server-5.0 mysql-client-5.0
Use 'apt-get autoremove' to remove them.

Obviously to the uninformed running an apt-get autoremove at this stage would be very unhelpful.

I can understand why this step would be required when migrating from a truely ancient distribution such as sarge where mysql-server is a real binary package supporting MySQL 4. Perhaps the patch for the preinst script should test which version of mysql-server we're coming from and if it is less than 5 then run /etc/init.d/mysql stop, otherwise it should be a no-op?

Revision history for this message
LoboOscuro (lobooscuro1) wrote :

no se ingles, habia publicado creo un bug parecido pero lo perdi.
Habia recibido un par de correos que creo yo, son soluciones, ya los mire, ya tenia todas las librerias instaladas:

libgcc1 debconf lsb-base libplrpc-perl readline-common libtext-wrapi18n-perl libwrap0 libreadline5 libdbi-perl sed mysql-common findutils libmysqlclient15off perl-modules debconf-i18n libnet-daemon-perl adduser perl ncurses-bin libgdbm3 libstdc++6 libpam-runtime libpam-modules passwd libselinux1 mysql-client-5.0 liblocale-gettext-perl zlib1g libncurses5 libc6 libpam0g libdbd-mysql-perl libtext-iconv-perl psmisc perl-base libdb4.7 libdb4.6 libtext-charwidth-perl gcc-4.3-base debianutils

  El segundo correo es solo una imagen de todo el suceso de apt-get.

  sigo con el mismo problema:

Procesando activadores para man-db ...
Configurando mysql-client-5.0 (5.0.67-0ubuntu6.1) ...
Configurando mysql-server-5.0 (5.0.67-0ubuntu6.1) ...
 * Stopping MySQL database server mysqld [ OK ]
/var/lib/dpkg/info/mysql-server-5.0.postinst: line 143: /etc/mysql/conf.d/old_passwords.cnf: No existe el fichero ó directorio
dpkg: error al procesar mysql-server-5.0 (--configure):
 el subproceso post-installation script devolvió el código de salida de error 1
dpkg: problemas de dependencias impiden la configuración de mysql-server:
 mysql-server depende de mysql-server-5.0; sin embargo:
 El paquete `mysql-server-5.0' no está configurado todavía.
dpkg: error al procesar mysql-server (--configure):
 problemas de dependencias - se deja sin configurar
No se ha escrito ningún informe de Apport porque el mensaje de error indica que es un error proveniente de un fallo anterior.
                                             Se encontraron errores al procesar:
 mysql-server-5.0
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

Se me hace que el problema es mas bien simple y es que hay que configurar los archivos de configuracion o de password, pero me extraña, si no se instala por defecto y si por casualidad lo llego a arreglar a mano, que sucede con este proceso de instalacion?

Revision history for this message
Chuck Short (zulcss) wrote :

This should be fixed in lucid and above.

Changed in mysql-dfsg-5.0 (Ubuntu):
status: Triaged → Fix Released
Changed in mysql-dfsg-5.0 (Debian):
status: Confirmed → 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.