"Failed to update heartbeat for Repository" error for Rim node and Rim node missing from ServerNodeHeartbeats table

[montanablue2]

I am getting recurring "Failed to update heartbeat for Repository" errors in Repository System trace logs. I have followed the procedures for deleting and reissuing certs. Even uninstalled and reinstalled Qlik Sense on the rim node in tandem with cert delete and reissue.  

Still get same error along with seeing message in QMC for Rim node that "4 of 5 services are stopped".

I investigated the ServerNodeHeartbeats table in QSR and I see that the entry for the Rim node is missing the table. I suspect that is the issue.

Question is how would I force Qlik or manually update the table to add the Rim node entry to the ServerNodeHeartbeats table? This is a new installation of Qlik Sense May 2021

[montanablue2]

I am also seeing a previous issue with ServerNodeHeartbeats table in Qlik 2020 that gives similar errors

Issues within the environment with many errors of "failed to update heartbeat"
Jira issue ID: QB-32
Description: In case "ModifiedDate" value for any of the rim nodes from "ServerNodeHeartbeats" table
got corrupt, Qlik Sense Repository service would end up in a loop trying to correct it but continuously
failing to do so, because the value in the database was always newer than the one stored in QSR's
memory. This would result in "Failed to update heartbeat for Repository service status on node
<node_name>" errors in the logs and QMC showing services as offline.

[Ranganath_DR · Accepted solution]

Hi @montanablue2 ,

Qlik Sense May 2021 is not supported, upgrade to supported versions

https://community.qlik.com/t5/Product-Lifecycle/Qlik-Sense-Enterprise-on-Windows-Product-Lifecycle/t...

and if RIM node registration was successful check following article and add Keep Alive setting. 

https://community.qlik.com/t5/Product-Lifecycle/Qlik-Sense-Enterprise-on-Windows-Product-Lifecycle/t...