Symptom
Failover from node A to node B is not working with following error messages.
From nameserver trace file,
[62444]{-1}[-1/-1] 2019-02-02 11:54:14.896238 i failover TREXNameServer.cpp(06581) : failover from host node A to current host started
...
[61911]{-1}[-1/-1] 2019-02-02 11:54:52.207501 f ha_fcClientLVM fcClientLVM.py(00400) : mount failed after multiple retries
[61911]{-1}[-1/-1] 2019-02-02 11:54:52.207668 e ha_provider PythonProxyImpl.cpp(00524) : hdb_ha.fcClientLVM/fcClientLVM:attach() failed with python error: mount failed after multiple retries
fcClientLVM.py(401): raise Exception("mount failed after multiple retries")
[62444]{-1}[-1/-1] 2019-02-02 11:54:52.210760 f NameServer TREXNameServer.cpp(04069) : unable to connect storage devices -> stopping instance ...
[62444]{-1}[-1/-1] 2019-02-02 11:54:52.212105 f NameServer TREXNameServer.cpp(04083) : stopping topology thread
[62444]{-1}[-1/-1] 2019-02-02 11:54:52.212118 f NameServer TREXNameServer.cpp(04085) : got shutdown scope
[62444]{-1}[-1/-1] 2019-02-02 11:54:52.212121 f NameServer TREXNameServer.cpp(04089) : stopped topology thread
[62444]{-1}[-1/-1] 2019-02-02 11:54:52.212128 e Basis TREXNameServer.cpp(04099) : Process exited due to an error via explicit exit call with exit code 1 , no crash dump will be written
Read more...
Environment
-
HANA 1.0
-
HANA 2.0
Product
Keywords
"failover", "failed failover", "mount","hardware","mount failed" , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview