Single Node Upgrade from 4.25 to 4.26¶

This guide will lead you through the steps specific for upgrading from a NetEye Single Node installation from version 4.25 to 4.26. You must have successfully completed the Update Procedure before attempting to start the upgrade procedure.

Warning

Remember that you must upgrade sequentially without skipping versions, therefore an upgrade to 4.26 is possible only from 4.25; for example, if you have version 4.21, you must first upgrade to the 4.22, then 4.23, and so on.

Before starting an upgrade, you should very carefully read the latest release notes on NetEye’s blog and check the feature changes and deprecations specific to the version being upgraded. You should check also the whole section Breaking Changes below.

The remainder of this section is organised as follows. Section Breaking Changes introduces substantial changes that users must be aware of before starting the upgrade procedure and may require to carry out some tasks before starting the upgrade; section NetEye Single Node Upgrade Procedure presents the actual procedure, and finally section Additional Tasks shows which tasks must be executed after the upgrade procedure has been successfully executed.

Breaking Changes¶

OCS Inventory NG Plugin for GLPI¶

Custom OCS Servers

NetEye 4.26 upgrades the OCS Inventory NG plugin for GLPI to version 1.7.3. The new version of the plugin changes the encryption method used to store the password used to connect to the OCS Inventory database. This means that the passwords stored before the upgrade will fail to be loaded once NetEye is upgraded to version 4.26.

NetEye 4.26 automatically resets the passwords for the db user glpi_ocsinventoryng, in such a way that all OCS Servers authenticated by the user glpi_ocsinventoryng will continue working after the upgrade.

If inside OCS Inventory NG plugin for GLPI you configured instead an OCS Servers that authenticates with a db user different than glpi_ocsinventoryng, then the plugin will stop working due to its inability to decrypt the passwords. In such cases, please refer to the official channels: sales, consultants, or support portal.

OCS Inventory Server¶

Database Schema Changes: memories.CAPACITY migration

NetEye 4.26 updates the schema of the OCS MySQL database. One of those updates is applied to the CAPACITY column of the memories table. Prior to the upgrade, string values (VARCHAR(255)) could be stored in CAPACITY column, while after the upgrade the values are restricted to integers only.

In some cases the OCS agents still send string values like < 1 or No.

We strongly suggest to make sure the CAPACITY column does not contain values other than integers and perform backup of the table. During the upgrade, the neteye_secure_install command will replace the string values with the NULL value. Then we suggest to check if the agents that sent the string values continue to send data correctly. Otherwise, they should be updated.

Database Credentials: rpmnew migration

NetEye 4.26 also updates OCS modules to version 2.10.0. The update produces the two following rpmnew files, related to ocsinventory-server httpd configurations:

/etc/httpd/conf.d/ocsinventory-server-restapi.conf.rpmnew
/etc/httpd/conf.d/ocsinventory-server.conf.rpmnew

To avoid producing these rpmnew files in the future, we changed the way in which credentials are passed to the server’s configuration file, adopting an environment variable stored in the /neteye/shared/httpd/conf/sysconfig/ocsinventory-credentials sysconfig file.

For this reason, the database credentials needs to be migrated manually, along with the rpmnew files. The migration can be performed according to the procedure below.

Retrieve the current password used by the database user from the /etc/httpd/conf.d/ocsinventory-server-restapi.conf file, such as:

$ENV{OCS_DB_LOCAL} = 'ocsweb';
$ENV{OCS_DB_USER} = 'ocsserver';
$ENV{OCS_DB_PWD} = 'ocsserver_user_password';
$ENV{OCS_DB_SSL_ENABLED} = 0;

Copy the environment variable template file, removing the tpl extension:

neteye# cp /neteye/shared/httpd/conf/sysconfig/ocsinventory-credentials.tpl /neteye/shared/httpd/conf/sysconfig/ocsinventory-credentials

Add the password retrieved during Step 1 to the environment file we just created from the template. In our example this will result in:

#####################################
# OCS Inventory credentials sysconfig file
####################################
# This file contains the password used by the ocsserver user
# to access the ocsweb DB.
OCS_DB_PWD=ocsserver_user_password

Migrate the rpmnew keeping as password the newly introduced environment variable (see the Migrate RPM Configuration section for further information)

NetEye Single Node Upgrade Procedure¶

To perform the upgrade, run from the command line the command:

neteye# (nohup neteye upgrade &) && tail --retry -f nohup.out

All the tasks carried out by the command are listed in section neteye upgrade; a dedicated section provides directions in case the command fails.

Additional Tasks¶

This section lists the tasks that must be carried out manually, because they are not part of the neteye upgrade command.

In this release, no additional task is required.