Skip to content

Fleet Server is not installing (starting) correctly, stuck in crash loop (confirmed on LInux and macOS) #245

@EricDavisX

Description

@EricDavisX

Testing on latest 8.0 versions of Cloud + Agent on: Centos7

https://artifacts-api.elastic.co/v1/versions/8.0-SNAPSHOT/builds/8.0.0-12de385c

[root@mainqa-atlcolo-10-0-7-165 elastic-agent-8.0.0-SNAPSHOT-linux-x86_64]# elastic-agent version
Binary: 8.0.0-SNAPSHOT (build: fb1eb8d812002c28dd0478eb636b792d8b1abea2 at 2021-04-15 09:08:32 +0000 UTC)
Daemon: 8.0.0-SNAPSHOT (build: fb1eb8d812002c28dd0478eb636b792d8b1abea2 at 2021-04-15 09:08:32 +0000 UTC)

  • Steps to Reproduce:
    copy the linux.tar.gz file to the host
    tar -xvf elastic-agent*
    cd elastic-agent*
    sudo ./elastic-agent install -f --fleet-server-es=

to get more insight, since no logs were generated that helped, we decided to install the Agent in standaloene mode:
sudo ./elastic-agent install

then enroll it...
elastic-agent enroll --fleet-server-es=https://elastic:1234abcd@snap-thursday.es.us-central1.gcp.foundit.no:9243

logs:
[root@mainqa-atlcolo-10-0-7-165 elastic-agent-8.0.0-SNAPSHOT-linux-x86_64]# elastic-agent enroll --fleet-server-es=https://elastic:vhUWxIGb0zRUWRoK275jwSJg@snap-thursday.es.us-central1.gcp.foundit.no:9243
The Elastic Agent is currently in BETA and should not be used in production

This will replace your current settings. Do you want to continue? [Y/n]:y
2021-04-15T13:55:32.285-0400 INFO cmd/enroll_cmd.go:291 Generating self-signed certificate for Fleet Server
2021-04-15T13:55:34.787-0400 INFO cmd/enroll_cmd.go:622 Fleet Server - Starting
2021-04-15T13:57:32.152-0400 INFO cmd/enroll_cmd.go:622 Fleet Server - Restarting
Error: fleet-server never started by elastic-agent daemon: context canceled

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions