KUSANAGI Update 8.2.0

PostgreSQL can now be used with KUSANAGI. In addition to the existing Maria DB database option, uses can now choose PostgreSQL.

Database selection can be done during KUSANAGI initialization(kusanagi init), and there is now a new command, kusanagi dbinit.

Please check this kusanagi document for details about kusanagi dbinit.

For those using older versions, running the command below with root privileges will update KUSANAGI to 8.2.0.

# yum update

KUSANAGI Update 8.1.2-6

KUSANAGI 8.1.2-6 update with bug fix has been released.

For those using version 8.1.2-5 and earlier, running the command below with root privileges will update KUSANAGI to 8.1.2-6.

# yum update

If you have just performed the most recent update and the leftover cache causes a “no pakages marked for update” error, use the following command and then perform a yum update.

# yum clean all

Bugfixes in KUSANAGI 8.1.2-6

8.1.2-6 fixes the following issues:

If the Mroonga WordPress plugin is enabled, the ‘kusanagi addon remove mroonga’ will succeed, even though it should not.

In version 8.1.2-5 and earlier, there was a bug where removing the WordPress plugin Mroonga from MariaDB while it is activate only deletes the table data and leaves the index and other metadata intact, when it gets deactivated using ’kusanagi addon remove mroonga’.

Thus a new table would not get created after ractivating Mroonga.

This issue was fixed in KUSANAGI 8.1.2-6.

In KUSANAGI 8.1.2-6, on a website provisioned with WordPress on KUSANAGI with an active Mroonga plugin, attempting to remove Mroonga will result in the error message below. Deactivating the Mroonga plugin from profile name ‘xxxxx’ WordPress site and running the remove command again will succeed.

# kusanagi addon remove mroonga
Mroonga WordPress plugin is activated.
Please deactivate mroonga plugin from 'xxxxx' Profile.
add-on remove was aborted
# 

KUSANAGI Update 8.1.2-5

The KUSANAGI 8.1.2-5 update with bug fixes has been released.

For those using version 8.1.2-4 and earlier, running the command below with root privileges will update KUSANAGI to 8.1.2-5.

# yum update

If you have just performed the most recent update and the leftover cache causes a “no packages marked for update” error, use the following command and then perform a yum update.

# yum clean all

Bugfixes in KUSANAGI 8.1.2-5

8.1.2-5 fixes the following issues:

Failure to upgrade MariaDB during kusanagi init

During kusanagi init, there have been cases where referencing the MariaDB10.0 package cache causes upgrading MariaDB10.1 to fail.
This bug has been fixed in KUSANAGI-8.1.2-5.

If there are issues running commands

Redoing kusanagi init after updating to 8.1.2-5 is the most surefire solution, but the method below will also work:

Delete the existing MariaDB package.

# yum remove -y 'MariaDB*' galera

Check the file /etc/yum.repos.d/MariaDB.repo

baseurl = http://yum.mariadb.org/10.0/centos7-amd64
If you see this line, change it to the one below:
baseurl = http://yum.mariadb.org/10.1/centos7-amd64

# yum clean all
# yum install -y MariaDB-devel MariaDB-client MariaDB-server

If the KUSANAGI settings are written in the /etc/my.cnf.d/server.cnf.rpmsave file, copy the [mysql] contents from /etc/my.cnf.d/server.cnf.rpmsave to the [mysqld] contents of /etc/my.cnf.d/server.cnf.

Last, restart MariaDB.

systemctl restart mysql