SCSP Agent stops communicating with SCSP manager after glibc library update
|Article:TECH169788|||||Created: 2011-09-16|||||Updated: 2012-07-28|||||Article URL http://www.symantec.com/docs/TECH169788|
The Symantec Critical Systems Protection (SCSP) agent is installed on a Redhat Linux server and was functioning normally. After running the Yum package update tool several Linux install packages were downloaded and installed for an IBM WebSphere application. The SCSP 5.2.8 agent then stopped communicating with the SCSP manager unexpectedly.
Redhat Linux RHEL 5.5 server with the 2.6.18-194.3.1.el5 kernel. The SCSP 5.2.8 agent and other applications such as IBM WebSphere are installed.
The installation package for the IBM WebSphere application updates several glibc library files which caused a conflict with the current SCSP 5.2.8 agent installation.
The Redhat Linux server was completely rebuilt after the issue with the installation packages was discovered. After the server was rebuilt the SCSP 5.2.8 agent was installed first followed by the library packages for the IBM WebSphere application. The SCSP 5.2.8 agent is now communicating with the SCSP policy manager as expected.
The attachment contains specific information about which glibc library files were updated for the IBM WebSphere application using the Yum update utility.
Article URL http://www.symantec.com/docs/TECH169788