DataCollector is unable to collect information
Article ID: 100028316
Updated On:
Cause
nslookup command changes the exit value from 0 to 1 when the command can't resolve hostname.
DataCollecter was not able to handle the exit value changes.
Resolution
DataCollecter fixed to handle the behavior changes from version 3.8.1.20130226.
You can check the version with the following command:
# ./sortdc -version
===========================================================================
| Checking available driver (apg-sol16) resources
===========================================================================
Working directory file system type: ufs
Open files limit: 256
Virtual memory limit: unlimited (KB)
Free swap: 2048 (MB)
Loading Data Collector...
3.8.1.20130226
#
If you want to download the latest DataCollector manually, please refer the following file:
/opt/VRTSspt/DataCollector/README.data_collector
- Use Legacy VRTSexplorer
- Build DNS server which can resolve the hostname and configure /etc/resolv.conf (if possible)
- Use "/opt/VRTSspt/Data Collector/sort/offlinedc.sh" script
- Specify multiple hosts as arguments if the customer has installed/configured Veritas Cluster Server.
./sortdc -vxexplorer node1 node2
Applies To
- On Linux Platform, Redhat Enterprise Linux 6.3 or later
- On Solaris Platform, the patch 119783-25 (or equivalent patch) for BIND package is installed
On the both environment, if the host which is specifying in "/etc/resolv.conf" is not existed (or "/etc/resolv.conf" itself is not existed in the host), nslookup command can not resolve the localhost name, and the exit code returns non zero value
# nslookup `hostname`
;; connection timed out; no servers could be reached
# echo $?
1
Issue/Introduction
