FAQ

This page contains answers to frequently asked questions and additional information on how to use KUSANAGI.

Q1. I can't update themes and plugins from the WP Admin Dashboard, what should I do?

A1. If you are using PHP 8.0 or later, you need to change the following line in "wp-config.php":

define('FS_METHOD', 'ftpsockets');

Change it to the following:

define('FS_METHOD', 'ftpext');

Q2. Why can't I use the "kusanagi" commands?

A2. If you cannot use the "kusanagi" commands, please make sure you are a "root" user or a user belonging to the "www" group. (Kusanagi users belong to the ”www” group by default.)
The full path to the "kusanagi" commands is "/opt/local/bin/kusanagi".

Q3-1. The latest image of "KUSANAGI 9 for Vagrant" is available, why hasn't it automatically updated?

A3-1. Vagrant does not automatically download the latest "Box" (image) when it's released.
To download the latest "Box" of "KUSANAGI 9 for Vagrant", run the following command on the host side.

# vagrant box update --box primestrategy/kusanagi9

The latest "Box" will not be deployed into a "KUSANAGI 9 for Vagrant" environment that has already been built.
This is because when "KUSANAGI 9 for Vagrant" built the environment, it made a copy from the "Box" that existed at that time.
To build a "KUSANAGI 9 for Vagrant" environment from the latest "Box", you need to work in a different directory or re-create the environment.

Q3-2. Why did the OS become CentOS Stream 9 when I downloaded the latest image of "KUSANAGI 9 for Vagrant"?

A3-2. Starting from "KUSANAGI 9 for Vagrant" v9.3.2307, the base OS is CentOS Stream 9.
To download the latest "Box" with CentOS Stream 8, please run the following command on the host side.

# vagrant box add primestrategy/kusanagi9-centosstream8

This will download the latest "Box" for CentOS Stream 8.
When executing "vagrant up", please also specify "box" in "Vagrantfile".

Vagrant.configure("2") do |config|
  config.vm.box = "primestrategy/kusanagi9-centosstream8"
:
:
end

As with Q3-1, please note that the latest "Box" will not be deployed into a "KUSANAGI 9 for Vagrant" environment that has already been built.

Q4. When I run an update with "dnf", an error message shows up and I'm not able to update.

A4-1. If you see a message like the one below, a problem has occurred in the processing of package dependencies.

Error message example

(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)


It may be that the repository information still has not be updated.
In such cases, please delete the cache and try again using the command below.

# dnf clean all

If the problem occurs again, KUSANAGI 9 may be in the process of updating its modules when you attempted to update using "dnf", and all dependent packages may not have been published to the repository.
If this is the case, please wait awhile and run the update again.

A4-2. If the following message is output, the error occurred because MariaDB 10.3 has been removed from the repository.

Error message example

Errors during downloading metadata for repository 'mariadb10.3':
  - Status code: 404 for http://mirror.mariadb.org/yum/10.3/centos/8/x86_64/repodata/repomd.xml (IP: 162.55.42.214)
Error: Failed to download metadata for repo 'mariadb10.3': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

As of May 2023, MariaDB 10.3 is no longer supported and has been removed from the MariaDB repository.
It remains in the archive repository, so change the following line from "/etc/yum.repos.d/MariaDB.repo":

baseurl = http://yum.mariadb.org/10.3/centos/$releasever/x86_64

By rewriting as shown below, you will be able to update with the "dnf" command.

baseurl = https://archive.mariadb.org/yum/10.3/centos/$releasever/x86_64

However, since MariaDB 10.3 will never be updated, we recommend upgrading to the latest MariaDB.
The upgrade can be done with the "kusanagi upgrade mariadb" command.

A4-3. If the following message is output, it's because the signature has been changed in the PostgreSQL repository.

Error message example

Error: Failed to download metadata for repo 'pgdg-common': repomd.xml GPG signature verification error: Bad GPG signature)

"pgdg-redhat-repo" will need to be updated as shown below.
In addition, afterwards please disable unnecessary repositories according to the version of PostgreSQL you are using.

# dnf upgrade pgdg-redhat-repo --nogpgcheck

# dnf config-manager set-disabled pgdg\*
# dnf config-manager set-enabled pgdg-common

When Using PostgreSQL 13
# dnf config-manager set-enabled pgdg13

When Using PostgreSQL 14
# dnf config-manager set-enabled pgdg14

When Using PostgreSQL 15
# dnf config-manager set-enabled pgdg15

When Using PostgreSQL 16
# dnf config-manager set-enabled pgdg16

A4-4. If the following message is output, the error occurred because CentOS Stream 8 has been removed from the repository.

Error message example

Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist

As of May 2024, CentOS Stream 8 is no longer supported and has been removed from the CentOS repository.
It remains in the archive repository, so change the following lines starting with mirrorlist= from "/etc/yum.repos.d/CentOS-Stream-*.repo":

mirrorlist=http://mirrorlist.centos.org/?release=$stream&arch=$basearch&repo=AppStream&infra=$infr

By commenting out as shown below. (Bolded parts vary by file.)

#mirrorlist=http://mirrorlist.centos.org/?release=$stream&arch=$basearch&repo=AppStream&infra=$infr

Then, change the following lines starting with #baseurl= respectively:

#baseurl=http://mirror.centos.org/$contentdir/$stream/AppStream/$basearch/os/

By commenting in and rewriting as shown below, you will be able to update with the "dnf" command. (Bolded parts vary by file.)

baseurl=http://vault.centos.org/$contentdir/$stream/AppStream/$basearch/os/

However, since CentOS Stream 8 will never be updated, we recommend upgrading to AlmaLinux OS 8.
For the upgrade procedures, please refer to End of life KUSANAGI 8 / KUSANAGI 9 on CentOS Stream 8.

• Update procedure by executing commands

If manually rewriting the information is difficult, you can update the repository information by executing the following three commands sequentially.

# sed -i 's|^mirrorlist=|#mirrorlist=|' /etc/yum.repos.d/CentOS-*.repo
# sed -i 's|^#baseurl=|baseurl=|' /etc/yum.repos.d/CentOS-*.repo
# sed -i 's|^baseurl=http://mirror.|baseurl=http://vault.|' /etc/yum.repos.d/CentOS-*.repo

A4-5. If the following message is output in the AlmaLinux OS 8 environment, the error occurred because the update has failed due to an outdated GPG key for AlmaStar OS 8.

Import of key(s) didn't help, wrong key(s)?
Public key for alsa-lib-1.2.10-2.el8.x86_64.rpm is not installed. Failing package is: alsa-lib-1.2.10-2.el8.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for mesa-libgbm-23.1.4-2.el8.x86_64.rpm is not installed. Failing package is: mesa-libgbm-23.1.4-2.el8.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

Due to changes made to the AlmaLinux OS 8 GPG key in January 2024, environments that are still using the old key will encounter errors (for details, please see the link below).

AlmaLinux OS - Forever-Free Enterprise-Grade Operating System

In this case, please enter the following command to install a new key on the VM and then try again.

# rpm --import https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux

Q5. The setup screen for KUSANAGI 9 Premium Edition on AlmaLinux OS 8 does not progress beyond "Installing the KUSANAGI…"

A5. It is the same case as A4-5.
As a result, it has been confirmed that some of the processes carried out when initializing the Premium Edition may result in errors.

To check whether or not this is the case, please log in to the target VM via SSH and enter the following command.

# cat /tmp/kusanagi-biz/log/initialize.log

If the results displayed there include a message similar to what is described in A4-5, then it is the same issue.

Import of key(s) didn't help, wrong key(s)?
Public key for alsa-lib-1.2.10-2.el8.x86_64.rpm is not installed. Failing package is: alsa-lib-1.2.10-2.el8.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Public key for mesa-libgbm-23.1.4-2.el8.x86_64.rpm is not installed. Failing package is: mesa-libgbm-23.1.4-2.el8.x86_64
 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

As a countermeasure, please enter the following command, the same as in A4-5, to install a new key on the VM.

# rpm --import https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux

Afterwards, please enter the following command to roll back the setup, and then restart the VM.

# rm -f /tmp/kusanagi-biz/.setup_status
# reboot

After some time has passed, the setup screen will launch again and will complete successfully.