Distributed Environment - Joining New Manager

[NeoLife-iT]

Version

2.4.150

Installation Method

Security Onion ISO image

Description

upgrading

Installation Type

Distributed

Location

on-prem with Internet access

Hardware Specs

Exceeds minimum requirements

CPU

8

RAM

256

Storage for /

512

Storage for /nsm

4TB

Network Traffic Collection

other (please provide detail below)

Network Traffic Speeds

more than 10Gbps

Status

No, one or more services are failed (please provide detail below)

Salt Status

Yes, there are salt failures (please provide detail below)

Logs

No, there are no additional clues

Detail

I am in the rescue mode:

After Upgrade to 4.150 version - so-dockerregistry - missing error. I had tried salt-call state.apply registry and so-docker refresh several time still failed. Any tips on fix this issue would be great! Thanks in advance

2nd Option work in progress: Start from blank page
-I had created new Manager and looking for way for other nodes to join the new manager if this is possible? the finger print are different with new manager.
-Is it possible for the client on the network to join new manager?
-Proper way to moving the Data from old LV /nsm/nsm to new manager -

Thanks for all your help

Guidelines

• I have read the discussion guidelines at Read before posting! #1720 and assert that I have followed the guidelines.

[dougburks]

After Upgrade to 4.150 version - so-dockerregistry - missing error.

Do you have full Internet access?

Are there any firewalls, proxies, or other network devices that could be interfering with the network traffic?

I had tried salt-call state.apply registry and so-docker refresh several time still failed.

Do these commands output any errors?

[NeoLife-iT]

Hi Doug,

I rebuild the whole cluster from ground up - All working now

Thanks for reply