Filereader failed to start with GLIBCXX not found
search cancel

Filereader failed to start with GLIBCXX not found

book

Article ID: 241827

calendar_today

Updated On:

Products

Data Loss Prevention Data Loss Prevention Core Package Data Loss Prevention Enterprise Suite

Issue/Introduction

When relocating the DLP install the ld.so.conf is set incorrectly and filereader cannot find the correct version of GLIBC

In the Filreader0.log the following error will occur:

SEVERE: File Reader failed to start. Error starting File Reader. /opt/Symantec/ContentExtractionService/15.8.00000/Protect/lib/native/libcontentextractionjni.so: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /opt/Symantec/ContentExtractionService/15.8.00000/Protect/lib/native/libcontentextractionjni.so) No incidents will be detected.

 

Environment

Release : DLP 15.8.x , Redhat 8. x

Component :

Cause

When relocating the DLP install the libstdc++ is not found. 

Resolution

PreReqs:

locate the path of the dlp libstdc++.so files 

find / -iname libstdc++ (NOTE: you will want the files from ServerCommonPlatform folders)

1. edit the dlp-gcc.conf

vi /etc/ld.so.conf.d/dlp-gcc.conf

2. remove the line in the file and replace it from the find command above for example:

3. run ldconfig as root

4. restart DLP services. 

5. check Enforce UI and filereader should start.