Agent stuck on updating but still send index

Elastic Stack Elastic Agent
1

I'm just enroll new window fleet everything is fine data received by logstash and stored in our cluster but agent stuck on updating in fleet.
When i get agent status everything is healthy unless fleet-server stuck on re-configuration state.
The output log is notthing weird it only give alot of information like this:

I checked that fleet can reach to epr, artifact....

{"log.level":"info","@timestamp":"2022-11-21T13:34:38.192+0700","log.origin":{"file.name":"operation/operator.go","file.line":180},"message":"Source URI in operator changed to \"https://artifacts.elastic.co/downloads/\"","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:38.195+0700","log.origin":{"file.name":"stateresolver/stateresolver.go","file.line":48},"message":"New State ID is L_vNjgeQ","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:38.195+0700","log.origin":{"file.name":"stateresolver/stateresolver.go","file.line":49},"message":"Converging state requires execution of 3 step(s)","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:38.593+0700","log.origin":{"file.name":"operation/operator.go","file.line":387},"message":"operation 'operation-install' skipped for filebeat.8.5.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:38.593+0700","log.origin":{"file.name":"operation/operator.go","file.line":387},"message":"operation 'operation-start' skipped for filebeat.8.5.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:38.962+0700","log.origin":{"file.name":"operation/operator.go","file.line":387},"message":"operation 'operation-install' skipped for metricbeat.8.5.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:38.962+0700","log.origin":{"file.name":"operation/operator.go","file.line":387},"message":"operation 'operation-start' skipped for metricbeat.8.5.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:39.281+0700","log.origin":{"file.name":"operation/operator.go","file.line":387},"message":"operation 'operation-install' skipped for filebeat.8.5.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:39.281+0700","log.origin":{"file.name":"operation/operator.go","file.line":387},"message":"operation 'operation-start' skipped for filebeat.8.5.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:39.635+0700","log.origin":{"file.name":"operation/operator.go","file.line":387},"message":"operation 'operation-install' skipped for metricbeat.8.5.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:39.635+0700","log.origin":{"file.name":"operation/operator.go","file.line":387},"message":"operation 'operation-start' skipped for metricbeat.8.5.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-11-21T13:34:39.640+0700","log.origin":{"file.name":"stateresolver/stateresolver.go","file.line":66},"message":"Updating internal state","ecs.version":"1.6.0"}

Am i need to do anything to solve this problem?

2

I'm seeing identical symptoms on mine, though I figured maybe it was a bug since I was getting logs with no problems.
The agents themselves on both endpoints (Linux for now) and the Fleet server are reporting as "healthy" when running "elastic-agent status".
Do you have Logstash as an output? I noticed when I'm sending logs directly to elasticsearch cluster, the agents are healthy. It didn't start getting stuck until I decided I wanted the agents to output to Logstash instead.

1 Like
3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.