mysql-server-5.1 5.1.30-2ubuntu3 fails to install/upgrade / doesn't start - skip-bdb option unsupported (amarok)

Have you done a fresh install of 9.04 or is it an uppgrade?

In my freshly installed 9.04-alfa2 there is no mention of skip-bdb in /etc/mysql/my.cnf

But yes, if I myself add the option skip-bdb to my /etc/mysql/my.cnf I do get the same error.

Well, the most recent upgrade of mysql-common did give me a /etc/mysql/my.cnf containing the skip-bdb option, breaking mysql-server startup.

It works here too:

Commenting out the skip-bdb line enabled me to finish amarok 2.0 installation on a recent jaunty installation.

The same worked for me when installing amarok 2.

I confirm I have the same bug with a fresh install of Ubuntu 9.04 Alpha-3 release desktop i386 edition.

The solution of commenting out the skip-bdb line worked and Mysql was able to finish the installation.

Interesting... this worked for me. But this is of course not an ideal solution as I'd rather not deal with the overhead.

Thanks for the workaround.

works here too. (jaunty upgrade from 8.10 clean install x86) thanks for the workaround.

Should fixed with the new version of mysql-dfsg-5.0 which doesn't have the skip-bdb option set in my.cnf.

This bug was fixed in the package mysql-dfsg-5.0 - 5.1.30really5.0.75-0ubuntu3

---------------
mysql-dfsg-5.0 (5.1.30really5.0.75-0ubuntu3) jaunty; urgency=low

  * debian/additions/my.cnf: remove skip-bdb option. This option is not
    available in 5.1 anymore. Moreover 5.0 isn't build with the BerkeleyDB
    engine. (LP: #316849)
  * debian/mysql-sever-core-5.0.files: move character sets files to -core as
    they're required for mysqld to properly support character sets.

 -- Mathias Gug <email address hidden> Wed, 21 Jan 2009 19:41:14 -0500

I can confirm this bug still exists in mysql-server-5.1 (5.1.30-2ubuntu3), from an upgrade of Intrepid to Jaunty, then installing 5.1.
This breaks the upgrade, however, commenting out skip-bdb fix works and apt continues the upgrade

On Thu, Jan 22, 2009 at 02:22:02AM -0000, Tom Worley wrote:
> I can confirm this bug still exists in mysql-server-5.1 (5.1.30-2ubuntu3), from an upgrade of Intrepid to Jaunty, then installing 5.1.
> This breaks the upgrade, however, commenting out skip-bdb fix works and apt continues the upgrade

Could you check if mysql-common has been upgraded? If so have you been
prompted for a configuration change? If so did you accept it?

mysql-common is part of mysql-dfsg-5.0 and not mysql-dsfg-5.1. The fix
for this bug is in mysql-dfsg-5.0 - mysql-dfsg-5.1 hasn't been changed.

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

Sorry, I cannot check this anymore, my installation was completely messed up.
I removed it.

Tim Kuip
===============================
On Thursday 22 January 2009 16:45:45 Mathias Gug wrote:
> On Thu, Jan 22, 2009 at 02:22:02AM -0000, Tom Worley wrote:
> > I can confirm this bug still exists in mysql-server-5.1
> > (5.1.30-2ubuntu3), from an upgrade of Intrepid to Jaunty, then installing
> > 5.1. This breaks the upgrade, however, commenting out skip-bdb fix works
> > and apt continues the upgrade
>
> Could you check if mysql-common has been upgraded? If so have you been
> prompted for a configuration change? If so did you accept it?
>
>
> mysql-common is part of mysql-dfsg-5.0 and not mysql-dsfg-5.1. The fix
> for this bug is in mysql-dfsg-5.0 - mysql-dfsg-5.1 hasn't been changed.
>
> --
> Mathias Gug
> Ubuntu Developer http://www.ubuntu.com

It's happening again during the upgrade to 5.1.30-2ubuntu4 . Furthermore /etc/mysql/my.cnf does not contain the skip-bdb option to comment out.

Hm... perhaps that's why it was kept back.

Same happened here:
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]:
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]: FATAL ERROR: Could not find /fill_help_tables.sql
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]:
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]: If you compiled from source, you need to run 'make install' to
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]: copy the software into the correct location ready for operation.
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]:
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]: If you are using a binary release, you must either be at the top
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]: level of the extracted archive, or pass the --basedir option
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]: pointing to that location.
Jan 26 20:24:05 simon-desktop mysqld_safe[8415]:
Jan 26 20:24:05 simon-desktop mysqld_safe[8442]: 090126 20:24:05 [ERROR] Can't find messagefile '/usr/share/mysql/english/errmsg.sys'
Jan 26 20:24:05 simon-desktop mysqld_safe[8442]: 090126 20:24:05 InnoDB: Started; log sequence number 0 46409
Jan 26 20:24:05 simon-desktop mysqld_safe[8442]: 090126 20:24:05 [ERROR] Aborting
Jan 26 20:24:05 simon-desktop mysqld_safe[8442]:
Jan 26 20:24:05 simon-desktop mysqld_safe[8442]: 090126 20:24:05 InnoDB: Starting shutdown...
Jan 26 20:24:06 simon-desktop mysqld_safe[8442]: 090126 20:24:06 InnoDB: Shutdown completed; log sequence number 0 46409
Jan 26 20:24:06 simon-desktop mysqld_safe[8442]: 090126 20:24:06 [Note]
Jan 26 20:24:06 simon-desktop mysqld_safe[8458]: 090126 20:24:06 [ERROR] Can't find messagefile '/usr/share/mysql/english/errmsg.sys'
Jan 26 20:24:06 simon-desktop mysqld_safe[8458]: 090126 20:24:06 InnoDB: Started; log sequence number 0 46409
Jan 26 20:24:06 simon-desktop mysqld_safe[8458]: 090126 20:24:06 [ERROR] Aborting
Jan 26 20:24:06 simon-desktop mysqld_safe[8458]:
Jan 26 20:24:06 simon-desktop mysqld_safe[8458]: 090126 20:24:06 InnoDB: Starting shutdown...
Jan 26 20:24:08 simon-desktop mysqld_safe[8458]: 090126 20:24:08 InnoDB: Shutdown completed; log sequence number 0 46409
Jan 26 20:24:08 simon-desktop mysqld_safe[8458]: 090126 20:24:08 [Note]
Jan 26 20:24:08 simon-desktop mysqld_safe[8471]: 090126 20:24:08 [ERROR] Can't find messagefile '/usr/share/mysql/english/errmsg.sys'
Jan 26 20:24:08 simon-desktop mysqld_safe[8471]: 090126 20:24:08 InnoDB: Started; log sequence number 0 46409
Jan 26 20:24:08 simon-desktop mysqld_safe[8471]: 090126 20:24:08 [ERROR] Aborting

simon@simon-desktop:~$ sudo ln -s /usr/share/mysql-5.1/mysql /usr/share/mysql - fixed the problem

>sudo ln -s /usr/share/mysql-5.1/mysql /usr/share/mysql

Thanks, that fixed it for me too.

Indeed! The workaround does the trick.

Confirming this bug still present upgrading Jaunty => Karmic a couple days ago.
The presence of skip-bdb in my.cnf (and keeping existing config) prevented mysql-server restart after upgrade, and made package upgrade fail.