Zurück
-
Titel
After upgrading server receiving the error "This host has not been configured as a policy server" -
Beschreibung
After installing a Privilege Manager hotfix on the secondary server now pmsrvconfig reports:Policy Server Configuration:----------------------------Privilege Manager version : 6.0.0 (064)Listening port for pmmasterd daemon : 12345Comms failover method : randomComms timeout(in seconds) : 10Policy type in use : pmpolicyGroup ownership of logs :- No group has been configured for log ownershipGroup ownership of policy repository :- No group has been configured for policy ownershipPolicy server type :- This host has not been configured as a policy serverPrimary policy server for this group :- No primary policy server has been configuredGroup name for this group :- No policy server group has been configuredLocation of the repository :- No policy server group has been configuredHosts in the group :- No policy group has been configuredAttempts to run "pmsrvconfig -a -v s pmserver" produce:<snip>*** Updating settings file [ OK][FAIL]- ERROR: Unsupported policy mode: unknown- ERROR: Configuration of qpm4u unsuccessful.- ERROR: Installation log file is /opt/quest/qpm4u/install/pmsrvconfig_output.log -
Lösung
The pmlogGroup setting was missing from the pm.setttings file, the entry should be something like:pmlogGroup pmlogAlso the pmlog group should be group owner of all the eventlog database files and keystroke log files and directories. This should be done on all policy servers, once you do this you can run pmsrvconfig again.