On Monday, 09 August 2010 13:35:43 +0100,
Martin Simmons wrote:
> > > what is the output of 'ldd /usr/sbin/bacula-sd' ?
> > # ldd /usr/sbin/bacula-sd
> > libz.so.1 => /usr/lib64/libz.so.1 (0x00000032b9000000)
> > libbacpy-5.0.1.so => not found
> > libbaccfg-5.0.1.so => not found
> > libbac-5.0.1.so => not found
> > libpthread.so.0 => /lib64/libpthread.so.0 (0x00000032b8400000)
> > libdl.so.2 => /lib64/libdl.so.2 (0x00000032b8000000)
> > libssl.so.6 => /lib64/libssl.so.6 (0x00000032bb000000)
> > libcrypto.so.6 => /lib64/libcrypto.so.6 (0x00000032ba800000)
> > libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00000032ba000000)
> > libm.so.6 => /lib64/libm.so.6 (0x00000032b8800000)
> > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000032ba400000)
> > libc.so.6 => /lib64/libc.so.6 (0x00000032b7c00000)
> > /lib64/ld-linux-x86-64.so.2 (0x00000032b7800000)
> > libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2
> > (0x00000032bc400000)
> > libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00000032bdc00000)
> > libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00000032bcc00000)
> > libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00000032bd800000)
> > libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0
> > (0x00000032be000000)
> > libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00000032bc800000)
> > libresolv.so.2 => /lib64/libresolv.so.2 (0x00000032bd400000)
> > libselinux.so.1 => /lib64/libselinux.so.1 (0x00000032b9400000)
> > libsepol.so.1 => /lib64/libsepol.so.1 (0x00000032b8c00000)
> > Apparently, in spite of being the libraries in the operating system,
> > for some reason it is not finding them.
> It looks like you are running a 64-bit bacula-sd, so the libraries
> should be in /usr/lib64.
> The files you found are in /usr/lib, which are normally 32-bit.
> Either you have the 32-bit libraries installed by accident or the
> 64-bit libraries are installed in the wrong place (broken rpm?).
Indeed, I'm using CentOS 5.5 amd64. I was not doing the installation
with RPM packages, but compile the source code obtained at the official
site of Bacula. On sunday, doing tests comparing with the installation
done with packages RPM, I realized that the difference was in which the
libraries were in /usr/lib64.
Doing again the configuration using this time the --libdir=/usr/lib64
parameter, the problem was not reproduced. What it is strange to me is
that in an installation of Debian Lenny amd64, I didn't do the
configuration using --libdir=/usr/lib64 and in spite of putting the
libraries in /usr/lib, I did not have the problem occurred in CentOS.
What can be the difference?
Thanks for your reply.
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598
Description: Digital signature
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net