Ubuntu Precise breaks install and upgrade by trashing MariaDB [#1897018]

Until a few days ago, on a brand-new Ubuntu 12.04 server, I was able to install boa/barracuda/octopus/aegir without any problems at all.

Now, though, the same installation attempts fail (also on a brand new installation of the OS). During the attempt to install mariadb, there are now messages about unmet dependencies, and eventually the installation fails and mariadb has not been installed. This is literally being installed on a VirtualBox-hosted server instance which has had *no* updates applied to it or packages installed other than ddclient.

The following items reference the same sorts of messages about unmet dependencies for libmariadbclient18 I'm seeing.

Will post my logfile when I have one, but here's an example with similar messages:

Need to get 31.6 MB of archives. After unpacking 110 MB will be used.
The following packages have unmet dependencies:
 mariadb-server-core-5.5 : Conflicts: mysql-server-core-5.5 but 5.5.24-0ubuntu0.12.04.1 is installed and it is kept back.
 mysql-server-core-5.5 : Breaks: mysql-server-core-5.1 which is a virtual package.
 mariadb-client-core-5.5 : Conflicts: mysql-client-core-5.5 but 5.5.24-0ubuntu0.12.04.1 is installed and it is kept back.
 mysql-client-core-5.5 : Breaks: mysql-client-core-5.1 which is a virtual package.
The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1)     mariadb-client-5.5 [Not Installed]                 
2)     mariadb-client-core-5.5 [Not Installed]            
3)     mariadb-server-5.5 [Not Installed]                 
4)     mariadb-server-core-5.5 [Not Installed]

Comment	File	Size	Author
#5	barracuda-conf.txt	1.44 KB	lynnewu
#2	boa-console.txt	7.76 KB	lynnewu
#2	boa-install-log.txt	252.8 KB	lynnewu

Comments

Comment #1

omega8cc commented 23 January 2013 at 22:45

Status:

Active

» Postponed (maintainer needs more info)

Please follow bug submission guidelines.

Comment #2

lynnewu commented 23 January 2013 at 22:47

Status:

Postponed (maintainer needs more info)

» Active

Status	File	Size
new	boa-install-log.txt	252.8 KB
new	boa-console.txt	7.76 KB

Comment #3

lynnewu commented 23 January 2013 at 22:49

Ok. Which bug submission guidelines? I see that you're missing information, but am not sure what more I can provide. The console log and logfiles are the only information I have right now. If there's something else, I'd be happy to provide it. Thanks very much.

Comment #4

omega8cc commented 23 January 2013 at 22:54

Status:

Active

» Postponed (maintainer needs more info)

The guidelines and required files are explained/listed on the Create Issue form: http://drupal.org/node/add/project-issue/barracuda

It is to save some time, so we don't need to ask you for some specific details we need to know anyway.

Comment #5

lynnewu commented 23 January 2013 at 23:02

Status	File	Size
new	barracuda-conf.txt	1.44 KB

Neither of these files exist:

/var/aegir/config/includes/barracuda_log.txt
/var/aegir/install.log

root@xanthotis:/var/aegir# ls -alF
total 8
drwxr-xr-x  2 root root 4096 Jan 23 16:40 ./
drwxr-xr-x 15 root root 4096 Jan 23 16:40 ../

Comment #6

omega8cc commented 23 January 2013 at 23:15

Title:	boa installation doesn't install mariadb - messages mention unmet dependencies	» Ubuntu Precise breaks install and upgrade by trashing MariaDB
Status:	Postponed (maintainer needs more info)	» Active

Thanks, this helps. It looks like we need to better protect BOA from Ubuntu crazy folks who are not afraid to break *LTS* distro.

Comment #7

omega8cc commented 23 January 2013 at 23:19

Oh, I just realized that Peter W Bowey reported this earlier today via e-mail I will repost below:

Hi Grace,
 
I am 'frothing at the mouth' over Ubuntu's strange update policy!
 
As usual, we Australian's are the first to get hit by the OS update saga's.
 
Ubuntu released a update 23 hours ago that 'smashed out' omega8.cc's careful work to support
MariaDB 5.5.28-mariadb-a1~precise. Ubuntu poked out a updated 'libmysqlclient18' release
that smashed the BOA & MariaDB out of the picture. Ubuntu's new version is '5.5.29-0ubuntu0.12.10.1'
dated - 2013-01-22 15:07:08 UTC. This does not work yet with BOA
 
See Link here: https://launchpad.net/ubuntu/quantal/+source/mysql-5.5/5.5..29-0ubuntu0.12.10.1
 
Now, I have been 'battling for hours' to work around this Ubuntu pain, while we wait
on the MariaDB team to re-syncs it's own updates with the Ubuntu 12.04 updates.
 
Here is the 'crude *forced* style' I worked with to get BOA and MariaDB back to life - after the Ubuntu *forced*
update and dependency killed BOA and the database [MariaDB]:
 
 
 
