SUSE Linux Enterprise Server

This page describes the steps for installing and upgrading NXLog Agent on SUSE Linux Enterprise Server.

Installing NXLog Agent

First, download the appropriate NXLog Agent install file from the NXLog website.

Under the Downloads > NXLog Agent files tab, download the correct archive for your system.

Table 1. Available SLES NXLog Agent files
Platform	Archive
SUSE Linux Enterprise Server 12 AMD64	nxlog-6.9.10227_sles12_x86_64.tar.bz2
SUSE Linux Enterprise Server 15 AMD64	nxlog-6.9.10227_sles15_x86_64.tar.bz2
SUSE Linux Enterprise Server 15 PPC64le	nxlog-6.9.10227_sles15_ppc64le.tar.bz2

Connecting to NXLog Platform

You can configure NXLog Agent to connect to NXLog Platform automatically. The installation looks for the following environment variables to configure the Remote Management (xm_admin) instance in the managed.conf file.

NXP_ADDRESS: The NXLog Platform Agent Management URL and port. The installation sets the Host to this value.
NXP_AGENT_LABEL: Sets the agent_label label to this value.
NXP_OTHER_LABELS: A list of comma-separated key-value pairs, specifying custom labels. Keys and values cannot start with a digit, and spaces will be replaced with underscores (_). A maximum of ten key-value pairs is allowed.

You can use the labels to Set up automatic agent enrollment.

Set these variables from the terminal before executing the installation. For example:

$ export NXP_ADDRESS="agents.example.com:5515"
$ export NXP_AGENT_LABEL="new"
$ export NXP_OTHER_LABELS="key1=value1,key2=value2"

Installing interactively

Use SFTP or a similar secure method to transfer the archive to the target server.

$ tar -xvf nxlog-6.9.10227_sles15_x86_64.tar.bz2

Table 2. NXLog Agent packages in a SLES archive
Package	Description
nxlog-6.9.10227_sles15.x86_64.rpm	The main NXLog Agent package
nxlog-checkpoint-6.9.10227_sles15.x86_64.rpm	Provides the im_checkpoint module
nxlog-dbi-6.9.10227_sles15.x86_64.rpm	Provides the im_dbi and om_dbi modules
nxlog-java-6.9.10227_sles15.x86_64.rpm	Provides the xm_java, im_java, and om_java modules
nxlog-kafka-6.9.10227_sles15.x86_64.rpm	Provides the im_kafka and om_kafka modules
nxlog-odbc-6.9.10227_sles15.x86_64.rpm	Provides the im_odbc and om_odbc modules
nxlog-pcap-6.9.10227_sles15.x86_64.rpm	Provides the im_pcap module
nxlog-perl-6.9.10227_sles15.x86_64.rpm	Provides the xm_perl, im_perl, and om_perl modules
nxlog-python-6.9.10227_sles15.x86_64.rpm	Provides the xm_python, im_python, and om_python modules
nxlog-ruby-6.9.10227_sles15.x86_64.rpm	Provides the xm_ruby, im_ruby, and om_ruby modules
nxlog-systemd-6.9.10227_sles15.x86_64.rpm	Provides the im_systemd module
nxlog-wseventing-6.9.10227_sles15.x86_64.rpm	Provides the im_wseventing module
nxlog-zmq-6.9.10227_sles15.x86_64.rpm	Provides the im_zmq and om_zmq modules

Optional: To change the NXLog Agent user and group for the installation, set the NXLOG_USER and NXLOG_GROUP environment variables. During installation, a new user and group will be created from these environment variables. They will be used for the User and Group directives in nxlog.conf, and to set ownership of the /opt/nxlog directory.
- If the user or group already exists, the installation issues a warning and continues.
- If the user or group creation fails, the installation returns an error and stops.
- The created user and group will be deleted when you uninstall NXLog Agent.
- If the user or group deletion fails, the uninstall issues a warning and continues.
```
$ export NXLOG_USER=nxlog2
$ export NXLOG_GROUP=nxlog2
```
Download the public key file from the NXLog’s public contrib repository and import it to the RPM database.
```
$ sudo rpm --import nxlog-pubkey.asc
```
See Verify the signature of the RPM package for further details.
Install the required NXLog Agent packages and their dependencies. This example installs the main NXLog Agent package only.
```
$ sudo -E zypper install nxlog-6.9.10227_sles15.x86_64.rpm
```
Configure NXLog Agent by editing /opt/nxlog/etc/nxlog.conf.
See Log collection in the NXLog Platform User Guide for more information and configuration examples.
For more details about configuring NXLog Agent to collect logs on Linux, see Linux log sources.

Verify the configuration file syntax.

$ sudo /opt/nxlog/bin/nxlog -v
2025-08-02 08:05:06 INFO configuration OK

Start the service using the service command:
```
$ sudo systemctl start nxlog.service
```

Check that the NXLog Agent service is running with the systemctl command.

$ sudo systemctl | grep nxlog
nxlog.service
loaded active running  NXLog daemon

Upgrading NXLog Agent

To update an NXLog Agent installation to the latest release, use zypper as described in the installation instructions above. We recommend making a backup of the configuration files before starting this process.

$ sudo zypper install nxlog-6.9.10227_sles12.x86_64.rpm

When upgrading, you can configure new NXLog Platform settings by setting the relevant environment variables in addition to the FORCE environment variable. When forcing a configuration update, the installation backs up the nxlog.conf and managed.conf files before applying the changes.

$ export NXP_ADDRESS="agents.example.com" NXP_AGENT_LABEL="sles" FORCE="TRUE"
$ sudo -E zypper install nxlog-6.9.10227_sles12.x86_64.rpm

The same user and group will be used for the upgrade as was used for the original installation. See installation user and group above. Changing to a different user and group during an upgrade is not supported.

Uninstalling NXLog Agent

Use zypper remove to uninstall NXLog Agent. To remove any packages that were dependencies of NXLog Agent but are not required by any other packages, use the --clean-deps option. Verify the operation before going ahead!

$ sudo zypper remove 'nxlog*'

This procedure may not remove all files that were created while configuring NXLog Agent. Likewise, any files created as a result of NXLog Agent’s operations will not be removed. To find these files, examine the NXLog Agent configuration files and check the NXLog Agent installation directory (/opt/nxlog).