Logstash: Can not remove my installed plugin

Created on 10 May 2019 · 9Comments · Source: elastic/logstash

hi
i installed my plugin . but when i want to remove my plugin or any other plugins , logstash said :

#my commands : /usr/share/logstash/bin/logstash-plugin remove logstash-filter-myplugin
#another command: /usr/share/logstash/bin/logstash-plugin remove logstash-filter-kv

ERROR: Operation aborted, cannot remove plugin, message: The path `/root/logstash-core` does not exist.

after i copy /usr/share/logstash/logstash-core to /root/logstash-core , error changed to :

ERROR: Operation aborted, cannot remove plugin, message: The path `/root/logstash-core-plugin-api` does not exist.

i think logstash dont know where is installed .

Version: elk 7
Operating System: ubuntu 18.4

Source

alah64

👍1

Most helpful comment

I'm not sure why this issue was closed considering that users should not have to workaround this with their own manual cd. Can this issue please be reopened? @alah64

remd on 1 Jul 2019

😄4

All 9 comments

Ok , i solve it by cd /usr/share/logstash/ command before execute remove command.

alah64 on 10 May 2019

👍3 🚀1

I'm not sure why this issue was closed considering that users should not have to workaround this with their own manual cd. Can this issue please be reopened? @alah64

remd on 1 Jul 2019

😄4

Yes, i am also facing this issue.

rkhapre on 17 Jul 2019

Facing the same issue here

jeffrey-e on 10 Dec 2019

Issue does not only impact 7.x, it shows up when moving from 6.6.2 -> 6.7.0/6.8.x

JazyK on 13 Jan 2020

The workaround alah64 mentioned works, but still impacts 7.6.

bangejsans on 3 Mar 2020

Facing the same issue here。

guanyufen123 on 17 Apr 2020

Facing the same issue here

logstash --version
logstash 7.6.2

I tried to modify the code to print the backtrace of the exception, and I found that this line.

gem "logstash-core", :path => "./logstash-core"

# In line /usr/local/Cellar/logstash/7.6.2/libexec/Gemfile:5
# I installed logstash by homebrew.

It seems like that "./logstash-core" is the reason of the bug.
I am not familiar with the source code, but I guess that Gemfile.template is the file responsible for it.