Symantec Endpoint Protection (SEP) for Linux displays "error while loading shared libraries" in system logs or at the command-line. The client GUI displays Auto-Protect: Disabled and Scan: Unknown status.
SEP for Linux (any version)
Example errors from command-line or /var/log/messages:
rtvscand: /opt/Symantec/symantec_antivirus/rtvscand: error while loading shared libraries: libecomlodrlin.so: cannot open shared object file: No such file or directory
smcd: /opt/Symantec/symantec_antivirus/smcd: error while loading shared libraries: libsep-util.so.1: cannot open shared object file: No such file or directory>
When run without any parameters, ldconfig creates the necessary links and cache to the most recent shared libraries found in the directories specified in /etc/ld.so.conf, which contains the single line "include ld.so.conf.d/*.conf". Among things, directory /etc/ld.so.conf.d contains file symav.conf, which includes a reference to /opt/Symantec/symantec_antivirus.
When /etc/ld.so.cache is removed and ldconfig is used with the -n parameter, only directories specified on the command-line are processed and /opt/Symantec/symantec_antivirus is ignored.
/opt/Symantec/symantec_antivirus contains shared libraries libcx_lib.so, libduluxcallback.so, libecomlodrlin.so, libLuxCustomerLogger.so, libluxSEPCallback.so(.1), liblux.so, libpatchapp.so, libsepcommon.so(.1), libsep-cve.so(.1), libsep-util.so(.1), libSlicMan.so(.1), libSyLog.so(.1) and libSymDltCl.s. They are dependent on not only other shared libraries in /lib (e.g. libc.so.6, libm.so.6 and libpthread.so.0), but also other shared libraries in /opt/Symantec/symantec_antivirus/tools (which contains libgcc_s.so.1, liblog4cpp.so.4 and libstdc++.so.6). If its libraries are not present in the shared library cache, SEP for Linux will fail to load its services. As a result of that, AutoProtect will fail to load, scans will no longer run, etc.
Run the following command to cache SEP for Linux' shared libraries and restart smcd: