After Upgrading Enterprise Management, PolicyFetcher Causes a Memory Leak on the Endpoint

Document ID : KB000028818
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue: After upgrading Enterprise Management, PolicyFetcher is causing a memory leak on the endpoint.

 

Cause of the Issue: This issue occurs due to the fact that the encryption key on the Enterprise Management server gets reverted to the default key during the upgrade. If you were using an encryption key other than the default one, PolicyFetcher is using that key to connect with Enterprise Management and is getting failures.

To verify that this is the case, you should see the following lines in policyfetcher.log:

"trying to connect to host "DH__@ENTMHOSTNAME"
failed to connect to host "DH__@ENTMHOSTNAME",
retrying..." 

On the endpoint, start selang and run the command `host DH__@ENTMHOSTNAME`, where ENTMHOSTNAME is the hostname on which Enterprise Management is installed. If the encryption key is the cause of the issue, you should get an error message saying "ERROR: Unpacking of Data Failed (Command Status)".

 

Resolution: Once you have verified that the encryption key is the cause of the issue, use the sechkey command on the Enterprise Management server to change the encryption key from the default. The command would be `sechkey -d <newkey>`.