Sometimes it is necessary to perform a manual deploy of a malfunctioning managed host when it cannot download replication and processes are failing to start. How can you force the managed host to deploy its Configurationset to address such a problem?
A partially missing, entirely missing, or corrupt Configurationset on a managed host can cause a wide range of issues, including communication problems. Examples of files that fall into this category:
The script /opt/qradar/bin/local_transformation.sh makes it possible to force a managed host to transform the Configurationset for its local use, effectively performing a full deploy on the managed host only.
Before You Begin
The script requires the following preconditions to function:
- The Console is running the Tomcat service.
- The managed host is running Hostcontext.
- No current deploy, add or remove managed host actions are in progress.
- On the console cd to the Configurationsets directory:
Using SCP to copy the following Configurationset files from the Console to the managed host in question:
scp globalset_list.xml zipfile_GEN.full.zip zipfile_QVM.full.zip <managedhost ip>:/store/configservices/configurationsets
- SSH to the managed host. Run the replication .pl script to replicate the Postgress database on the managed host:
Warning: The following command is not to be run on the Console or it will corrupt the Console.
On the same managed host run the transformation.sh script with the following flags to force a full deploy on the managed host:
/opt/qradar/bin/local_transformation.sh -l -fIf successful, the output will display the following:
Starting up... Deployment status set to 'Initiating Deployment' Deployment status set to 'In Progress' Deployment status set to 'Success' Deploy Global Set: Done. local_transformation: End.
Was this topic helpful?
07 December 2020