How to remove the collector from an active/passive cluster manually?
An automatic uninstallation is not possible because the middleware server crashed or was moved to another machine.
Now that the middleware is no longer available, the collector installation on the cluster is orphaned. The primary link between Performance Analysis and cluster is that QAM Service of PA is listed as a Resource in the cluster configuration. In all likelihood, PA QAM service must be listed as a generic service in cluster administrator which means that this QAM Service is not a critical resource and can be deleted from the cluster administrator, without any impact on the cluster.
So to remove manually PA installation in cluster environment you should:
1. Delete QAM launcher cluster resource.
In cluster administrator, under cluster group, QAM launcher service can be seen. Select the service, right-click and delete the service.
2. Now, it is safe to delete QAM service in Windows services.
Navigate to PA installation directory on the shared disk to <install dir>\agents\bin, from cmdline run quest_launcher <port> -unregister on all cluster nodes.
** Copy the 'quest_launcher.exe' from the active node to all passive nodes c: drive. This way you can unregister the QAM service without having to failover.
3. Delete the installation directory and PA collector component is uninstalled on all cluster nodes.
NOTES:
1. If you do not delete the QAM service from cluster resources AND stop the windows QAM service, the cluster resource detects that the linked resource is not running and will be marked in failure state. If it was configured as critical resource, the cluster manager fail whole group and move the resources to another node. So it is important to ensure that the cluster resource is a generic service and it should be deleted, before any state change is done to the windows QAM service.
2. There is only one collector installation on the shared disk in a cluster environment. So there should not be a separate PA installation on the passive node. Only the QAM service is installed and registered on the passive node. As per above notes, QAM service on passive node too must be unregistered to remove the service from Windows services
3. It is important to remember that cluster administrator views PA QAM service (as seen in Windows services) as a cluster resource and thus any state change done to QAM service will have an impact on the cluster resource too. Hence the reason to delete the QAM service under cluster resource first and then move to the actual Windows service and unregister the service (this stops the Windows service and deletes the service)
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center