-
Notifications
You must be signed in to change notification settings - Fork 159
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationknown-issuerelease-notes
Description
Description
We need to create a known issue for elastic/elastic-agent#8245 in https://github.com/elastic/docs-content/tree/main/release-notes/fleet-elastic-agent.
Resources
The output of the elastic-agent
status command shows an error similar to the one below:
units:
input-osquery-default-4b464ff8-e88a-47df-a99f-b98615bde173:
message: 'Failed: pid ''95375'' exited with code ''1'''
state: 4
This happens because the osquery.app/
directory is unconditionally stripped at installation time because of an omission directing agent to preserve this file on MacOS.
Starting contents of the components/ directory showing that the osquery.app directory exists:
❯ ls ~/Downloads/builds/elastic-agent-9.1.0-SNAPSHOT-darwin-aarch64/data/elastic-agent-ea8a07/components
LICENSE.txt checksum.yml fleet-server.spec.yml
NOTICE.txt endpoint-security lenses
agentbeat endpoint-security-resources.zip module
agentbeat.spec.yml endpoint-security.spec.yml osquery-extension.ext
certs fleet-server osquery.app
Install the agent in development mode:
❯ sudo ./elastic-agent install --develop -f
Installing into development namespace; this is an experimental and currently unsupported feature.
[== ] Service Started [4s] Elastic Agent - Development successfully installed, starting enrollment.
[== ] Done [4s]
Elastic Agent - Development has been successfully installed.
Resulting installed agent is missing the osquery.app directory:
❯ sudo ls /Library/Elastic/Agent-Development/data/elastic-agent-9.1.0-SNAPSHOT-ea8a07/components/
agentbeat endpoint-security lenses
agentbeat.spec.yml endpoint-security-resources.zip module
certs endpoint-security.spec.yml osquery-extension.ext
Which documentation set does this change impact?
Elastic On-Prem only
Feature differences
N/A
What release is this request related to?
9.0
Serverless release
N/A
Collaboration model
The documentation team
Point of contact.
Main contact: @cmacknz
Stakeholders: @alexandra5000
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationknown-issuerelease-notes