Forward node not sending data to Manager Search #12620
-
Version2.4.50 Installation MethodNetwork installation on Debian Descriptionother (please provide detail below) Installation TypeDistributed Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU6 RAM20 Storage for /2 TB Storage for /nsm2 TB Network Traffic Collectiontap Network Traffic Speeds1Gbps to 10Gbps StatusYes, all services on all nodes are running OK Salt StatusNo, there are no failures LogsNo, there are no additional clues DetailI have a distributed setup with two forward nodes, one forward node is at one office by itself. The other forward node is at an office with the manager search node. The one at the other office by itself is sending data from what it is seeing to the manager and it is showing up in the web interface. The forward node that is at the same office as the manager is seeing traffic as well, but it is not forwarding data to the manager and it is not showing up in the web interface. I looked into the logs on the manager to get an idea of what it might be, looked at log-stash, Redis, and then Elasticsearch and nothing unusual there. Got into the forward node in question and looked at the logs there and the Telegraf log showed a problem with one of the scripts, the suriloss.sh was the problem script. I believe this might be pointing towards InfluxDB, I've tested the port connections to the firewall and it was all successful. I've been looking around but don't have a good idea of where else to look, any help is appreciated! Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
On the sensor that is not sending logs, chech the Elastic Agent, |
Beta Was this translation helpful? Give feedback.
That looks to be the fix, it finally got added to Elastic Fleet I know can see the data from the office that I couldn't see to begin with. Thank you @cm-ops for pointing me in the right direction!