server:~/aegir-boa-installer# aptitude install mariadb-server-5.5 mariadb-common
The following NEW packages will be installed:
  libdbd-mysql-perl{a} libmariadbclient18{ab} libmysqlclient18{a} mariadb-client-5.5{a} mariadb-client-core-5.5{a} mariadb-server-5.5 mariadb-server-core-5.5{a}
0 packages upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 31.8 MB of archives. After unpacking 107 MB will be used.
The following packages have unmet dependencies:
 mysql-common : Breaks: mysql-client-5.1 which is a virtual package.
                Breaks: mysql-client-core-5.1 which is a virtual package.
                Breaks: mysql-server-core-5.1 which is a virtual package.
 libmariadbclient18 : Depends: libmysqlclient18 (= 5.5.28-mariadb-a1~precise) but 5.5.29-0ubuntu0.12.04.1 is to be installed.
The following actions will resolve these dependencies:
 
     Keep the following packages at their current version:
1)     libmariadbclient18 [Not Installed]
2)     mariadb-client-5.5 [Not Installed]
3)     mariadb-client-core-5.5 [Not Installed]
4)     mariadb-server-5.5 [Not Installed]
5)     mariadb-server-core-5.5 [Not Installed]
 
 
 
Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:
 
     Install the following packages:
1)     libmysqlclient18 [5.5.28-mariadb-a1~precise (<NULL>)]
 
     Downgrade the following packages:
2)     mysql-common [5.5.29-0ubuntu0.12.04.1 (now, precise-security, precise-updates) -> 5.5.28-mariadb-a1~precise (<NULL>)]
 
 
 
Accept this solution? [Y/n/q/?]
 
The following packages will be DOWNGRADED:
  mysql-common
The following NEW packages will be installed:
  libdbd-mysql-perl{a} libmariadbclient18{a} libmysqlclient18{a} mariadb-client-5.5{a} mariadb-client-core-5.5{a} mariadb-server-5.5 mariadb-server-core-5.5{a}
0 packages upgraded, 7 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
Need to get 30.9 MB of archives. After unpacking 104 MB will be used.
Do you want to continue? [Y/n/?] y
Get: 1 http://archive.ubuntu.com/ubuntu/ precise/main libdbd-mysql-perl i386 4.020-1build2 [104 kB]
Get: 2 http://ftp.osuosl.org/pub/mariadb/repo/5.5/ubuntu/ precise/main mysql-common all 5.5.28-mariadb-a1~precise [8,780 B]
Get: 3 http://ftp.osuosl.org/pub/mariadb/repo/5.5/ubuntu/ precise/main libmariadbclient18 i386 5.5.28-mariadb-a1~precise [817 kB]
Get: 4 http://ftp.osuosl.org/pub/mariadb/repo/5.5/ubuntu/ precise/main libmysqlclient18 i386 5.5.28-mariadb-a1~precise [2,920 B]
Get: 5 http://ftp.osuosl.org/pub/mariadb/repo/5.5/ubuntu/ precise/main mariadb-client-core-5.5 i386 5.5.28-mariadb-a1~precise [1,797 kB]
Get: 6 http://ftp.osuosl.org/pub/mariadb/repo/5.5/ubuntu/ precise/main mariadb-client-5.5 i386 5.5.28-mariadb-a1~precise [5,097 kB]
Get: 7 http://ftp.osuosl.org/pub/mariadb/repo/5.5/ubuntu/ precise/main mariadb-server-core-5.5 i386 5.5.28-mariadb-a1~precise [5,113 kB]
Get: 8 http://ftp.osuosl.org/pub/mariadb/repo/5.5/ubuntu/ precise/main mariadb-server-5.5 i386 5.5.28-mariadb-a1~precise [18.0 MB]
Fetched 30.9 MB in 30s (1,020 kB/s)
Preconfiguring packages ...
dpkg: warning: downgrading mysql-common from 5.5.29-0ubuntu0.12.04.1 to 5.5.28-mariadb-a1~precise.
(Reading database ... 61332 files and directories currently installed.)
Preparing to replace mysql-common 5.5.29-0ubuntu0.12.04.1 (using .../mysql-common_5.5.28-mariadb-a1~precise_all.deb) ...
Unpacking replacement mysql-common ...
Selecting previously unselected package libmariadbclient18.
Unpacking libmariadbclient18 (from .../libmariadbclient18_5.5.28-mariadb-a1~precise_i386.deb) ....
Selecting previously unselected package libmysqlclient18.
Unpacking libmysqlclient18 (from .../libmysqlclient18_5.5.28-mariadb-a1~precise_i386.deb) ....
Selecting previously unselected package libdbd-mysql-perl.
Unpacking libdbd-mysql-perl (from .../libdbd-mysql-perl_4.020-1build2_i386.deb) ...
Selecting previously unselected package mariadb-client-core-5.5.
Unpacking mariadb-client-core-5.5 (from .../mariadb-client-core-5.5_5.5.28-mariadb-a1~precise_i386.deb) ...
Selecting previously unselected package mariadb-client-5.5.
Unpacking mariadb-client-5.5 (from .../mariadb-client-5.5_5.5.28-mariadb-a1~precise_i386.deb) ....
Selecting previously unselected package mariadb-server-core-5.5.
Unpacking mariadb-server-core-5.5 (from .../mariadb-server-core-5.5_5.5.28-mariadb-a1~precise_i386.deb) ....
Selecting previously unselected package mariadb-server-5.5.
Unpacking mariadb-server-5.5 (from .../mariadb-server-5.5_5.5.28-mariadb-a1~precise_i386.deb) ....
 * Stopping MariaDB database server mysqld                                                                                                                                                                                             [ OK ]
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up mysql-common (5.5.28-mariadb-a1~precise) ...
 
Configuration file `/etc/mysql/my.cnf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** my.cnf (Y/I/N/O/D/Z) [default=N] ? N
Setting up libmysqlclient18 (5.5.28-mariadb-a1~precise) ...
Setting up libdbd-mysql-perl (4.020-1build2) ...
Setting up libmariadbclient18 (5.5.28-mariadb-a1~precise) ...
Setting up mariadb-client-core-5.5 (5.5.28-mariadb-a1~precise) ...
Setting up mariadb-client-5.5 (5.5.28-mariadb-a1~precise) ...
Setting up mariadb-server-core-5.5 (5.5.28-mariadb-a1~precise) ...
Setting up mariadb-server-5.5 (5.5.28-mariadb-a1~precise) ...
 * Stopping MariaDB database server mysqld                                                                                                                                                                                             [ OK ]
 * Starting MariaDB database server mysqld                                                                                                                                                                                             [ OK ]
 * Checking for corrupt, not cleanly closed and upgrade needing tables.
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

This also means that any attempt to run BOA or Barraccuda updates - will kill MariaDB
simply because Ubuntu will drag in the new update dependants
- > mysql-common [5.5.29-0ubuntu0.12.04.1
 
(now, precise-security, precise-updates)
 
instead of 5.5.28-mariadb-a1~precise (<NULL>)]

Comment #8

ethnovode commented 23 January 2013 at 23:43

Thanks for the infos !

Edit : Oh, you already have a fix in ! Awesome.

Comment #9

omega8cc commented 24 January 2013 at 00:15

Status:

Active

» Needs review

So, a bit of Pin-Priority magic was required to force MariaDB install properly. You need to create /etc/apt/preferences file and put there this:

Package: *
Pin: origin repo.percona.com
Pin-Priority: 1003

Package: *
Pin: origin ftp.osuosl.org
Pin-Priority: 1002

Then run install or upgrade as usual.

We need to test this again on clean install and upgrades both for Ubuntu Precise and Lucid to make sure it doesn't cause any side effects. It shouldn't, but who knows.

Comment #10

omega8cc commented 24 January 2013 at 00:16

Status:

Needs review

» Fixed

The commit: http://drupalcode.org/project/barracuda.git/commit/182ff06

Comment #11

omega8cc commented 24 January 2013 at 02:39

Now it is fixed via wrappers also for stable BOA-2.0.5: http://drupalcode.org/project/barracuda.git/commit/5c9f845

Comment #12

lynnewu commented 24 January 2013 at 16:48

I'm happy to re-try this, but am not sure if I need to specify a particular commit(?) (branch?) when I wget BOA.sh.txt?

Should I use in-stable/in-head?

Thanks.

Comment #13

omega8cc commented 24 January 2013 at 17:12

It fixes itself on the wrappers level, when you run always forced:

wget -q -U iCab http://files.aegir.cc/BOA.sh.txt
bash BOA.sh.txt

So it just works also for stable BOA-2.0.5 - both install and upgrades.

Comment #14

lynnewu commented 24 January 2013 at 20:00

That worked perfectly using:

boa in-stable public MYHOST.MYDOMAIN.org MY.NAME@gmail.com o1 max

Environment: Ubuntu Server 12.04.1 LTS on a VirtualBox VM

Thank you very, very much. Do you want the successfull installation log for reference?

Comment #15

omega8cc commented 24 January 2013 at 20:17

Thanks for the confirmation. We don't need more logs, we have tested this many times already :)

Comment #16

7 February 2013 at 20:20

Status:

Fixed

» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Ubuntu Precise breaks install and upgrade by trashing MariaDB

Comments

Comment #1

Comment #2

Comment #3

Comment #4

Comment #5

Comment #6

Comment #7

Comment #8

Comment #9

Comment #10

Comment #11

Comment #12

Comment #13

Comment #14

Comment #15

Comment #16

News items

Our community

Documentation

Drupal code base

Governance of community