To report basic information about the configuration of a policy server
-
From the command line, enter:
# pmsrvinfo
This command returns output similar to this:
Policy Server Configuration:
----------------------------
Safeguard version : 6.1.0 (nnn)
Listening port for pmmasterd daemon : 12345
Comms failover method : random
Comms timeout(in seconds) : 10
Policy type in use : sudo
Group ownership of logs : pmlog
Group ownership of policy repository : pmpolicy
Policy server type : primary
Primary policy server for this group : myhost.example.com
Group name for this group : MyPolicyGroup
Location of the repository : file:
////var/opt/quest/qpm4u/.qpm4u/.repository/sudo_repos/trunk
Hosts in the group : myhost.example.com
The "master" copy of the policy file resides in a repository on the primary policy server. Each primary and secondary policy server maintains a "production" copy of the policy file or files. Use the pmpolicy utility to verify that the production copy is current with the master policy.
To compare the production policy file against the master policy on the primary server
- From the command line, enter:
# pmpolicy masterstatus
If the files are in sync, the Current Revision number will match the Latest Trunk Revision number. If someone hand-edited the local copy without using pmpolicy utility commands to commit the changes, "Locally modified" will indicate "YES".
If the production policy is not current with the master policy you can update the production policy with pmpolicy sync.
Related Topics
pmpolicy
When the policy server is not working as expected, use the pmsrvcheck command to determine the state of the server and its configuration.
To verify the policy server is running
- From the command line, enter:
# pmsrvcheck
This command returns output similar to this:
testing policy server [ Pass ]
If the policy server is working properly, the output returns 'pass', otherwise it returns, 'fail'.
Related Topics
pmsrvcheck
The primary and secondary policy servers need to communicate with each other. The Sudo Plugin hosts also need to communicate with the policy servers in the policy group. Run pmpluginloadcheck on the remote hosts to verify that they can communicate with the policy servers in the group.
To determine if there any issues with policy servers in the policy group
From the Safeguard for Sudo host command line, enter:
# pmpluginloadcheck -r
This command has output similar to this:
[0][root@sol10-x86 /]# pmpluginloadcheck -r
** Reporting current availability of each configured master...
* Host:myhost1.example.com (172.16.1.129) ... [ OK ]
** Based on this data, the server list is currently ordered as:
1. myhosts.example.com
Related Topics
pmpluginloadcheck
