The modules that composed KUSANAGI had been updated. The new versions are as follows.

Use the following command to update modules.

# yum update

The modules that compose KUSANAGI have been updated. The new versions are as follows:

Use the following command to update modules:
# yum update

The modules that composed KUSANAGI had been updated. The new versions are as follows.

Use the following command to update modules.

# yum update

The modules that compose KUSANAGI have been updated. The new versions are as follows:

Use the following command to update modules:

# yum update

The modules that composed KUSANAGI had been updated. The new versions are as follows.

openssl1.0.2j

Use the following command to update modules.

# yum update

We suggest to do upgrade version openssl-1.0.2j as fast as possible because this update includes security fixes issues.
Restart kusanagi with using command as follows when openssl-1.0.2j update is done.

# kusanagi restart

KUSANAGI version upgrade details 8.0.0-3

The bug fix of KUSANAGI 8.0.0 is done.
If you are currently using a previous version, please enter the following command as root user to upgrade to 8.0.0-2

# yum update

The bug fixes and modifications of 8.0.0-3 are as follows.

1. Failure in kusanagi update cert

1. Failure in kusanagi update cert

We recognize the process to get the Let’s Encrypt SSL certificate is failed while using kusanagi update cert.
We fixed this bug in KUSANAGI 8.0.0-3.

KUSANAGI version upgrade details 8.0.0-2

The bug fix of KUSANAGI 8.0.0 is done。
If you are currently using a previous version, please enter the following command as root user to upgrade to 8.0.0-2。

# yum update

The bug fixes and modifications of 8.0.0-2 are as follows.

1. Use kusanagi init can not create DH key sometimes
2. Can not issue SSL certificate with kusanagi provision
3. Failure with kusanagi update cert
4. The specification of specifying FQDN with www by kusanagi provision

1.Use kusanagi init can not create DH key sometimes

After yum update,run the command kusanagi init sometimes can not create the DH key.

It will create the DH key with command kusanagi init in KUSANAGI 8.0.0-2.
If there is already DH key there,though run the command kusanagi init ,the DH key will not be recreated.

2.Can not issue SSL certificate with kusanagi provision

Using kusanagi provision without configuring --email, there will be a dialogue to configure email address,but the processing will not continue to get the Let’s Encrypt SSL certificate.

We fixed this bug in KUSANAGI 8.0.0-2.

3. Failure in kusanagi update cert

Run the command kusanagi update cert turned out to be a failure to get Let’s Encrypt SSL certificate.
We fixed this bug in KUSANAGI 8.0.0-2.

4. The specification of specifying FQDN with www by kusanagi provision

Fulfill the conditions below,with kusanagi provision to specify www.example.com or example.com as a FQDN, both  www.example.com and example.com will be configured as VirtualHosts.

• Both www.example.com and example.com registered as A record of DNS
• exmaple.com registered in whois information

At the time of getting the SSL certificate by Let’s Encrypt with specifying the FQDN  and the email address,both www.example.com and example.com will get the SSL certificate.

There will be the same process at the time of changing FQDN with the command kusanagi setting --fqdn and the time of getting the SSL certificate with command kusanagi ssl .

The modules that composed KUSANAGI had been updated. The new versions are as follows.

Use the following command to update modules.

# yum update

The update of the openssl-1.0.2i with several security fixes,please update as soon as possible.
After you update to openssl-1.0.2i,use the command below to restart the service.

# kusanagi restart

KUSANAGI version upgrade details 7.8.3-5

After bug fix ,KUSANAGI 7.8.3-5 is now available.On every cloud service, if you are a new user, perform the yum system update covered in the ,KUSANAGI initialization,guide to automatically upgrade to 7.8.3-5 .
If you are currently using a previous version, please enter the following command as root user to upgrade to 7.8.3-5.

# yum update -y kusanagi*

The bug fixs and modifications of 7.8.3-5 are as follows:

1. Configuration modification of kusanagi monit
2. Bug fix of kusanagi ssl
3. Option service of kusanagi provision、configuration 、ssl
4. Message addition

1. Configuration modification of kusanagi monit

We modified the configuration of kusanagi monit ,the status code 5xx can response correctly.

When you do the version upgrade,run the command kusanagi monit config ,it is necessary to recreate the configuration file of monit .If you do several provisions,designate the profile of each provision,and run the command kusanagi monit config. at last,you should run the command monit again(kusanagi monit off; kusanagi monit on).

# kusanagi monit config [profile]
# kusanagi monit off
# kusanagi monit on

2.Bug fix of kusanagi ssl

Using the command kusanagi ssl to issue the ssl certification later of Let’s Encrypt ,when the Let’s Encrypt turns out to be a failure,there is a bug that the configuration of the WordPress accidentally rewrited.
We correct this at KUSANAGI 7.8.3-5,when issuing the ssl certification of Let’s Encrypt turns out to be a failure,there will not be a rewrite to WordPress.

3. Option service of kusanagi provision,configuration ,ssl

Commands that can use options start with a “-” such as kusanagi provision,kusanagi configuration ,kusanagi ssl and so on ,It will just ignore the options if you use a undefined option.while for KUSANAGI 7.8.3-5 ,if you use a undefined option,there will be a error message and end.

4. Message addition

When set the ssl certification for kusanagi ssl,kusanagi https,httpd or nginx will not restart.
The reason is that it will confirm the configuration file to make sure if the ssl certification had been correctly changed.
While for KUSANAGI 7.8.3-5,if it is necessary to restart httpd/nginx,we modified that there will be a purport message.
the message will be like this “Please check nginx/httpd config files and restart.”,then you should confirm the configuration file and restart httpd or nginx using commands as follows:

# httpd -t
# nginx -t
# kusanagi restart

The modules that compose KUSANAGI had been updated. The new versions are as follows:

Use the following command to update modules:

# yum update