UNable to complete boa 2.0.7 install using percona or upgrade to 2.0.7 with percona

I'm afraid we didn't test Percona enough, since after its critical bugs in two releases in a row, which caused servers crashes, we have switched everything to MariaDB and we recommend to avoid Percona after this experience.

The _DB_ENGINE=InnoDB is a correct default for a new feature, since now you can specify default database engine. If you will specify MyISAM, it will affect only newly created Drupal 6 sites, since Drupal 7 forces InnoDB anyway. That said, this has nothing to do with these problems here.

addtl info

Well, switching to MariaDB is easy, you just change it to _DB_SERVER=MariaDB in the /root/.barracuda.cnf and run the upgrade.

However, we should still support Percona anyway, because some people may still use it, and we don't want to drop it altogether - unless they will do the same bad things in a row again.

We (at omega8.cc) also don't use Ubuntu, but we still support it in BOA because some people prefer it over Debian for some weird reasons I don't understand.

@mclendening Thanks! It's nice to hear that!

@EdNet - I just tried upgrade on Debian Squeeze from MariaDB to Percona - no issues. Then clean install with Percona on Debian Squeeze gave me this weird error, which is simply a result of error handling and not a real issue, because Percona was installed and running just fine.

Barracuda [Sat Apr  6 00:13:32 UTC 2013] ==> INFO: Installing DNS cache pdnsd server, please wait...
Barracuda [Sat Apr  6 00:13:51 UTC 2013] ==> INFO: DNS cache pdnsd server installation completed
Barracuda [Sat Apr  6 00:13:53 UTC 2013] ==> INFO: Updating apt sources
Barracuda [Sat Apr  6 00:13:55 UTC 2013] ==> INFO: We will use Debian mirror ftp.debian.org
Barracuda [Sat Apr  6 00:13:59 UTC 2013] ==> INFO: Running aptitude update, please wait...
Barracuda [Sat Apr  6 00:15:06 UTC 2013] ==> INFO: Installing required libraries and tools
Barracuda [Sat Apr  6 00:15:06 UTC 2013] ==> NOTE! This step may take a few minutes, please wait...
Barracuda [Sat Apr  6 00:16:51 UTC 2013] ==> INFO: Testing Nginx version...
Barracuda [Sat Apr  6 00:16:53 UTC 2013] ==> INFO: Installed Nginx version nginx/1.2.7, upgrade required
Barracuda [Sat Apr  6 00:16:55 UTC 2013] ==> INFO: Installing Nginx, please wait...
Barracuda [Sat Apr  6 00:17:35 UTC 2013] ==> INFO: Installing Percona, please wait...
Barracuda [Sat Apr  6 00:19:02 UTC 2013] ==> INFO: Running aptitude full-upgrade again, please wait...
Barracuda [Sat Apr  6 00:19:15 UTC 2013] ==> INFO: Testing Nginx version...
Barracuda [Sat Apr  6 00:19:17 UTC 2013] ==> INFO: Installed Nginx version nginx/1.3.15, no upgrade required
Barracuda [Sat Apr  6 00:19:19 UTC 2013] ==> INFO: Installing /usr/bin/wkhtmltopdf x86_64 version, please wait...
Barracuda [Sat Apr  6 00:19:23 UTC 2013] ==> INFO: Installing /usr/bin/wkhtmltoimage x86_64 version, please wait...
Barracuda [Sat Apr  6 00:19:28 UTC 2013] ==> INFO: Checking SMTP connections, please wait...
Barracuda [Sat Apr  6 00:19:30 UTC 2013] ==> INFO: Installing VnStat monitor, please wait...
Barracuda [Sat Apr  6 00:19:37 UTC 2013] ==> INFO: Installing a few more tools, please wait...
Barracuda [Sat Apr  6 00:19:39 UTC 2013] ==> INFO: Installing IonCube x86_64 version for PHP-FPM, please wait...
Barracuda [Sat Apr  6 00:19:42 UTC 2013] ==> INFO: Installing PHP-FPM 5.3.23, please wait...
Barracuda [Sat Apr  6 00:23:31 UTC 2013] ==> INFO: Installing PhpRedis for PHP-FPM 5.3.23, please wait...
Barracuda [Sat Apr  6 00:23:49 UTC 2013] ==> INFO: Installing UploadProgress for PHP-FPM 5.3.23, please wait...
Barracuda [Sat Apr  6 00:23:59 UTC 2013] ==> INFO: Installing JSMin for PHP-FPM 5.3.23, please wait...
Barracuda [Sat Apr  6 00:24:17 UTC 2013] ==> INFO: Installing New Relic Apps and Server Monitor, please wait...
Barracuda [Sat Apr  6 00:24:57 UTC 2013] ==> INFO: Installing Bazaar (bzr) 2.6b2, please wait...
Barracuda [Sat Apr  6 00:25:42 UTC 2013] ==> INFO: Installing lshell, please wait...
Barracuda [Sat Apr  6 00:25:47 UTC 2013] ==> INFO: Installing latest Pure-FTPd server, please wait...
Barracuda [Sat Apr  6 00:26:22 UTC 2013] ==> INFO: Installing Redis update for Debian/squeeze, please wait...
Barracuda [Sat Apr  6 00:26:56 UTC 2013] ==> INFO: Generating random password for Redis server
Barracuda [Sat Apr  6 00:27:13 UTC 2013] ==> INFO: Generating random password for Percona
Barracuda [Sat Apr  6 00:27:15 UTC 2013] ==> INFO: OS and services installation completed
Barracuda [Sat Apr  6 00:27:17 UTC 2013] ==> ALRT: Percona server not running properly!
Barracuda [Sat Apr  6 00:27:17 UTC 2013] ==> EXIT: We can't proceed with installation and will exit now
Barracuda [Sat Apr  6 00:27:17 UTC 2013] ==> HINT: Please check /var/backups/barracuda-install-130406-0012.log for more information,
Barracuda [Sat Apr  6 00:27:17 UTC 2013] ==> HINT: (re)start Percona server and then run installer again
Barracuda [Sat Apr  6 00:27:17 UTC 2013] ==> Bye
Octopus [Sat Apr  6 00:27:18 UTC 2013] ==> ALRT: Percona server not running properly!
Octopus [Sat Apr  6 00:27:18 UTC 2013] ==> EXIT: We can't proceed and will exit now
Octopus [Sat Apr  6 00:27:18 UTC 2013] ==> HINT: Please (re)start Percona server and then run installer again
Octopus [Sat Apr  6 00:27:18 UTC 2013] ==> Bye

