-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Plugin installation script ignores path.plugins #10673
Comments
@orweinberger thanks for reporting. Yes this is a known problem and I'm on it :) |
+1 |
The bin/plugin script now uses the default CONF_DIR & CONF_FILE environment vars. This allows to install a plugin even if Elasticsearch has been installed with a RPM or a DEB package. This commit also adds testing files for TAR archive and plugins installation. Closes elastic#10673
The bin/plugin script now uses the default CONF_DIR & CONF_FILE environment vars. This allows to install a plugin even if Elasticsearch has been installed with a RPM or a DEB package. This commit also adds testing files for TAR archive and plugins installation. Closes elastic#10673
The bin/plugin script now uses the default CONF_DIR & CONF_FILE environment vars. This allows to install a plugin even if Elasticsearch has been installed with a RPM or a DEB package. This commit also adds testing files for TAR archive and plugins installation. Closes elastic#10673
The bin/plugin script now uses the default CONF_DIR & CONF_FILE environment vars. This allows to install a plugin even if Elasticsearch has been installed with a RPM or a DEB package. This commit also adds testing files for TAR archive and plugins installation. Closes #10673
Just wanted to check what version this fix was released in, I'm still seeing the same problem in 1.7. |
@markwalkom I just tested with the cloud-azure plugin and ES 1.7, it seems OK. Can you please elaborate on your issue (paths, privileges, plugins, type of ES installation etc)? Thanks My output:
|
This is ES 1.7.0 (tar.gz) on OS X. I installed all of our commercial plugins;
As you can see they just installed to $ES_HOME. Then when I checked what was installed;
|
@markwalkom I could not reproduce it on Ubuntu or OSX. In your example, I think that the configuration file is not correctly resolved by the Can you edit the You can also pass the CONF_DIR and/or CONF_FILE as env vars like |
Hi, I get a CONF_FILE error when I now attempt to install any plugin in ES 2.1.1. I'm upgrading from 1.7.3 (where all my plugins worked fine) to 2.1.1 where they now don't. Can you help? Thanks |
@trekr5 please ask on https://discuss.elastic.co. |
Hi, I've asked the question here on discuss https://discuss.elastic.co/t/upgrading-elasticsearch-from-1-7-3-to-2-1-1/39281/2 with this same config issue that has stopped elasticsearch service from running properly on upgraded nodes and prevents correct install of plugins |
Custom directory that is defined in the
elasticsearch.yml
under thepath.plugins
settings is being ignored by thebin/plugin
script when installing new plugins.It attempts to install the plugin to the default directory and there is no way of manually setting the plugin script to install a plugin to a different location.
The text was updated successfully, but these errors were encountered: