This article explains how to fix the issue if adding the Managed host is failing with the error mentioned in the screenshot below:

This is a generic error. To understand the exact cause, we need to check qradar.log or qradar.error under /var/log

This will fail in step 10 as per the screenshot below:

As you can see in the description, it is failing while updating the database. But you will be getting the following error from the logs:

Jul 16 09:06:40 ::ffff:127.0.0.1 [hostcontext.hostcontext] [83639d40-1766-42c6-8986-ed98609a6a26/SequentialEventDispatcher] com.q1labs.configservices.capabilities.AddHost: [ERROR] [NOT:0000003000][10.104.4.125/- -] [-/- -]Failed to read output from ssh connection on host 172.29.150.28

Jul 16 09:06:40 ::ffff:127.0.0.1 [hostcontext.hostcontext] [83639d40-1766-42c6-8986-ed98609a6a26/SequentialEventDispatcher] com.q1labs.configservices.common.ConfigServicesException: Failed to read output from ssh connection on host 172.29.150.28

Jul 16 09:06:40 ::ffff:127.0.0.1 [hostcontext.hostcontext] [83639d40-1766-42c6-8986-ed98609a6a26/SequentialEventDispatcher] com.q1labs.configservices.capabilities.AddHost: [ERROR] [NOT:0000003000][10.104.4.125/- -] [-/- -]SSH connection or SSH command execution failed. The ip of the host is: <ManagedHostIP>

If the issue is due to the database, you will see that the Postgres services will not be running and will be unable to start them:

[root@jphk-jsa-dn1-new ~]# systemctl start postgresql-qrd.service

Job for postgresql-qrd.service failed because the control process exited with error code.

See "systemctl status postgresql-qrd.service" and "journalctl -xe" for details.

[root@jphk-jsa-dn1-new ~]# systemctl start postgresql-qvm.service

Failed to start postgresql-qvm.service: Unit postgresql-qvm.service not found.

This is due to the fact that the Managed Host didn't install properly

To fix the issue, please reinstall or redeploy the Managed host, which will be added to the deployment.