-
Version2.4.40 Installation MethodSecurity Onion ISO image Descriptionother (please provide detail below) Installation TypeDistributed Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU8 RAM135GB Storage for /135G Storage for /nsm8TB Network Traffic Collectionspan port Network Traffic SpeedsLess than 1Gbps StatusNo, one or more services are failed (please provide detail below) Salt StatusYes, there are salt failures (please provide detail below) LogsYes, there are additional clues in /opt/so/log/ (please provide detail below) DetailI have a new install that I then had to do a lot of work on to get RAID setup for nsm. Now I am getting faults due to elastic search on the manager and search nodes. Manger shows Elasticsearch Status: Fault and I see shard failure logs. Search node says the elasticsearch and logstash containers are missing. Process status shows fault and Elasticsearch shows as unknown. On the search node. I see the following in the docker logs: I'm a novice to this and trying to figure out how to troubleshoot the issue. Any help appreciated. Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
I tried restarting the logstash and elasticsearch containers. Both exit with code 1. In the logstash container logs I see the following: |
Beta Was this translation helpful? Give feedback.
-
I fixed part of the issue. When I moved /nsm on the search node, I don't think I preserved file permissions. I modified /nsm/elasticsearch and /nsm/logstash and then the containers started and stay started. Search node looks green in the soc Grid screen now. Manager still shows elasticsearch fault though so I wonder there are still permission issues I need to fix. |
Beta Was this translation helpful? Give feedback.
-
Clicking alert, dashboard, or hunt in the SOC gives me the following style error. The search query encountered a failure within the Elasticsearch cluster. Check SOC logs for details. I see these in the sensaroni log: {"fields":{"host":"sosearch01","processStatus":{"soman01":"red"}},"level":"warn","timestamp":"2024-02-06T21:54:25.198816743Z","message":"Host not found in process status metrics"} {"fields":{"reason":"N/A","reasonType":"no_shard_available_action_exception"},"level":"warn","timestamp":"2024-02-06T21:32:39.741908409Z","message":"Shard failure"} {"fields":{"error":"ERROR_QUERY_FAILED_ELASTICSEARCH", ... ,"level":"warn","timestamp":"2024-02-06T21:32:39.74206283Z","message":"Request did not complete successfully"} |
Beta Was this translation helpful? Give feedback.
-
I ended up rebuilding the servers. this time made sure to use cp -a when moving the /nsm files around. Things are all green now. |
Beta Was this translation helpful? Give feedback.
I ended up rebuilding the servers. this time made sure to use cp -a when moving the /nsm files around. Things are all green now.