package mysql-server-5.1 5.1.41-3ubuntu12.3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

Bug #613683 reported by norbert schuehler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-dfsg-5.1 (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Lucid Lynx
upgrade failed
upgrade claims mysql server could not be stopped, but server isn't running

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: mysql-server-5.1 5.1.41-3ubuntu12.3
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
Uname: Linux 2.6.31-20-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Aug 4 20:35:34 2010
ErrorMessage: subprocess new pre-installation script returned error exit status 1
Logs.var.log.daemon.log:

Logs.var.log.kern.log:

MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['mysql_upgrade_info', 'debian-5.0.flag', 'ibdata1', 'ib_logfile1', '.bash_history', 'mysql', 'debian-5.1.flag', 'ib_logfile0']
SourcePackage: mysql-dfsg-5.1
Title: package mysql-server-5.1 5.1.41-3ubuntu12.3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

Revision history for this message
norbert schuehler (info-thrakkorzog) wrote :
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Norbert, thank you for reporting this issue and working with us to make Ubuntu better!

This bug in mysql-server-5.1.preinst, is mostly due to misleading error messages. The script assumes because the mysqld init script exists, that mysqld is in fact running, when it may very well not be.

The fix is to only try to stop mysqld if it is running, though its not entirely clear how to reliably determine that it is running (possibly with the pid file)

Marking Triaged and setting Importance to Low, as most users who have installed mysql-server will in fact have it running.

Changed in mysql-dfsg-5.1 (Ubuntu):
status: New → Triaged
importance: Undecided → Low
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.