-
Title
How to troubleshoot issues when the agent is unable to connect to the policy server? -
Description
If sudo commands are failing and it is suspected that the issues lies in the agent's ability to communicate with the policy server what troubleshooting steps should be taken? -
Resolution
RESOLUTION:
Step 1. Ensure that the agent is able to properly resolve the hostname of the policy server. This should include short names, long names and reverse lookup.
nslookup hostname
nslookup hostname.domainname
nslookup 10.10.10.10
Step 2. Make sure the policy servers are responding by running;
/opt/quest/sbin/pmpluginloadcheck
Step 3. If the issues persists collect traces for the following processes by running these commands
/opt/quest/sbin/pmmasterd -z on
/opt/quest/sbin/pmpluginloadcheck -z on
This will create files in /tmp labelled;
pmpluginloadcheck.trc
pmmasterd.trc
These can be included when opening a case for support for analysis.
To turn off tracing please run;
/opt/quest/sbin/pmmasterd -z off
/opt/quest/sbin/pmpluginloadcheck -z offOther files to collect:
/etc/opt/quest/qpm4u/pm.settings
/var/log/pm*.log
output from the following commands:
/opt/quest/sbin/pmplugininfo
/opt/quest/sbin/pmpolicyplugin -s/opt/quest/sbin/pmsrvinfo
/opt/quest/sbin/pmpolicy masterstatus
sudo -V
df -k
uname -a