Fleet server does not get installed after a so-elastic-fleet-reset #15001
-
Version2.4.170 Installation MethodSecurity Onion ISO image Descriptionother (please provide detail below) Installation TypeDistributed Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU8 RAM16G Storage for /64G Storage for /nsm128G Network Traffic Collectionother (please provide detail below) Network Traffic Speeds1Gbps to 10Gbps StatusNo, one or more services are failed (please provide detail below) Salt StatusNo, there are no failures LogsNo, there are no additional clues DetailWe have the following nodes: When doing a fresh ISO install of the fleet node, everything works perfect, but after a so-elastic-fleet-reset on the manager node, the dedicated fleet server is not being installed as a fleet server. There is no new fleet-server policy being created for the dedicated fleet server. Agents on all nodes and the fleet server on the manager node is working fine after the so-elastic-fleet-reset. Do i have to make a clean ISO installation of the dedicated fleet node again? Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I just updated the wording on the reset script: #15003 "Only the Elastic Fleet instance on the Manager will be reinstalled - dedicated Fleet node config will removed and will need to be reinstalled." |
Beta Was this translation helpful? Give feedback.
I just updated the wording on the reset script: #15003
"Only the Elastic Fleet instance on the Manager will be reinstalled - dedicated Fleet node config will removed and will need to be reinstalled."