Exachk Execution Reports Some Skipped Checks

Asset ID:	1-72-1632249.1
Update Date:	2014-04-15
Keywords:

Solution Type Problem Resolution Sure

Solution 1632249.1 : Exachk Execution Reports Some Skipped Checks

Applies to:

Exadata Database Machine X2-2 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Exachk may skip some checks Infiniband Switch (can also be other checks)

Examples:

skipping Infiniband switch HOSTNAME configuration (checkid:- 9AD56124DDFE9FCCE040E50A1EC038A6) on dm01sw-ib3 because s_sysconfig_network_dm01sw-ib3.out not found
skipping Infiniband switch HOSTNAME configuration (checkid:- 9AD56124DDFE9FCCE040E50A1EC038A6) on dm01sw-ib2 because s_sysconfig_network_dm01sw-ib2.out not found
skipping Infiniband switch HOSTNAME configuration (checkid:- 9AD56124DDFE9FCCE040E50A1EC038A6) on dm01sw-ib3 because s_sysconfig_network_dm01sw-ib3.out not found
skipping Infiniband switch HOSTNAME configuration (checkid:- 9AD56124DDFE9FCCE040E50A1EC038A6) on dm01sw-ib2 because s_sysconfig_network_dm01sw-ib2.out not found
skipping Infiniband Switch NTP configuration (checkid:- 9AD59DE0898D0513E040E50A1EC03EEA) on dm01sw-ib3 because s_ntp_dm01sw-ib3.out not found
skipping Infiniband Switch NTP configuration (checkid:- 9AD59DE0898D0513E040E50A1EC03EEA) on dm01sw-ib2 because s_ntp_dm01sw-ib2.out not found
skipping Infiniband Switch NTP configuration (checkid:- 9AD59DE0898D0513E040E50A1EC03EEA) on dm01sw-ib3 because s_ntp_dm01sw-ib3.out not found
skipping Infiniband Switch NTP configuration (checkid:- 9AD59DE0898D0513E040E50A1EC03EEA) on dm01sw-ib2 because s_ntp_dm01sw-ib2.out not found
skipping Infiniband switch routing_engine configuration (checkid:- 9AD8F72CFE0AC95BE040E50A1EC050D0) on dm01sw-ib3 because s_opensm_dm01sw-ib3.out not found
skipping Infiniband switch routing_engine configuration (checkid:- 9AD8F72CFE0AC95BE040E50A1EC050D0) on dm01sw-ib2 because s_opensm_dm01sw-ib2.out not found
skipping Infiniband switch routing_engine configuration (checkid:- 9AD8F72CFE0AC95BE040E50A1EC050D0) on dm01sw-ib3 because s_opensm_dm01sw-ib3.out not found
skipping Infiniband switch routing_engine configuration (checkid:- 9AD8F72CFE0AC95BE040E50A1EC050D0) on dm01sw-ib2 because s_opensm_dm01sw-ib2.out not found
skipping Infiniband switch log_flags configuration (checkid:- 9ADA623709086DC5E040E50A1EC0168D) on dm01sw-ib3 because s_opensm_dm01sw-ib3.out not found
skipping Infiniband switch log_flags configuration (checkid:- 9ADA623709086DC5E040E50A1EC0168D) on dm01sw-ib2 because s_opensm_dm01sw-ib2.out not found
skipping Infiniband switch log_flags configuration (checkid:- 9ADA623709086DC5E040E50A1EC0168D) on dm01sw-ib3 because s_opensm_dm01sw-ib3.out not found
skipping Infiniband switch log_flags configuration (checkid:- 9ADA623709086DC5E040E50A1EC0168D) on dm01sw-ib2 because s_opensm_dm01sw-ib2.out not found
skipping Infiniband switch controlled_handover configuration (checkid:- 9ADAAD73FF532FE4E040E50A1EC0284E) on dm01sw-ib3 because s_opensm_dm01sw-ib3.out not found
skipping Infiniband switch controlled_handover configuration (checkid:- 9ADAAD73FF532FE4E040E50A1EC0284E) on dm01sw-ib2 because s_opensm_dm01sw-ib2.out not found
skipping Infiniband switch controlled_handover configuration (checkid:- 9ADAAD73FF532FE4E040E50A1EC0284E) on dm01sw-ib3 because s_opensm_dm01sw-ib3.out not found
skipping Infiniband switch controlled_handover configuration (checkid:- 9ADAAD73FF532FE4E040E50A1EC0284E) on dm01sw-ib2 because s_opensm_dm01sw-ib2.out not found

Cause

The issue with the skipped checks on the IB switches was due to the old left-over files from the IB switches IB2 and IB3 /tmp location.

* dm01sw-ib2:

[root@dm01sw-ib2 ~]# ls -la /tmp | grep exac
-rw-r--r-- 1 nm2user nm2user 228 Feb 21 10:54 .exachk

[root@dm01sw-ib2 ~]# cat /tmp/.exachk
dm01sw-ib3.datacenter.local||dm01sw-ib3.datacenter.local
dm01sw-ib2.datacenter.local||dm01sw-ib2.datacenter.local
dm01sw-ib3.datacenter.local||dm01sw-ib3.datacenter.local
dm01sw-ib2.datacenter.local||dm01sw-ib2.datacenter.local

* dm01sw-ib3:

[root@dm01sw-ib3 ~]# ls -la /tmp | grep exac
-rw-r--r-- 1 nm2user nm2user 228 Feb 21 10:54 .exachk

[root@dm01sw-ib3 ~]# cat /tmp/.exachk
dm01sw-ib3.datacenter.local||dm01sw-ib3.datacenter.local
dm01sw-ib2.datacenter.local||dm01sw-ib2.datacenter.local
dm01sw-ib3.datacenter.local||dm01sw-ib3.datacenter.local
dm01sw-ib2.datacenter.local||dm01sw-ib2.datacenter.local

Solution

A) As the root userid, remove the standard file /tmp/.exachk from the IB switches.

B) retry a standard run of the exachk.

1) as the oracle userid on node 1 ,make a clean directory and load
2.2.4(BETA)_20140210 into it, for example
/home/oracle/exachk/bug_18293524_224BETA_debug-2.
2)cd to the directory created in 1)
3) bash -x exachk
During the run,
answer the prompt to set crs home as "Y".
select all databases
answer the prompts for the root password on the storage servers
answer the prompts for the root password on the storage servers
answer the prompts for the nm2user password on the IB switches
4) enter "exit" after the run completes to stop screen capture

References

<BUG:18293524> - EXACHK EXECUTION REPORTS SOME SKIPPED CHECKS
<BUG:18329202> - BAD MAGIC NUMBER IN SUPER-BLOCK WHILE TRYING TO OPEN

Attachments

This solution has no attachment