# Fleet Server Unhealthy when first Launched

**URL:** <https://discuss.elastic.co/t/fleet-server-unhealthy-when-first-launched/361850>\
**Category:** Elastic Agent\
**Tags:** fleet\
**Created:** [June 21, 2024, 12:29pm UTC](https://discuss.elastic.co/t/fleet-server-unhealthy-when-first-launched/361850 "2024-06-21T12:29:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mid\_city](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@mid\_city](https://discuss.elastic.co/u/mid_city)\
**Post date:** [June 21, 2024, 12:29pm UTC](https://discuss.elastic.co/t/fleet-server-unhealthy-when-first-launched/361850/1 "2024-06-21T12:29:08Z")

</div>

Whenever I launch a fleet server it has a status of unhealthy. The system integration had warnings and I found the following when looking through my log diagnostic.

```auto
{"log.level":"error","@timestamp":"2024-06-21T11:10:06.244Z","log.origin":{"file.name":"coordinator/coordinator.go","file.line":606},"message":"Component state changed log-default (STARTING->FAILED): Failed: pid '14021' exited with code '-1'","log":{"source":"elastic-agent"},"component":{"id":"log-default","state":"FAILED","old_state":"STARTING"},"ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2024-06-21T11:10:06.244Z","log.origin":{"file.name":"coordinator/coordinator.go","file.line":624},"message":"Unit state changed log-default-logfile-system-eeccd981-c02e-4c16-bc16-b50b6e4b1271 (STARTING->FAILED): Failed: pid '14021' exited with code '-1'","log":{"source":"elastic-agent"},"component":{"id":"log-default","state":"FAILED"},"unit":{"id":"log-default-logfile-system-eeccd981-c02e-4c16-bc16-b50b6e4b1271","type":"input","state":"FAILED","old_state":"STARTING"},"ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2024-06-21T11:10:06.244Z","log.origin":{"file.name":"coordinator/coordinator.go","file.line":624},"message":"Unit state changed log-default (STARTING->FAILED): Failed: pid '14021' exited with code '-1'","log":{"source":"elastic-agent"},"component":{"id":"log-default","state":"FAILED"},"unit":{"id":"log-default","type":"output","state":"FAILED","old_state":"STARTING"},"ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2024-06-21T11:10:06.710Z","log.origin":{"file.name":"coordinator/coordinator.go","file.line":606},"message":"Component state changed system/metrics-default (FAILED->STARTING): Starting: spawned pid '14022'","log":{"source":"elastic-agent"},"component":{"id":"system/metrics-default","state":"STARTING","old_state":"FAILED"},"ecs.version":"1.6.0"}

```

---

<div class="post-metadata">

**Author:** ![Julia\_Bardi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julia_bardi/32/79463_2.png) [@Julia\_Bardi](https://discuss.elastic.co/u/Julia_Bardi)\
**Post date:** [July 9, 2024, 7:40am UTC](https://discuss.elastic.co/t/fleet-server-unhealthy-when-first-launched/361850/2 "2024-07-09T07:40:40Z")

</div>

Hi mid\_city,

Is there anything else in the logs which could help determine the root cause?  
What is the command you are using to enroll fleet-server?