FreeBSD-client under 6.5.x - /libexec/ld-elf.so.1: ./bplist: Undefined symbol "__h_error"

[ejsym]

Hi,

I've got a FreeBSD client system (FreeBSD 7.1, 64-bit). Installation has been done locally, i.e. 6.5 from CD, upgrade to 6.5.3, then hotfix to 6.5.3.1 to have the most current version.

Server initiated backups run without problems, however when I try to execute a command on the client I get the following error:

# ./bplist
/libexec/ld-elf.so.1: ./bplist: Undefined symbol "__h_error"
#

Whatever "bp..."-command I execute from /usr/openv/netbackup/bin I get the same error.

Please note that I've got the 5.x-compatibility libraries installed, from ports, i.e. compat5x-amd64-5.4.0.8_9 to be exact.

The libraries referred to in the FreeBSD client executables of NetBackup are also available on the system:

# ldd bplist
bplist:
        libkvm.so.2 => /usr/local/lib32/compat/libkvm.so.2 (0x280d1000)
        libstdc++.so.4 => /usr/local/lib32/compat/libstdc++.so.4 (0x280d7000)
        libm.so.3 => /usr/local/lib32/compat/libm.so.3 (0x281b4000)
        libc.so.5 => /usr/lib32/libc.so.5 (0x281cf000)
#

i.e. all of the above (libkvm.so.2, libstdc++.so.4,...) are present.

Also, both the kernel and system are fresh, i.e. compiled and installed only a few days ago.


Here are my questions:

o) Has anybody else seen problems like these?

o) What can I do to get the netbackup related commands going on the FreeBSD-client?

Thanks much in advance for your help,
-ewald

[CRZ]

Hi ewald,

I have nothing, and I totally believe you, but just to humor me, could you throw us the `ls -l` output for each path you list above so we can be sure they're REALLY on your system?

That is to say:

# ls -l /usr/local/lib32/compat/libkvm.so.2
# ls -l /usr/local/lib32/compat/libstdc++.so.4
# ls -l /usr/local/lib32/compat/libm.so.3
# ls -l /usr/lib32/libc.so.5

I just want to make sure none of them show anything crazy like a 0 filesize or something like that.

[ejsym]

Hi,

Sure, here we go:

# ls -l /usr/local/lib32/compat/libkvm.so.2
-r--r--r--  1 root  wheel  24957 Apr  7 18:47 /usr/local/lib32/compat/libkvm.so.2
# ls -l /usr/local/lib32/compat/libstdc++.so.4
-r--r--r--  1 root  wheel  1102049 Apr  7 18:47 /usr/local/lib32/compat/libstdc++.so4
# ls -l /usr/local/lib32/compat/libm.so.3
-r--r--r--  1 root  wheel  126743 Apr  7 18:47 /usr/local/lib32/compat/libm.so.3
# ls -l /usr/lib32/libc.so.5
-r--r--r--  1 root  wheel  1047956 Mar 24 14:32 /usr/lib32/libc.so.5
#

and while we're at it:

# uname -v
FreeBSD 7.2-PRERELEASE #1: Thu Apr  2 19:54:52 CEST 2009
#

(Please note, that the above "7.2-PRELEASE #1" is caused by the recent update of the FreeBSD kernel/system I did a few days ago; this is because 7.2 of FreeBSD is to be expected in the near future, hence the name "7.2 Prerelease". I've seen the exact same problem before upgrading my kernel/system, i.e. with plain vanilla FreeBSD 7.1)

Thanks much in advance for your help,
-ewald