8000 [Filebeat] Initial errors/failures observed when testing AbuseCH integration in Agentless · Issue #42815 · elastic/beats · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
[Filebeat] Initial errors/failures observed when testing AbuseCH integration in Agentless #42815
Closed
@qcorporation

Description

@qcorporation

Please include configurations and logs if available.
elastic-agent-diagnostics-2025-02-20T20-36-47Z-00.zip

For confirmed bugs, please report:

Version:

9.0.0-beta1

Operating System:

Agentless Deployment

Steps to Reproduce:

  1. Instantiate a cloud security elastic stack instance on staging against v9.0.0
  2. Install a modified ti_abusech integration with agentless enabled using elastic-package to the instance
  3. Create/Install an AbuseCH integration in Agentless
  4. After a few minutes when logs have been ingested, capture an agent diagnostic
  5. note errors within agent logs
{"log.level":"error","@timestamp":"2025-02-20T20:05:47.646Z","message":"fatal error: concurrent map read and map write","component":{"binary":"filebeat","dataset":"elastic_agent.filebeat","id":"cel-default","type":"cel"},"log":{"source":"cel-default"},"ecs.version":"1.6.0"}

Running it through the agent analyzer synposis looks like this:

2025-02-20T20:05:47.68Z: Component state changed cel-default (HEALTHY->FAILED): Failed: pid '68' exited with code '2'
2025-02-20T20:05:47.68Z: Unit state changed cel-default (STARTING->FAILED): Failed: pid '68' exited with code '2'
2025-02-20T20:05:47.68Z: Unit state changed cel-default-cel-ti_abusech-06203ce2-d5cc-43a6-83f6-d43252af6890 (STARTING->FAILED): Failed: pid '68' exited with code '2'
2025-02-20T20:06:44.379Z: Component state changed cel-default (HEALTHY->FAILED): Failed: pid '161' exited with code '2'
2025-02-20T20:06:44.379Z: Unit state changed cel-default-cel-ti_abusech-06203ce2-d5cc-43a6-83f6-d43252af6890 (STARTING->FAILED): Failed: pid '161' exited with code '2'
2025-02-20T20:06:44.379Z: Unit state changed cel-default (STARTING->FAILED): Failed: pid '161' exited with code '2'
2025-02-20T20:07:21.605Z: Component state changed cel-default (HEALTHY->FAILED): Failed: pid '226' exited with code '2'
2025-02-20T20:07:21.605Z: Unit state changed cel-default-cel-ti_abusech-06203ce2-d5cc-43a6-83f6-d43252af6890 (STARTING->FAILED): Failed: pid '226' exited with code '2'
2025-02-20T20:07:21.605Z: Unit state changed cel-default (STARTING->FAILED): Failed: pid '226' exited with code '2'
2025-02-20T20:09:12.822Z: Component state changed cel-default (HEALTHY->FAILED): Failed: pid '417' exited with code '2'
2025-02-20T20:09:12.823Z: Unit state changed cel-default-cel-ti_abusech-06203ce2-d5cc-43a6-83f6-d43252af6890 (STARTING->FAILED): Failed: pid '417' exited with code '2'
2025-02-20T20:09:12.823Z: Unit state changed cel-default (STARTING->FAILED): Failed: pid '417' exited with code '2'
2025-02-20T20:09:57.277Z: Component state changed cel-default (HEALTHY->FAILED): Failed: pid '491' exited with code '2'

and

2025-02-20T20:07:43.807Z: Error fetching data for metricset http.json: error making http request: Get "http://unix/inputs": dial unix /agentless/data/tmp/WDSbrgjXxHKnME7Z0CSyI1xJnirO2oRp.sock: connect: connection refused
2025-02-20T20:10:41.879Z: Error fetching data for metricset http.json: error making http request: Get "http://unix/stats": dial unix /agentless/data/tmp/WDSbrgjXxHKnME7Z0CSyI1xJnirO2oRp.sock: connect: connection refused

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0