ocean:~# ps axf | grep mysql
 6117 ?        S      0:00 /bin/sh /usr/bin/mysqld_safe
 6185 ?        Sl     0:00  \_ /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/var/lib/mysql/ocean.ams.host8.biz.err --pid-file=/var/lib/mysql/ocean.ams.host8.biz.pid
24276 pts/3    S+     0:00      \_ grep --color=auto mysql
ocean:~#

The problem is that we have had that workaround with another database server restart to avoid this issue, so it will properly use generated config, but we have removed it as redundant, because it is not needed in MariaDB - see here: http://drupalcode.org/project/barracuda.git/commit/20dbd31

Without this extra restart, the result is like below:

ocean:~# ls -la /var/run/mysqld/mysqld.pid
ls: cannot access /var/run/mysqld/mysqld.pid: No such file or directory
ocean:~# ls -la /var/run/mysqld/mysqld.sock
srwxrwxrwx 1 mysql mysql 0 Apr  6 00:18 /var/run/mysqld/mysqld.sock=
ocean:~#

While our code does this check:

if [ ! -e "/var/run/mysqld/mysqld.pid" ] || [ ! -e "/var/run/mysqld/mysqld.sock" ] ; then
  _DB_SERVER_TEST=`mysql -V 2>&1`
  if [[ "$_DB_SERVER_TEST" =~ "MariaDB" ]] ; then
    _DB_SERVER=MariaDB
  else
    _DB_SERVER=Percona
  fi
  msg "ALRT: $_DB_SERVER server not running properly!"
  msg "EXIT: We can't proceed and will exit now"
  msg "HINT: Please (re)start $_DB_SERVER server and then run installer again"
  msg "Bye"
  exit 1
fi

We simply need to revert this change and use the extra restart only for Percona.

Wait, no, this is because our config file is missing, ouch.

root@ocean:~# service mysql restart
Stopping MySQL (Percona Server): mysqld.
Starting MySQL (Percona Server) database server: mysqld ..
Checking for corrupt, not cleanly closed and upgrade needing tables..
root@ocean:~#

ocean:~# ls -la /var/run/mysqld/mysqld.pid
ls: cannot access /var/run/mysqld/mysqld.pid: No such file or directory
ocean:~#

ocean:/etc/mysql# ls -la
total 20K
drwxr-xr-x  3 root root 4.0K Apr  6 00:18 ./
drwxr-xr-x 97 root root 4.0K Apr  6 00:27 ../
drwxr-xr-x  2 root root 4.0K Mar  6 18:14 conf.d/
-rw-------  1 root root  333 Apr  6 00:18 debian.cnf
-rwxr-xr-x  1 root root 1.3K Mar  6 18:08 debian-start*

So Percona comes *without* /etc/mysql/my.cnf config file, which is just weird and it causes that mess on initial install after we have changed a bit the order of config updates to be able to tune also Jetty configuration, which exposed that Percona not nice behaviour.

Anyway, fix committed: http://drupalcode.org/project/barracuda.git/commit/0a33d50

Thanks for the report!

Updating status, since it is important enough to release BOA-2.0.8.

Yet another reason to use MariaDB: http://www.mysqlperformanceblog.com/2013/04/24/percona-server-5-5-30-30-...

In our last 5.5 series release of Percona Server, we included a regression in the RPM packaging that prevented the server from restarting following an upgrade — instead, the server would remain stopped after the upgrade was completed regardless of its state before updating. This caused some problems for some users, especially if automatic upgrading was configured on machines with running database servers.

addtl info