Status code 174 while backing up RedHat client or "Incorrectly built binary which accesses errno, h_errno or _res directly"

Problem

Status code 174 while backing up RedHat client or "Incorrectly built binary which accesses errno, h_errno or _res directly"

Error Message

ldd /usr/openv/netbackup/bin/bpcd Incorrectly built binary which accesses errno, h_errno or _res directly. Needs to be fixed.

Solution

This status 174 or INCORRECTLY BUILT BINARY which accesses errno, h_errno or _res directly issue occurs when a version of VERITAS NetBackup (tm) earlier than Feature Pack 6 (FP6) is run on a RedHat Linux client. Earlier versions of NetBackup are compiled for glibc 2.2. RedHat 9 and Advanced Server 3 utilize glibc 2.3. This results in the incorrectly built binary message.

The solution to this problem is to install a supported version of NetBackup on the clients. Currently 4.5 FP6 is the minimum supported version for these operating systems.

A good test to check version compatibility is to run this command:
ldd /usr/openv/netbackup/bin/bpcd on Redhat 9

# ldd /usr/openv/netbackup/bin/bpcd
Incorrectly built binary which accesses errno, h_errno or _res directly. Needs to be fixed.
libnsl.so.1 => /lib/libnsl.so.1 (0x40034000)
libresolv.so.2 => /lib/libresolv.so.2 (0x40049000)
libdl.so.2 => /lib/libdl.so.2 (0x4005b000)
libc.so.6 => /lib/libc.so.6 (0x4005f000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

This is due to the fact that RedHat switched to glibc 2.3 in RedHat 9 instead of glibc 2.2 in earlier versions.
The fix is to install a supported version of NetBackup. Reference the OS compatibility matrix.


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)