Category: Imunify360

ipset: error while loading shared libraries: libipset.so.13: cannot open shared object file: No such file or directory

Troubleshooting Imunify360 Installation on Linux: Resolving Missing Libraries

When installing security tools like Imunify360 on a Linux system, dependency issues can arise due to missing libraries or incompatible configurations. This guide walks you through resolving a common error encountered during installation:

—

The Problem

During installation, you might see an error similar to this:

[root@stack10 ~]# bash i360deploy.sh IPL  
...  
ipset: error while loading shared libraries: libipset.so.13: cannot open shared object file: No such file or directory  
[2022-12-21 04:44:14] Your OS virtualization technology kvm has limited support for ipset in containers. Please, contact Imunify360 Support Team.

The key issue here is the missing libipset.so.13 library, which is required by ipset, a tool used by Imunify360 for managing firewall rules.

—

Step-by-Step Solution

1. Install the ipset-libs Package

Run this command to install the missing library:


sudo yum install ipset-libs -y

—

2. Verify Library Installation

Confirm the library exists:


ls /usr/lib64/libipset.so.13

—

3. Update Dynamic Linker Cache

Update the system’s dynamic linker cache:


sudo ldconfig

—

4. Retry Imunify360 Installation

Re-run the installer:


bash i360deploy.sh IPL

—

5. Address KVM Virtualization Warning

If the error persists:

  • If using a container (e.g., LXC, Docker) or nested virtualization: Contact Imunify360 Support for guidance.
  • For critical systems: Install Imunify360 on a bare-metal or non-containerized environment.

—

Why Does This Happen?

  • Missing Dependencies: The ipset-libs package provides libipset.so.13, which Imunify360 requires.
  • Outdated Repositories: Unupdated package managers may lack the latest versions of required packages.

—

Additional Checks

1. Update Package Repositories


sudo yum clean all  
sudo yum makecache

2. Check ipset Version


ipset --version  
rpm -q ipset ipset-libs

If outdated, reinstall with:


sudo yum reinstall ipset ipset-libs -y

3. Check for Conflicting Packages


rpm -qa | grep ipset

Uninstall conflicting versions if found.

—

Final Notes

  • Documentation First: Always check the Imunify360 documentation for the latest steps.
  • Contact Support: If issues persist, provide:
    • Full error logs.
    • Output of uname -a (system details).
    • Output of rpm -qa | grep ipset.

—

Stay Secure & Updated

By following these steps, you can resolve dependency issues and ensure a smooth Imunify360 installation. Keep your system’s packages updated and verify dependencies before deploying security tools!

Leave a comment below if you encountered other errors during installation—we’re here to help!

Keywords: Imunify360 installation error, libipset.so.13 missing, KVM virtualization limitation, ipset-libs CentOS.

Troubleshooting: Imunify360 database is corrupt. Application cannot run with corrupt database

Error Message:

# service imunify360 start
Starting imunify360: WARNING [+ 3743ms] defence360agent.utils.check_db|DatabaseError detected: database disk image is malformed
WARNING [+ 3766ms] defence360agent.cli.subparsers.common.server|Imunify360 database is corrupt. Application cannot run with corrupt database. Please, contact Imunify360 support team at https://cloudlinux.zendesk.com

Detail Information & Explanation:

If you are using imunify360, an application firewall for linux servers by Cloudlinux team, you might incur an error where it says the database is corrupt. You might first see ‘Imunify360 is not started’ error from the WHM panel and end up getting the above error message as stated. Imunify360 uses a SQL database, located under ‘/var/imunify360/imunify360.db’. This image is checked everytime Imunfi360 tries to start, and if the database is malformed, it would not start. Fortunately, imunify360 comes with tools to handle this database and recover if corrupted.

How to Fix:

First, we start by running database integrity check. This can be done using the following:

imunfiy360-agent checkdb

(From Imunify360 Doc: checkdb  – Check database integrity)

Once done, you can now use ‘migratedb’ to repair and restore if the database is corrupted.

imunify360-agent migratedb

(From Imunify360 Doc: migratedb – Check and repair database if it is corrupted.)

If migratedb fails, the only way to recover this is to reinstall imunify360.