Error Message

2019/05/31 12:00:00 VCS NOTICE V-16-1-11027 VCS engine startup arguments=-restart
2019/05/31 12:00:00 VCS NOTICE V-16-1-11050 VCS engine version=7.3
2019/05/31 12:00:00 VCS NOTICE V-16-1-11054 VCS engine join version=7.3.0.000
2019/05/31 12:00:00 VCS NOTICE V-16-1-11052 VCS engine pstamp=7.3.0.000-2017-04-21-03.29.09
2019/05/31 12:00:00 VCS ERROR V-16-1-16002 sched_setscheduler failed with error(1) for RT class
2019/05/31 12:00:00 VCS NOTICE V-16-1-10114 Opening GAB library
2019/05/31 12:00:00 VCS NOTICE V-16-1-10619 'HAD' starting on: system101
2019/05/31 12:00:00 VCS INFO V-16-1-10118 GAB timeout set to 30000 ms. GAB peak load timeout set to 30000 ms.
2019/05/31 12:00:00 VCS ERROR V-16-1-10116 GabHandle::open failed errno = 2
2019/05/31 12:00:00 VCS ERROR V-16-1-11033 GAB open failed. Exiting

There are many causes for this error code. Below is a list of situations that apply.

1. Veritas packages are corrupted after OS restore
2. Veritas packages are corrupted after patching.
3. Failed to use "-onenode" option in single node cluster.

For Causes 1 and 2:

-Verify Veritas packages on the OS and/or re-install LLT/VXFEN/GAB packages.
-Verify LLT/VXFEN are started before testing GAB.

3. When a single node is configured in VCS cluster, you will need to use "-onenode" option to allow GAB to start up without LLT configured.

Please see the following TN for steps on how to enable hastart with onenode.

https://supportinfoscale.cloud.com/support-home/kbsearch/article?articleNumber=100015174&articleTitle=vcs-one-node-cluster-not-starting-after-upgrade& 

GAB is failing to start after reboot/patching/restore. V-16-1-11033