Elastic Fleet in an inconsistent state #12172
Replies: 1 comment 1 reply
-
On your manager what does |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Version
2.4.30
Installation Method
Security Onion ISO image
Description
other (please provide detail below)
Installation Type
Distributed
Location
on-prem with Internet access
Hardware Specs
Exceeds minimum requirements
CPU
32
RAM
144GB
Storage for /
200GB
Storage for /nsm
5TB
Network Traffic Collection
span port
Network Traffic Speeds
1Gbps to 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 recently reinstalled SO to move to 2.4 as we had been happily running 2.3 for a few years. I used the ISO and everything seemed to install cleanly. I installed the manager/search node first and then a sensor node. I am seeing alerts from the playbooks fine but I was getting nothing from the Sensor (Metadata or Suricata). I followed the troubleshooting guide and wasn't able to resolve the issue. I tried restarting the service on the manager and it says it isn't started. When I try to start it, it says that it is already started:
The log files in /opt/so/log/elasticfleet are empty. I am not sure what to do next to get things working. Thanks!
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions