The primary and secondary policy servers must be able to communicate with each other and the remote hosts must be able to communicate with the policy servers in the policy group.
For example, if you run the pmloadcheck command on a policy server or PM Agent to determine that it can communicate with other policy servers in the policy group, you may get output similar to the following:
++ Checking host:myhost.example.com (10.10.181.87) ... [FAIL]
There are several possible reasons for failure:
- Policy server host is down
- Network outage
- Service not running on policy server host
These are some ways to verify that the Privilege Manager for Unix service is running properly on the policy server host:
- To verify the policy server configuration, run
# pmsrvinfo
- To verify that the service is running, enter
# ps –ef | grep pmserviced
- To verify that the pmmasterd port is in a listening state on the primary policy server, enter
# netstat –na | grep 12345
- To verify the service is enabled, look for the following in the Privilege Manager configuration file (/etc/opt/quest/qpm4u/pm.settings)
pmmasterdEnabled YES
- To restart the service (on a Linux host), enter
# /etc/init.d/pmserviced restart
-Or-
pmserviced -s
- Check for other communication issues, such as with your firewall, name resolution, dead network interface, and so forth.