If Control Compliance Suite (CCS) 11.5 APU package has been applied in the environment, then the Agent Product Update (APU) or Agent Content Update (ACU) that are applied in future will fail for Linux platforms.
Error seen in CCS Console:
Failed to update content for agent 'agentname'
Error removing package files on agent
error reading reply from update server on agentname
connection closed by remote process
Failed to transfer file 'C:\Program Files (x86)\Symantec\CCS\Reporting and Analytics\DPS\AgentContent\Unix\Linux\intel\agentupdatemanifest.xml' to agent 'agentname'
Error verifying signature of the file /esm/system/agnetname/tmp/agentupdatemanifest.xml
Error seen on agent side in /esm/system/<hostname>/esmupdd.log:
[ERROR] esmupdd: Error verifying signature of the file /esm/system/"agentname"/tmp/agentupdatemanifest.xml
 [2016/05/03 04:52:38:228] [ERROR] esmupdd: gpgv: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
 [2016/05/03 04:52:38:229] [ERROR] esmupdd: Error verifying signature of the file /esm/system/"agentname"/tmp/agentupdatemanifest.xml
This happens because the gpgv file shipped with 11.5 APU package is dynamically linked and when the required dependent libraries are not be found on linux x86, linux 64 bit or linux ppc64 platform agents, then it causes a failure while applying ACU or APU in the future.
Not all of the libraries are installed on the server for gpgv to work properly (these libraries are not included with the CCS agent install).
To fix this issue, we have created a new Agent Product Update (APU) package with a statically linked gpgv file with all the required libraries.
File are available on Liveupdate server and Fileconnect (new file dated from 19th July 2016)
Check to see if there are missing libraries for gpgv. Have the System Administrator run the following command from the /esm/bin/<platform>/ directory on the CCS agent to see if there are any missing required libraires:
If any of the libraries are listed and say 'not found', they will need to be installed manually by the SA. One possible way is to use the yum command to apply the libraries (as shown below), but the SA would be able to determine what is the best way to get the libraries in your environment.
yum install bzip2-libs.i686