SAS GRID Controller is failed and nodes are not taking control

MG18 — Tue, 15 Nov 2022 08:51:51 GMT

Hi team ,

The Grid Control Server(26) is failed due to a physical hardware/Network/Power failure . The rest of installation is available ( including the shared file system ) are up and running.

The common answer is the other nodes would take over. But in our case when are trying to make node as controller it is not becoming .

LSF services on nodes are running fine but when we tried to login as egosh services ,it is failing with below error.

Error:-

[sasinst@lxxxxt27 ~]$ egosh user logon -u Admin -x Admin

Cannot contact the master host. If you cannot start the cluster

successfully, refer to VEMKD and LIM log files for troubleshooting

information

I have started the lsadmin and bsadmin services on 27 28 29 (rest of the node ) and then tried to login to egosh services but it is giving above error .

Re: SAS GRID Controller is failed and nodes are not taking control

doug_sas — Tue, 15 Nov 2022 12:46:57 GMT

The lsf.conf file and the ego.conf file have parameters for the list of master hosts (LSF_MASTER_LIST & EGO_MASTER_LIST). The value of these variables is a space separated list of host names in order of priority.

If the dead master machine is the only host listed by these variables, LSF does not know what to do.

For example, if you have EGO_MASTER_LIST="myhost1.mydomain.com" then when myhost1 goes down, LSF does not know who to make the master. If, on the other hand, EGO_MASTER_LIST="myhost1.mydomain.com myhost2.mydomain.com", when myhost1 goes down, myhost2 becomes the master.

topic SAS GRID Controller is failed and nodes are not taking control in Administration and Deployment

SAS GRID Controller is failed and nodes are not taking control

Re: SAS GRID Controller is failed and nodes are not taking control