Services fail to start with "Failed to get OS Statistics" error
search cancel

Services fail to start with "Failed to get OS Statistics" error


Article ID: 236108


Updated On:


Data Loss Prevention


After applying patches to Linux OS, Detection Server Services failed to start.

Following Error is seen in the Box Monitor Log:

com.vontu.boxmonitor.statistics.SystemStatsTask run
SEVERE: Failed to get OS statistics.
java.lang.UnsatisfiedLinkError: /opt/Symantec/DataLossPrevention/ServerPlatformCommon/15.8.00000/Protect/lib/native/ /lib64/ version `GLIBCXX_3.4.21' not found (required by /opt/Symantec/DataLossPrevention/ServerPlatformCommon/15.8.00000/Protect/lib/native/
 at java.lang.ClassLoader$NativeLibrary.load(Native Method)
 at java.lang.ClassLoader.loadLibrary0(
 at java.lang.ClassLoader.loadLibrary(
 at java.lang.Runtime.load0(
 at java.lang.System.load(
 at com.vontu.statistics.SystemStatsJNI.<init>(
 at com.vontu.statistics.SystemStatsJNI.getInstance(
 at java.util.TimerThread.mainLoop(

The key piece of information in this log (In bold), is that it is trying to load the libstdc++ library located in /lib64, instead of the version that is packaged with DLP (It would be in the DLP Installation Directory instead of /lib64).


Detection Server hosted on RHEL OS


The Dynamic Linker/Loader system in RHEL should load the libraries included with DLP. However, if there are changes made to the configuration for this, it requires that the new configuration be re-loaded. When this happens, the system can become unaware of the DLP libraries that need to be loaded.

It appears that some kernel updates for RHEL can cause the configuration to need to be reloaded.


Log in to the system as root and run the following command:


This will reload the dynamic linker/loader configuration, and the system will again be aware of the libraries included with DLP.