Return
-
Title
Remove secondary server from Master Policy server list however it still shows on client -
Description
We are decommissioning a secondary policy server from the policy group and PM4Sudo. Secondary server is removed from master server list on the policy servers but it's still in the master server list on client systems when performing pmpluginloadcheck. -
Cause
Product Defect: TFS 784399 -
Resolution
STATUS:
This is fixed in 6.0.0.066 which is currently only available as a pre-release.
You will need to upgrade all the plugin hosts and policy servers before removing the secondary policy server.
When unconfiguring the secondary, you should ensure that the pmserviced daemon is running on the primary.
After unconfiguring, you should do a pmsrvinfo on the primary to verify that secondary has been removed from the list.
A pmpluginloadcheck run on any host in your PM4Sudo environment should only connect to the active policy servers.WORKAROUND:
This needs to be run on every client system that is seeing this issue.
1. Stop the pmpluginloadcheck daemon by running the following:
/opt/quest/sbin/pmpluginloadcheck -s
2. run "ps -ef | grep pmpluginloadcheck" to verify that the daemon has stopped.
3. Remove cache files that contain the name of the decommissioned server in the following directory:
cd /var/opt/quest/qpm4u/.qpm4u/.perfdata
Example command to remove files that contain the name of the decommissioned server.
rm -f `grep -l sudo-server.idm.hal.lab .*`
3. Restart the pmpluginloadcheck daemon
For example on RHEL:
/etc/init.d/pmpluginloadcheck start -
Change Request
784399