# Elastic Observability Engineer course - Fleet server not running

**URL:** <https://discuss.elastic.co/t/elastic-observability-engineer-course-fleet-server-not-running/380580>\
**Category:** Elastic Training\
**Created:** [July 30, 2025, 6:25am UTC](https://discuss.elastic.co/t/elastic-observability-engineer-course-fleet-server-not-running/380580 "2025-07-30T06:25:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_Sc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_sc/32/140043_2.png) [@John\_Sc](https://discuss.elastic.co/u/John_Sc)\
**Post date:** [July 30, 2025, 6:25am UTC](https://discuss.elastic.co/t/elastic-observability-engineer-course-fleet-server-not-running/380580/1 "2025-07-30T06:25:32Z")

</div>

Course: Elastic Observability Engineer course  
Version: 8.8.2  
Question: Hello, in lab 2.1 you're required to install an agent. But the already installed fleet server is not running (offline). So Elastic tells me to add one.

Please help me resolving this issue.

Best regards,  
John

---

<div class="post-metadata">

**Author:** ![John\_Sc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_sc/32/140043_2.png) [@John\_Sc](https://discuss.elastic.co/u/John_Sc)\
**Post date:** [July 30, 2025, 7:35am UTC](https://discuss.elastic.co/t/elastic-observability-engineer-course-fleet-server-not-running/380580/2 "2025-07-30T07:35:05Z")

</div>

I tried to check if a fleet proces is already running:

> [@Lab 2.1 - Elastic Agent - Adding Nginx Integration/Agent fail](https://discuss.elastic.co/t/lab-2-1-elastic-agent-adding-nginx-integration-agent-fail/380490/2):
>
> Hello @fabio.iovine From the error "{"file.name":"cmd/enroll\_cmd.go","file.line":806},"message":"Fleet Server - Error - listen tcp 0.0.0.0:8220: bind: address already in use","ecs.version":"1.6.0"} Error: fleet-server failed: context canceled" it seems the port is in use, could you please check what is the process which is using the port : sudo lsof -i :8220 If it is related to elastic-agent process of older installation maybe as you have already uninstalled the older agent, you can kill the…

This fails because I'm not allowed to use sudo. Also not from a fresh shell.

---

<div class="post-metadata">

**Author:** ![John\_Sc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_sc/32/140043_2.png) [@John\_Sc](https://discuss.elastic.co/u/John_Sc)\
**Post date:** [July 30, 2025, 7:40am UTC](https://discuss.elastic.co/t/elastic-observability-engineer-course-fleet-server-not-running/380580/3 "2025-07-30T07:40:40Z")

</div>

Got the following:

ss -tuln | grep :8220\*

(elastic) elastic@ip-172-31-0-129:~$ ss -tuln | grep :8220  
tcp LISTEN 0 4096 0.0.0.0:8220 0.0.0.0:\*  
tcp LISTEN 0 4096 [::]:8220 [::]:\*

---

<div class="post-metadata">

**Author:** ![fabio.iovine](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fabio.iovine/32/144319_2.png) [@fabio.iovine](https://discuss.elastic.co/u/fabio.iovine)\
**Post date:** [July 30, 2025, 9:28am UTC](https://discuss.elastic.co/t/elastic-observability-engineer-course-fleet-server-not-running/380580/4 "2025-07-30T09:28:04Z")

</div>

got the same problem, after a couple of attempts I abandoned this chapter and went ahead ...

---

<div class="post-metadata">

**Author:** ![John\_Sc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_sc/32/140043_2.png) [@John\_Sc](https://discuss.elastic.co/u/John_Sc)\
**Post date:** [July 30, 2025, 10:30am UTC](https://discuss.elastic.co/t/elastic-observability-engineer-course-fleet-server-not-running/380580/5 "2025-07-30T10:30:51Z")

</div>

Solved by recreating the environment by support.