# Issue for Elastic Observability Engineer Lab 2.1 - Elastic Agent

**URL:** <https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717>\
**Category:** Elastic Agent\
**Created:** [April 18, 2024, 1:52pm UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717 "2024-04-18T13:52:44Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![ganesh.pawar](https://avatars.discourse-cdn.com/v4/letter/g/a587f6/32.png) [@ganesh.pawar](https://discuss.elastic.co/u/ganesh.pawar)\
**Post date:** [April 27, 2024, 5:48am UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717/23 "2024-04-27T05:48:05Z")

</div>

elastic@ip-172-31-15-133:/opt/Elastic$ cd Agent/  
-bash: cd: Agent/: Permission denied  
elastic@ip-172-31-15-133:/opt/Elastic$ sudo -i

---

<div class="post-metadata">

**Author:** ![ganesh.pawar](https://avatars.discourse-cdn.com/v4/letter/g/a587f6/32.png) [@ganesh.pawar](https://discuss.elastic.co/u/ganesh.pawar)\
**Post date:** [April 27, 2024, 8:33am UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717/25 "2024-04-27T08:33:57Z")

</div>

I tried it and it always asked for sudo password for elastic...

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/c/0c71aa88b749fc3b1deea8134de2dbc4b066fb10.jpeg)

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 27, 2024, 10:16am UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717/26 "2024-04-27T10:16:21Z")

</div>

I think there's a restart button somewhere. It should recreate the VM if it was incorrectly created.  
i don't think you need to hack around.

But may be someone from the @elastic.training team could help.

---

<div class="post-metadata">

**Author:** ![Andre\_Murbach\_Maidl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andre_murbach_maidl/32/83508_2.png) [@Andre\_Murbach\_Maidl](https://discuss.elastic.co/u/Andre_Murbach_Maidl)\
**Post date:** [April 27, 2024, 3:40pm UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717/27 "2024-04-27T15:40:51Z")

</div>

That's corret @dadoonet: there's no need to hack aroud.

@ganesh.pawar I have replaced your environment. Please follow lab instructions carefully, because `sudo` access is limited for installing and running the Elastic Agent only.

Best,  
Andre

---

<div class="post-metadata">

**Author:** ![ganesh.pawar](https://avatars.discourse-cdn.com/v4/letter/g/a587f6/32.png) [@ganesh.pawar](https://discuss.elastic.co/u/ganesh.pawar)\
**Post date:** [April 28, 2024, 3:54am UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717/28 "2024-04-28T03:54:10Z")

</div>

@dadoonet I also do not want to hack around for these kind of issues....but if basic command is not working for almost 2-3 weeks..what someone will do... I am on lab 2. after 3 weeks now 🙂

---

<div class="post-metadata">

**Author:** ![ganesh.pawar](https://avatars.discourse-cdn.com/v4/letter/g/a587f6/32.png) [@ganesh.pawar](https://discuss.elastic.co/u/ganesh.pawar)\
**Post date:** [April 28, 2024, 3:54am UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717/29 "2024-04-28T03:54:52Z")

</div>

@Andre_Murbach_Maidl thanks....I hope this time it will worjk as expected...and I will be able to move t next labs....Again I do not want to play around with lab setup....but it should work as intended.....

---

<div class="post-metadata">

**Author:** ![AndreasR](https://avatars.discourse-cdn.com/v4/letter/a/779978/32.png) [@AndreasR](https://discuss.elastic.co/u/AndreasR)\
**Post date:** [June 13, 2024, 6:19am UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717/30 "2024-06-13T06:19:17Z")

</div>

I have problems at this point too.

Installation was successfull, but no data will be send. The agent status shows, that there are communication problems.

elastic@ip-172-31-2-34:~/elastic-agent-8.8.2-linux-x86\_64$ ./elastic-agent status  
Error: failed to communicate with Elastic Agent daemon: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /home/elastic/elastic-agent-8.8.2-linux-x86\_64/data/tmp/elastic-agent-control.sock: connect: no such file or directory"  
For help, please see our troubleshooting guide at [Troubleshoot common problems | Fleet and Elastic Agent Guide [8.8] | Elastic](https://www.elastic.co/guide/en/fleet/8.8/fleet-troubleshooting.html)  
elastic@ip-172-31-2-34:~/elastic-agent-8.8.2-linux-x86\_64$

@elastic.training could you please reset my environment?

---

<div class="post-metadata">

**Author:** ![Andre\_Murbach\_Maidl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andre_murbach_maidl/32/83508_2.png) [@Andre\_Murbach\_Maidl](https://discuss.elastic.co/u/Andre_Murbach_Maidl)\
**Post date:** [June 13, 2024, 3:18pm UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717/31 "2024-06-13T15:18:51Z")

</div>

Hi @AndreasR ,

I just replaced your lab environment.

Best,  
Andre

---

<div class="post-metadata">

**Author:** ![Lionel\_cgi](https://avatars.discourse-cdn.com/v4/letter/l/e5b9ba/32.png) [@Lionel\_cgi](https://discuss.elastic.co/u/Lionel_cgi)\
**Post date:** [August 11, 2025, 10:17am UTC](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717/32 "2025-08-11T10:17:04Z")

</div>

Hey,

I have the same error 🙂

lastic@ip-172-31-2-28:~/elastic-agent-8.8.2-linux-x86\_64$ ./elastic-agent status  
Error: failed to communicate with Elastic Agent daemon: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /home/elastic/elastic-agent-8.8.2-linux-x86\_64/data/tmp/elastic-agent-control.sock: connect: no such file or directory"  
For help, please see our troubleshooting guide at [Troubleshoot common problems | Fleet and Elastic Agent Guide [8.8] | Elastic](https://www.elastic.co/guide/en/fleet/8.8/fleet-troubleshooting.html)  
elastic@ip-172-31-2-28:~/elastic-agent-8.8.2-linux-x86\_64$

And to get Agent installed I had to add –insecure on the enroll command …

Could you please help me on this case ?

Best regards

Lionel

[Previous page](https://discuss.elastic.co/t/issue-for-elastic-observability-engineer-lab-2-1-elastic-agent/357717.md?page=1)
