`Dirty` trick from Linux vendors

Today I wasted several hours to troubleshoot an installation problem on OEL 6.3: GI was unable to install in silent mode due to error ‘File “/etc/resolv.conf” is not consistent across nodes’. I tried almost everything and even checked an md5 hash of the files.

At last the reason has been found on the OS vendor’s side and described in MOS document PRVF-5637 : DNS response time could not be checked on following nodes [ID 1480242.1] – in RHEL/OEL 6.3 the command nslookup returns exit code “1” instead of “0” in case of failure. Thus the issue has been successfully workaround by the following trick (as root on every node)

# mv /usr/bin/nslookup /usr/bin/nslookup.orig
# echo '#!/bin/bash
> /usr/bin/nslookup.orig $*
> exit 0' > /usr/bin/nslookup
# chmod a+x /usr/bin/nslookup

The last question is: according to POSIX a command can return 0 in case of success and 1 to 255 in case of failure, so OS vendors did a right thing. So why this small move to expected behavior have broken the installer?

Tagged with:
Posted in Oracle

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Oracle ... as usual

Oracle by Laurent Leturgez

Carlos Sierra's Tools and Tips

Tools and Tips for Oracle Performance and SQL Tuning


Just another oracle developer

Coskan's Approach to Oracle

What I learned about Oracle

Oracle Scratchpad

Just another Oracle weblog

Oleksandr Denysenko's Blog

be prepared for The Future...

%d bloggers like this: