Skip to main content
NetApp Knowledge Base

Consul pod not joining ACC cluster anymore

  1. Last updated
  2. Save as PDF
Views:
415
Visibility:
Public
Votes:
0
Category:
astra
Specialty:
snapx
Last Updated:

Applies to

  • Astra Control Center
  • Kubernetes

Issue

Kubernetes node shutdown unexpectedly causing consul pod to timeout

kubectl logs -n netapp-acc polaris-consul-consul-server-1
2024-01-29T08:28:36.783Z [ERROR] agent: startup error: error="refusing to rejoin cluster because server has been offline for more than the configured server_rejoin_age_max (168h0m0s) - consider wiping your data dir"

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.