Troubleshooting Installation of the Catalogic DPX Client on UNIX and UNIX-like Systems

There are common troubles with installing the Catalogic DPX Client on UNIX and UNIX-like systems, often because users skipped some prerequisites. Again, carefully review the prerequisites before installing the Catalogic DPX Client: Installing the Catalogic DPX Client on Linux or UNIX.

Installation Failed on Linux Because of Insufficient free PE

To enable the Block Data Protection for Linux, you have to have a volume which is part of an LVM volume group. Then, the LVM volume group must have free physical extent (PE) of at least 10%. Free PE is different from free spaces in each volume. For example, you can get the following error at the end of the installation when there is no free PE at all in the volume group even though the volume has ample spaces:

Error: There has been an error.
The free space requirement for Advance Recovery is not satisfied. 
Block DataProtection cannot be installed. 
The minimum required free space is 10% of the allocated space 
of all the logical volumes in the volume group.

In this case, you have to create more free PE in the volume group either by shrinking the volumes in the volume group and then the volume group too while keeping the disk capacity; or, attach a new disk and add it to the volume group so that the new disk can be used with free PE.

See also. For detailed instructions, see the following article:

• Catalogic Knowledge Base: Unable to install DPX Client on Linux due to insufficient free PE.

Adding a Client Node and Getting the Error: “No network route to the host”

When you add a client node to an Enterprise in the HTML5-based DPX Management Interface, you can see the following error:

There is no network route to the host.

When you see this error, check if the firewall in the client system meets the requirement as stated in the following article, and allow all required ports if needed.

See also. Catalogic Knowledge Base: Firewall Support Requirements and Implementation.

Adding a Client Node and Getting the Error: “Did not register with CMAGENT”

When you add a client node to an Enterprise from either one of the DPX Management Interfaces, you can see the following error:

The server on the node did not register with CMAGENT 
within the timeout setting.

If the client node is Linux, ensure that it has the libnss3 plug-in. The installation method varies by operating systems, distributions, and product versions. For example, you can use the following command to install the plug-in on Red Hat Enterprise Linux 8 and its variants:

$ sudo yum install libnss3.so

If the client node is FreeBSD, add this node from the Java-based DPX Management Interface.

The root causes of this error message vary. If you still see this error, contact Catalogic Technical Support.

Installation Logs of the Catalogic DPX Client for UNIX-like Systems

After installing the Catalogic DPX Client for UNIX or UNIX-like systems, you can see the installation log file:

<product directory>/logs/install.<release version>.log

If you selected the default product directory (/opt/DPX/) while installing the Catalogic DPX Client, you can see the log in /opt/DPX/logs/install..log

Copy and provide the installation log file to Catalogic Support when you request their assistance.