Troubleshooting Tip: Recover FortiPortal after the cluster is down

Due to some environment migration or maintenance tasks, it may be necessary to turn off the FortiPortal cluster.

When working with a FortiPortal cluster, be aware of some technical considerations, as described in in Limitations with Scalable Cluster - FortiPortal release notes.

Initiating only the primary instance may cause some additional issues which affect the functionality of the cluster:

[fortiportal.utils.redis:redis.py:39 wrapper()] - WARNING - Fail to Execute Redis Query Because of No master found for 'mymaster'.
[fortiportal.utils.redis:redis.py:44 wrapper()] - WARNING - No master found for 'mymaster', will update rediscli and retry
[fortiportal.utils.redis:redis.py:39 wrapper()] - WARNING - Fail to Execute Redis Query Because of No master found for 'mymaster' : Redis<ConnectionPool<Connection<host=redis-local.redis.svc.cluster.local,port=26379,db=0>>> - AuthenticationError('invalid username-password pair or user is disabled.').
[fortiportal.utils.redis:redis.py:44 wrapper()] - WARNING - No master found for 'mymaster' : Redis<ConnectionPool<Connection<host=redis-local.redis.svc.cluster.local,port=26379,db=0>>> - AuthenticationError('invalid username-password pair or user is disabled.'), will update rediscli and retry

After a cluster is fully down, all three nodes need to be brought up at the same time.