SpectroServer - liblzma.so.5 no version information available message
search cancel

SpectroServer - liblzma.so.5 no version information available message

book

Article ID: 236503

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction



The following error message appears in the VNM.out of our SpectroServers:

spectrum:/usr/spectrum/SS> cat VNM.OUT | head -3
/usr/spectrum/SS/SpectroSERVER: /usr/lib64/liblzma.so.5: no version information available (required by /opt/SPECTRUM/lib/../SS/libxml2.so.2)
Feb 09 15:33:05 : /usr/spectrum/SS/SpectroSERVER starting
Feb 09 15:33:05 : MTS enabled, thread heaps = 3
**************************************************************************


The further check with the ldd command resulted in the following information:

spectrum:/usr/spectrum/> ldd ./SS/libxml2.so.2
./SS/libxml2.so.2: /usr/lib64/liblzma.so.5: no version information available (required by ./SS/libxml2.so.2)
        linux-vdso.so.1 (0x00007ffc235db000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f0e49c90000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f0e49a79000)
        liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007f0e49853000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f0e49556000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f0e491b1000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f0e4a1f9000)
        libpthread.so.0 => /lib64/noelision/libpthread.so.0 (0x00007f0e48f94000)



The lib is present in the specified directory.

spectrum:/usr/spectrum/> ll /usr/lib64/liblzma*
lrwxrwxrwx 1 root root     16 Dec 22 08:21 /usr/lib64/liblzma.so.5 -> liblzma.so.5.0.5
-rwxr-xr-x 1 root root 154160 May 27  2019 /usr/lib64/liblzma.so.5.0.5

 

 

Environment

Release : 21.2.6
Component : Spectrum Core / SpectroSERVER

Cause


SuSe Support had informed the client that there is no version information available

  "But in this case the liblzma does not bring a symbol definition version because there was no need for such a marker in this version."

Resolution


This error was resolved with an updated version of liblzma (liblzma.so.5.2.3) from SuSe support. Since this version was
   implemented the error is no longer seen in the VNM.OUT log