Skip to main content
NetApp Knowledge Base

Bare-metal node that was previously decommissioned stuck on StorageGRID expansion

Views:
16
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

  • NetApp StorageGRID
  • NetApp StorageGRID bare-metal based storage node

Issue

A previously decommissioned node that is being re-added is stuck in Expansion.
 
  • bycast-err.log:

Nov  910:24:40 <nodename> chunk[18638]: [must.go:26:] CRITICAL: listen tcp: lookuplocalhost-grid on <ip>: no such host

  • chunk.log:

2023/11/0910:24:40 [net.go:46:] WARNING: Failed DNS lookup for IPs of host"localhost-grid": lookup localhost-grid on <ip>: no suchhost

  • servermanager.log:

2023-11-0915:17:44 +0000 |servermanager            | Failed to get all admin hostnames from dynip: Failed to open TCP connectionto localhost:9400 (Connection refused - connect(2) for "localhost"port 9400)

  • From install.log:

[2023-11-09T10:41:11+00:00INSG] sudo: unable to resolve host <nodename>: Name or service not known

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.