This is a discussion on Sybase ASE insists on using tls libraries on CentOS4.2 - why? within the Linux Operating System forums, part of the Unix Operating Systems category; --> G'day all nixers, Having upgraded a RH7.3 server to CentOS 4.2 I am left with a problem getting the ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| G'day all nixers, Having upgraded a RH7.3 server to CentOS 4.2 I am left with a problem getting the Sybase ASE dataserver to start. /opt/sybase-12.5.3/ASE/bin/dataserver: relocation error: /lib/librt.so.1: symbol __librt_multiple_threads, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference It seems that it is trying to use some libraries from the ssl/tls package /lib/tls rather than from /lib as I would expect. I have hacked the ld.so.conf around a bit to no avail - not sure why the kerberos entry is there and I guess the sasl entry is linked to that or the apache install. Given it is mentioned in the $PATH but none of the .rpm's are installed this doesn't seem good. Anyway, how do I remove the systems fixation with the tls libraries? Does the $PATH influence things? Should I yum the missing kerberos bits in to settle it down? Cheers, Frank. Config follows ... [~]# echo $LD_LIBRARY_PATH /opt/sybase-12.5.3/ASE/lib:/opt/sybase-12.5.3/FTS/lib:/opt/sybase-12.5.3/OCS/lib:/opt/sybase-12.5.3/SQLRemote/lib: [~]# echo $PATH /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/ucb:/bin:/usr/bin:/etc:/usr/local/bin:/root/bin:/opt/sybase-12.5.3/ASE/bin:/opt/sybase-12.5.3/OCS/bin:/opt/sybase-12.5.3/SYSAM/bin:/opt/sybase-12.5.3/shared/jre/bin:/root/bin:/etc/rc.d/init.d [~]# [~]# ldd /opt/sybase-12.5.3/ASE/bin/dataserver libdl.so.2 => /lib/libdl.so.2 (0x00d8c000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x001a3000) librt.so.1 => /lib/tls/librt.so.1 (0x00211000) libm.so.6 => /lib/tls/libm.so.6 (0x0054a000) libnsl.so.1 => /lib/libnsl.so.1 (0x00269000) libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x006b4000) libpam.so.0 => /lib/libpam.so.0 (0x002ee000) libc.so.6 => /lib/tls/libc.so.6 (0x00832000) /lib/ld-linux.so.2 (0x00f8f000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00e36000) libaudit.so.0 => /lib/libaudit.so.0 (0x00e95000) [~]# [~]# cat /etc/ld.so.conf include ld.so.conf.d/*.conf /usr/lib /usr/kerberos/lib /usr/lib/sasl # # cd /lib [lib]# ls -l libpthread* librt* libm* libc* -rwxr-xr-x 1 root root 1438761 Oct 9 07:43 libc-2.3.4.so lrwxrwxrwx 1 root root 11 Feb 9 09:23 libcap.so -> libcap.so.1 lrwxrwxrwx 1 root root 14 Feb 9 09:05 libcap.so.1 -> libcap.so.1.10 -rwxr-xr-x 1 root root 10440 Feb 22 2005 libcap.so.1.10 -rwxr-xr-x 1 root root 191046 Oct 9 07:43 libcidn-2.3.4.so lrwxrwxrwx 1 root root 16 Feb 9 09:05 libcidn.so.1 -> libcidn-2.3.4.so lrwxrwxrwx 1 root root 17 Feb 9 09:05 libcom_err.so.2 -> libcom_err.so.2.1 -rwxr-xr-x 1 root root 5668 Aug 23 2005 libcom_err.so.2.1 -rwxr-xr-x 2 root root 25487 Oct 9 07:43 libcrypt-2.3.4.so -rwxr-xr-x 1 root root 824208 Nov 3 04:00 libcrypto.so.0.9.6b -rwxr-xr-x 1 root root 935272 Oct 12 05:48 libcrypto.so.0.9.7a lrwxrwxrwx 1 root root 19 Feb 21 00:04 libcrypto.so.2 -> libcrypto.so.0.9.6b lrwxrwxrwx 1 root root 19 Feb 9 09:07 libcrypto.so.4 -> libcrypto.so.0.9.7a lrwxrwxrwx 1 root root 17 Feb 9 09:05 libcrypt.so.1 -> libcrypt-2.3.4.so -rwxr-xr-x 2 root root 25487 Oct 9 07:43 libcrypt.so.2 lrwxrwxrwx 1 root root 13 Feb 9 09:05 libc.so.6 -> libc-2.3.4.so -rwxr-xr-x 1 root root 176195 Oct 9 07:43 libm-2.3.4.so lrwxrwxrwx 1 root root 13 Feb 9 09:05 libm.so.6 -> libm-2.3.4.so -rwxr-xr-x 1 root root 89667 Oct 9 07:43 libpthread-0.10.so lrwxrwxrwx 1 root root 18 Feb 9 09:05 libpthread.so.0 -> libpthread-0.10.so -rwxr-xr-x 1 root root 44743 Oct 9 07:43 librt-2.3.4.so lrwxrwxrwx 1 root root 14 Feb 9 09:05 librt.so.1 -> librt-2.3.4.so [lib]# [lib]# ls -l /lib/tls total 1840 drwxr-xr-x 2 root root 4096 Feb 9 09:05 i486 drwxr-xr-x 2 root root 4096 Feb 9 09:05 i586 drwxr-xr-x 2 root root 4096 Feb 9 09:05 i686 -rwxr-xr-x 1 root root 1451366 Oct 9 07:43 libc-2.3.4.so lrwxrwxrwx 1 root root 13 Feb 9 09:05 libc.so.6 -> libc-2.3.4.so -rwxr-xr-x 1 root root 176195 Oct 9 07:43 libm-2.3.4.so lrwxrwxrwx 1 root root 13 Feb 9 09:05 libm.so.6 -> libm-2.3.4.so -rwxr-xr-x 1 root root 91889 Oct 9 07:43 libpthread-2.3.4.so lrwxrwxrwx 1 root root 19 Feb 9 09:05 libpthread.so.0 -> libpthread-2.3.4.so -rwxr-xr-x 1 root root 45739 Oct 9 07:43 librt-2.3.4.so lrwxrwxrwx 1 root root 14 Feb 9 09:05 librt.so.1 -> librt-2.3.4.so -rwxr-xr-x 1 root root 27731 Oct 9 07:43 libthread_db-1.0.so lrwxrwxrwx 1 root root 19 Feb 9 09:05 libthread_db.so.1 -> libthread_db-1.0.so [lib]# |
| ||||
| Frank Hamersley wrote: > G'day all nixers, > > Having upgraded a RH7.3 server to CentOS 4.2 I am left with a problem > getting the Sybase ASE dataserver to start. > > /opt/sybase-12.5.3/ASE/bin/dataserver: relocation error: > /lib/librt.so.1: symbol __librt_multiple_threads, version GLIBC_PRIVATE > not defined in file libc.so.6 with link time reference > > It seems that it is trying to use some libraries from the ssl/tls > package /lib/tls rather than from /lib as I would expect. > > I have hacked the ld.so.conf around a bit to no avail - not sure why the > kerberos entry is there and I guess the sasl entry is linked to that or > the apache install. Given it is mentioned in the $PATH but none of the > .rpm's are installed this doesn't seem good. > > Anyway, how do I remove the systems fixation with the tls libraries? > Does the $PATH influence things? Should I yum the missing kerberos bits > in to settle it down? > > Cheers, Frank. > > Config follows ... > > [~]# echo $LD_LIBRARY_PATH > /opt/sybase-12.5.3/ASE/lib:/opt/sybase-12.5.3/FTS/lib:/opt/sybase-12.5.3/OCS/lib:/opt/sybase-12.5.3/SQLRemote/lib: > > [~]# echo $PATH > /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/ucb:/bin:/usr/bin:/etc:/usr/local/bin:/root/bin:/opt/sybase-12.5.3/ASE/bin:/opt/sybase-12.5.3/OCS/bin:/opt/sybase-12.5.3/SYSAM/bin:/opt/sybase-12.5.3/shared/jre/bin:/root/bin:/etc/rc.d/init.d > > [~]# > [~]# ldd /opt/sybase-12.5.3/ASE/bin/dataserver > libdl.so.2 => /lib/libdl.so.2 (0x00d8c000) > libpthread.so.0 => /lib/tls/libpthread.so.0 (0x001a3000) > librt.so.1 => /lib/tls/librt.so.1 (0x00211000) > libm.so.6 => /lib/tls/libm.so.6 (0x0054a000) > libnsl.so.1 => /lib/libnsl.so.1 (0x00269000) > libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 > (0x006b4000) > libpam.so.0 => /lib/libpam.so.0 (0x002ee000) > libc.so.6 => /lib/tls/libc.so.6 (0x00832000) > /lib/ld-linux.so.2 (0x00f8f000) > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00e36000) > libaudit.so.0 => /lib/libaudit.so.0 (0x00e95000) > [~]# > [~]# cat /etc/ld.so.conf > include ld.so.conf.d/*.conf > /usr/lib > /usr/kerberos/lib > /usr/lib/sasl > # > # cd /lib > [lib]# ls -l libpthread* librt* libm* libc* > -rwxr-xr-x 1 root root 1438761 Oct 9 07:43 libc-2.3.4.so > lrwxrwxrwx 1 root root 11 Feb 9 09:23 libcap.so -> libcap.so.1 > lrwxrwxrwx 1 root root 14 Feb 9 09:05 libcap.so.1 -> libcap.so.1.10 > -rwxr-xr-x 1 root root 10440 Feb 22 2005 libcap.so.1.10 > -rwxr-xr-x 1 root root 191046 Oct 9 07:43 libcidn-2.3.4.so > lrwxrwxrwx 1 root root 16 Feb 9 09:05 libcidn.so.1 -> > libcidn-2.3.4.so > lrwxrwxrwx 1 root root 17 Feb 9 09:05 libcom_err.so.2 -> > libcom_err.so.2.1 > -rwxr-xr-x 1 root root 5668 Aug 23 2005 libcom_err.so.2.1 > -rwxr-xr-x 2 root root 25487 Oct 9 07:43 libcrypt-2.3.4.so > -rwxr-xr-x 1 root root 824208 Nov 3 04:00 libcrypto.so.0.9.6b > -rwxr-xr-x 1 root root 935272 Oct 12 05:48 libcrypto.so.0.9.7a > lrwxrwxrwx 1 root root 19 Feb 21 00:04 libcrypto.so.2 -> > libcrypto.so.0.9.6b > lrwxrwxrwx 1 root root 19 Feb 9 09:07 libcrypto.so.4 -> > libcrypto.so.0.9.7a > lrwxrwxrwx 1 root root 17 Feb 9 09:05 libcrypt.so.1 -> > libcrypt-2.3.4.so > -rwxr-xr-x 2 root root 25487 Oct 9 07:43 libcrypt.so.2 > lrwxrwxrwx 1 root root 13 Feb 9 09:05 libc.so.6 -> libc-2.3.4.so > -rwxr-xr-x 1 root root 176195 Oct 9 07:43 libm-2.3.4.so > lrwxrwxrwx 1 root root 13 Feb 9 09:05 libm.so.6 -> libm-2.3.4.so > -rwxr-xr-x 1 root root 89667 Oct 9 07:43 libpthread-0.10.so > lrwxrwxrwx 1 root root 18 Feb 9 09:05 libpthread.so.0 -> > libpthread-0.10.so > -rwxr-xr-x 1 root root 44743 Oct 9 07:43 librt-2.3.4.so > lrwxrwxrwx 1 root root 14 Feb 9 09:05 librt.so.1 -> librt-2.3.4.so > [lib]# > [lib]# ls -l /lib/tls > total 1840 > drwxr-xr-x 2 root root 4096 Feb 9 09:05 i486 > drwxr-xr-x 2 root root 4096 Feb 9 09:05 i586 > drwxr-xr-x 2 root root 4096 Feb 9 09:05 i686 > -rwxr-xr-x 1 root root 1451366 Oct 9 07:43 libc-2.3.4.so > lrwxrwxrwx 1 root root 13 Feb 9 09:05 libc.so.6 -> libc-2.3.4.so > -rwxr-xr-x 1 root root 176195 Oct 9 07:43 libm-2.3.4.so > lrwxrwxrwx 1 root root 13 Feb 9 09:05 libm.so.6 -> libm-2.3.4.so > -rwxr-xr-x 1 root root 91889 Oct 9 07:43 libpthread-2.3.4.so > lrwxrwxrwx 1 root root 19 Feb 9 09:05 libpthread.so.0 -> > libpthread-2.3.4.so > -rwxr-xr-x 1 root root 45739 Oct 9 07:43 librt-2.3.4.so > lrwxrwxrwx 1 root root 14 Feb 9 09:05 librt.so.1 -> librt-2.3.4.so > -rwxr-xr-x 1 root root 27731 Oct 9 07:43 libthread_db-1.0.so > lrwxrwxrwx 1 root root 19 Feb 9 09:05 libthread_db.so.1 -> > libthread_db-1.0.so > [lib]# Hmmm that was a quick fix ... a simple mv of /lib/tls to /lib/tlsxxx and voila - it works. I wonder what else that shimmy might break though? :-( Now the challenge is to find out why that tls path was considered in the first place. So far I haven't found all the probable causes that result in the /lib/tls path being considered - AFAIK the /etc/ld.so.conf, $LD_LIBRARY_PATH and perhaps $PATH are implicated - but none of these has an explicit /lib/tls path in them. Can anyone suggest what the other possibilities might be? Cheers, Frank. |