

�[38 5 6m �[38 5 5m00:43:16.70 �[0m�[38 5 2mINFO �[0m => about to run the command: redis-cli -h .local -p 26379 sentinel get-master-addr-by-name backend-redis redis-backend-node-0 redisĬould not connect to Redis at .local:26379: Connection refused redis-backend-node-0 redis �[38 5 6m �[38 5 5m00:41:06.32 �[0m�[38 5 2mINFO �[0m => about to run the command: redis-cli -h .local -p 26379 sentinel master backend-redis redis-backend-node-0 redisĬould not connect to Redis at .local:26379: Connection timed out redis-backend-node-0 redis


BITNAMI MEAN NODE APP FOREVER MANUAL
This bug only occurs when the cluster is already broken (= no elected master) and it can only recover with manual interaction (=deleting all Pods). Liveness probe will kill the rest and the cluster will stay in endless crash loop forevery (until all Pods are deleted).ĬontainerSecurit圜ontext: &containerSecurit圜ontextĬontainerSecurit圜ontext: *containerSecurit圜ontext master election failed) new nodes will not come up again and will be fully broken. If [[ -z "$(getent ahosts "$HEADLESS_SERVICE" | grep -v "^$
