Category: Imunify360

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

Error

When you try to install Imunify360, you get the following:

[root@stack10 ~]# bash i360deploy.sh IPL
Checking for an update to i360deploy.sh
Downloading i360deploy.sh.repo_version (please wait)
i360deploy.sh is already the latest version (2.58) - continuing
Detecting ostype... centos
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 reason is, latest Imunify360 installer looking for the ipset library. To install that, use the following:

yum install ipset-libs -y

Once done, you should be able to install Imunify360 now.

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.