Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix instructions for uninstalling agent #1364

Closed
kilfoyle opened this issue Oct 4, 2024 · 0 comments · Fixed by #1368
Closed

Fix instructions for uninstalling agent #1364

kilfoyle opened this issue Oct 4, 2024 · 0 comments · Fixed by #1368
Assignees

Comments

@kilfoyle
Copy link
Contributor

kilfoyle commented Oct 4, 2024

The instructions in Uninstall Elastic Agents from edge hosts aren't working. See SDH for reference and suggested fix for the docs.


Customer Details - Description:
customer is trying to uninstall elastic agent

  • docs - https://www.elastic.co/guide/en/fleet/current/uninstall-elastic-agent.html#_uninstall_on_macos_linux_and_windows
    • snippet from docs - Be sure to run the uninstall command from the directory where Elastic Agent is running, as shown in the example below, and not from the directory where you previously ran the install command. Running the command from the wrong directory can leave the agent in an inconsistent state.
  • But, if we run uninstall from where it is running, then we receive this error message
    • error message - Error: error uninstalling agent: uninstall must be run from outside the installed path

So, the correct solution to uninstall elastic agent is to ...

  • be in a directory outside of of current install location.
  • install location is C:\Program Files\Elastic\Agent
  • run the command in C:\Program Files\Elastic or \tmp or even your default home directory
  • then run the uninstall command C:\"Program Files"\Elastic\Agent\elastic-agent.exe uninstall
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant