-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
bin/plugin can not install plugins on CentOS #4638
Comments
Similar story for a Debian 8.3 x64 VM. Steps needed to reproduce
Now, attempting to install a plugin results in the same behavior as above. Any of:
just produces the line
and then hangs until |
@Ploy-XIV thanks a lot for your detailed report. I wonder if you can check the permissions used to run this? is the logstash user able to write inside vendor/ directory? |
For the examples I made here in this bug report, I ran all the commands as root, so, the file permissions should not matter. (In other installs of Logstash I used to |
Ok! On Mon, Feb 8, 2016 at 3:17 PM Ploy notifications@github.com wrote:
|
It's of course possible that my cloud hoster did something crazy with the VM templates, and they aren't "same enough" compared to installs from official CentOS/Debian install media. |
Are you able to test with official distro? might be through vagrant?
On Mon, Feb 8, 2016 at 3:21 PM Ploy notifications@github.com wrote:
|
Just to check if it's an issue of the user running
Making sure that all the logstash files belong to the logstash user, just in case:
And attempt to install the plugin using the logstash user (who's home directory is
Result is exactly the same as before:
...and then nothing, until |
OK, I just tried again with CentOS installed myself from an official install medium ( Setup steps were the same as listed above, with the addition of configuring network and the OpenSSH server. Plugin installation works as expected here... I'll have a look and see if I can find out in what way my VM hoster's image is different that leads to breakage. I'm using DigitalOcean, BTW. |
Is your server able to access rubygems.org? Is there any firewall settings preventing external network actvity? |
It's not a networking issue, as installing a plugin from a local file (previously downloaded from rubygems) fails in exactly the same way, as documented in my first post. I had a look with with wireshark, and there is absolutely no network traffic when I run |
Just a quick update on some more things I have tried: I have now all in all tested five different OS instances (some discussed above already):
For some of the machines with issues I tried most of the available logstash 2.x releases, and the behavior seems to be exactly the same across all versions (that is: I tried debugging I've also found out that when I move my I have no idea how to investigate this issue further... |
When stracing java programs, especially for file or network-related activity, I recommend using |
@Ploy-XIV |
I have the exact same issue on Amazon Linux AMI and I can't figure out what to do to fix this. Works perfectly on Docker CentOS on an Ubuntu kernel. |
Same issue for me using CentOS 7 droplet on Digital Ocean. It seems to be related to a lack of entropy in the PRNG. I've resolved the problem by installing haveged. |
I had this problem on a physical box running jessie and using logstash v 5.1.1. I Installed haveged but it didn't fix the issue. Also in the process of trying to install the plugin my logstash install corrupted. I had to modify
Running it inside of strace was a success! How is this possible?
|
For me, this issue was solved when adding more resources. (On AWS, t2.micro -> t2.small). |
For me it looks to be an issue with the ENV vatiable not being referenced correctly, adding that to the Dockerfile built fine. |
I am unable to get
bin/plugin
to do anything useful other thanlist
I tried this on a freshly created CentOS 7.1 x64 VM. The commands listed below are literally my entire interaction with this VM:
Steps needed to reproduce
Install logstash on CentOS:
The file
/etc/yum.repos.d/logstash.repo
has the following content:The version of logstash that was installed is
2.2.0
.Attempt to install plugins using
bin/plugin
(with/without verification and install from local file):Expected outcome
Each of the executions of
bin/plugin
shown above should install a plugin (if it's not installed already).Actual outcome
plugin
hangs until it is killed for all tried invocations. I picked the plugin names at random, the plugins used are just examplesThe text was updated successfully, but these errors were encountered: