Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
ldubin
Contributor II
Contributor II

Failover between nodes fails with forbidden error

We are in the process of replatforming our Qlik Sense environment and I was able to change the central node to a new server (via CLI). However when I attempt to move it again to another node now I gett the following error in the logs:


282 20231026T123500.899-0400 ERROR CENTRAL System.Repository.Repository.Core.Failover.FailoverWorker 50 fb0fef56-7a00-4573-bb14-01d289656e3d USER Failed to get ServerNodeConfiguration with ID c7bc042a-3d86-4c50-aa61-eae799b47594 as from node for FailoverWorker Forbidden at Repository.Core.Repository.Common.ModelRepository`1.ExecuteGet(Guid id, Boolean appendPrivileges, Int64 privilegesFilter)↵↓ at Repository.Core.Repository.Common.ModelRepository`1.Get(Guid id, Boolean appendPrivileges, Int64 privilegesFilter)↵↓ at Repository.Core.Failover.FailoverWorker.<>c__DisplayClass9_0.<TryGetServerNodes>b__1(IModelRepository`1 serverNodeRepsitory) fb0fef56-7a00-4573-bb14-01d289656e3d


283 20231026T123500.899-0400 ERROR CENTRAL System.Repository.Repository.Core.Failover.FailoverWorker 50 35c35313-985f-4ecb-b933-624d38667dab USER Failed to get both from-node and to-node. Unable to perform failover. 35c35313-985f-4ecb-b933-624d38667dab

The 3 nodes are all set as failover candidates. What am I missing? 

Labels (1)
1 Solution

Accepted Solutions
3 Replies
Alan_Slaughter
Support
Support

Hi Luke, what articles did you follow? What version of Qlik Sense? How many nodes do you have?

Alan_Slaughter
Support
Support

ldubin
Contributor II
Contributor II
Author

Going to be honest I forgot about this but I believe the issue ended up being an issue with the local cluster internal certs so the C:\Program Files\Qlik\Sense\Repository\Repository.exe" -bootstrap -iscentral -restorehostname command ended up fixing it.