Solved

Fail-fast after detecting hung stargate ops

  • 5 January 2016
  • 4 replies
  • 1503 views
F
Userlevel 3
Badge +19
Hello,

I am facing issue in Health page in Prism showing "Nutanix Web Console
CVM to Host Connectivity" after initial diag I found that CVM cannot ping 192.168.5.1 interface of host but host can ping CVM interfaces.Going through another forum entry, it might caused if stargate is crashed, while cluster status shows Stargate is running, I found a FATAL error "F0104 10:09:45.332298 27391 stargate.cc:1362] Fail-fast after detecting hung stargate ops: Operation with id 30 hung for 60secs"I referred to INFO logs but get the same error there. Any ideas how to get it resolved. RegardsvF.P
icon

Best answer by farhanparkar 5 January 2016, 11:00

Issue resolved, I am suspecting switch issue which caused CVm to loose connectivity and failover storage path.

genesis restart failback the storage path.



Thanks for wonderful support as usual.



vF.P
View original
This topic has been closed for comments

4 replies

DonnieBrasco
Rank
Userlevel 4
Badge +18
Hi Farhan

I see that a case is opened with us. We have one of our SRE's working with you to help fix this issue.
F
Userlevel 3
Badge +19
Issue resolved, I am suspecting switch issue which caused CVm to loose connectivity and failover storage path.
genesis restart failback the storage path.

Thanks for wonderful support as usual.

vF.P
R
Badge +6
We seem to be having the same problem where the host can ping the CVM on 192.168.5.2 but the CVM can not ping the host on 192.168.5.1

This maybe what is leading to the stargate fatal error

F0725 02:38:44.585690 15262 stargate.cc:1323] Watch dog fired: stuck during initialization

What was the solution? Presumably the physical switch is not involved since this comunication is only between the CVM and the host.
A

Hi, Which switch was having problem? physical or virtual inside Nutanix?