XenServer 8.2 restart automatic after enabling HA

[Hakim Hinglawala]

XenServer 8.2 restart automatic  after enabling HA. Getting mentioned error: -

 

\var\log\xha.log

Feb 27 13:19:12 IST 2021 [warn] SC: (script_service_do_query_liveset) reporting "heartbeat approaching timeout". host[8].time_since_last_hb=81335.
Feb 27 13:19:12 IST 2021 [warn] SC: (script_service_do_query_liveset) reporting "State-File approaching timeout". host[8].time_since_last_update_on_sf=79225.

 

\var\log\kern.log

Feb 27 08:30:09 falmumxen01 kernel: [ 4295.392220] qla2xxx [0000:04:00.0]-8009:1: DEVICE RESET ISSUED nexus=1:0:32 cmd=000000000ac48073.
Feb 27 08:30:09 falmumxen01 kernel: [ 4295.450297] qla2xxx [0000:04:00.0]-800e:1: DEVICE RESET SUCCEEDED nexus:1:0:32 cmd=000000000ac48073.

 

Anyone face this issue or any resolution for this?

[Tobias Kreidl]

Is NTP properly set up and synchronized on all your hosts? You can check the time offsets from the CLI with "ntpstat -s" which should be done on each host. Also, check to make sure you can connect to and communicate with your HA storage device.

 

-=Tobias

[Alan Lantz]

Yes, NTP sync is important, having 3 hosts minimum in the pool is important, and all hosts being able to access 

to your SR that holds your HA files is important.

 

--Alan--

 

[Hakim Hinglawala]

On 2/27/2021 at 8:16 PM, Tobias Kreidl said:

Is NTP properly set up and synchronized on all your hosts? You can check the time offsets from the CLI with "ntpstat -s" which should be done on each host. Also, check to make sure you can connect to and communicate with your HA storage device.

 

-=Tobias

 

 

[Hakim Hinglawala]

I have already checked the NTP on all the host & its working fine but still facing issue.

[Tobias Kreidl]

The hosts can be manually booted up though, correct, it's the HA that's not working? Have you tried turning HA off and reconfiguring it?

[Hakim Hinglawala]

Yes.. I have reconfigured the HA but still same issue. After 20min host restarting automatic.

[Tobias Kreidl]

You'll have to look at the logs to see what causes this. Hard to guess off-hand.

 

-=Tobias

[Hakim Hinglawala]

I have already checked the logs & getting error message: - 

 

var\log\xha.log

Feb 27 13:19:12 IST 2021 [warn] SC: (script_service_do_query_liveset) reporting "heartbeat approaching timeout". host[8].time_since_last_hb=81335.
Feb 27 13:19:12 IST 2021 [warn] SC: (script_service_do_query_liveset) reporting "State-File approaching timeout". host[8].time_since_last_update_on_sf=79225.

 

\var\log\kern.log

Feb 27 08:30:09 falmumxen01 kernel: [ 4295.392220] qla2xxx [0000:04:00.0]-8009:1: DEVICE RESET ISSUED nexus=1:0:32 cmd=000000000ac48073.
Feb 27 08:30:09 falmumxen01 kernel: [ 4295.450297] qla2xxx [0000:04:00.0]-800e:1: DEVICE RESET SUCCEEDED nexus:1:0:32 cmd=000000000ac48073.

[Tobias Kreidl]

I'd try to delete and reconfigure the heartbeat setting and see if that makes a difference. The timeout would indicate the host cannot communicate with the heartbeat device.