Hi I have installed both Elasticsearch and Kibana on the same server and I am trying to install the X-Pack plugin for the Elasticsearch. I have downloaded the plugin zip file and I tried the following command.
./plugin install file:///root/x-pack-5.1.1.zip
And I got the following error:
Verifying file:/root/x-pack-5.1.1.zip checksums if available ...
NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Could not find plugin descriptor 'plugin-descriptor.properties' in plugin zip
`
Did you try with elastic search-plugin command ?
I tried below steps, for me its working.
To add xpack extension for elasticsearch
go to /usr/share/elasticsearch/bin
bin/elasticsearch-plugin install x-pack
To add xpack extension for kibana
go to /usr/share/kibana/bin
bin/kibana-plugin install x-pack
Set the passwords for all built-in users:
go to /usr/share/elasticsearch
bin/x-pack/setup-passwords interactive
Here it will ask passwords for installed services
Open the kibana.yml file and change the following:
elasticsearch.username: "ur-username"
elasticsearch.password: "ur-password"
Restart elasticsearch, logstash and kibana
Related
I had installed x-pack earlier and used it, but The elasticsearch.stdout log says :
java.lang.IllegalArgumentException: unknown secure setting
[bootstrap.password] please check that any required plugins are
installed, or check the breaking changes documentation for removed
settings
Thanks.
When you install X-Pack, bootstrap password is added to the keystore. If the elastic user does not have a password, the bootstrap is used by default. So, when it is set but don't run elasticsearch with X-Pack, elasticsearch fails!
Considering you uninstalled the X-Pack, I can recommend you remove it from the keystore by running the following command after navigating your [elacticsearch]/bin directory:
elasticsearch-keystore remove bootstrap.password
I am new to elasticsearch, logstash and kibana .
I am using Windows
i recently install x-pack plugin by folowing this tutorial :
https://www.elastic.co/guide/en/x-pack/5.1/installing-xpack.html
the main point is :
Go to ES_PATH
elasticsearch-plugin install x-pack
Go to Kibana PATH
kibana-plugin install x-pack
everything goes well, until i try to verify my x-pack instalation.
i go to kibana url. http://localhost:5601/
if everything is right, based on documentation, i should be prompted to login to kibana.
but, all i got is this message:https://stackoverflow.com/questions/ask
I am trying to install kibana using rpm kibana-4.5.0-1.x86_64.rpm.
However when i try to start the Kibana process, i am getting below prompt
Starting kibana....... unable to start process kibana.
To check the reason i have enabled log file by setting the below parameter in kibana.yml :
logging.dest: /opt/kibana/kibana.log
However no log file is getting created and i am unable to identify why kibana process is not starting.
Any suggestion would be appreciated..
Please check ---
RPM install is not supported on distributions with old versions of RPM, such as SLES 11 and CentOS 5.
My suggetion you can install Kibana with .tar.gz
Can follow the link :
https://www.elastic.co/guide/en/kibana/current/targz.html
I'm not able to access marvel in my browser.
http://localhost:9200/_plugins/marvel/ returns
{"error": "ElasticsearchIllegalArgumentException[No feature for name [marvel]]","status": 400}
I have installed elastic search 1.7.1 and its up and running running at http://localhost:9200/
I'm running on a window 2008R2 server with chrome and java 1.7.0_79
I did (and tried) the following things:
I installed the marvel plugin marvel (marvel-latest.zip). The
folder marvel folder is created in the plugins folder
The log shows the plugin is started ([INFO ][plugins ]
[MY_01_dev] loaded [marvel], sites [marvel])
tried giving in teh path to the index page manually (http://localhost:9200/_plugins/marvel/_site/kibana/index.html#/dashboard)
Changed the config with: marvel.agent.exporter.es.hosts: localhost:9200
No luck so far, all commands with cURL seems to work, but as much as I'm fond of command lines, my colleagues aren't, so i realy would like to get the plugin up and running
The url is not with _plugins, but with _plugin (singular):
http://localhost:9200/_plugin/marvel/kibana/index.html#/dashboard/file/marvel.overview.json
Marvel and sense plugin should be installed to Kibana and then access it using marvel agent on elastic node.
https://stackoverflow.com/a/33732567/1013528
I'm trying to setup Shield for Elasticsearch, but had some trouble
When I try to start Elasticsearch like:
/usr/share/elasticsearch/bin/elasticsearch
all work as expected, but when I'm trying to start/restart Elasticsearch like:
/etc/init.d/elasticsearch srart
I've got error described below
[2015-02-17 21:44:09,662][ERROR][shield.audit.logfile ] [Tusk] [rest] [authentication_failed] origin_address=[/192.168.88.17:58291], principal=[es_admin], uri=[/_aliases?pretty=true]
OS: Ubuntu 12.04
Elasticsearch: 1.4.3
Shield: 1.0.1
Elasticsearch and Shield were running with default settings
If your elasticsearch configs are not in /usr/share/elasticsearch but lets say at /etc/elasticsearch
Then just move the usr/share/elasticsearch/config/shield to /etc/elasticseach
Take care that if you start elasticsearch with the user elasticsearch that the new /etc/elasticsearch/shield folder belongs to the user elasticsearch.
If that doesn't make it, then also see this
http://www.elasticsearch.org/guide/en/shield/current/getting-started.html#_configuring_your_environment
Same thing happened with me when i tried to add shield to our elasticsearch cluster to add auth based access to elasticsearch data.
I was on ubuntu 14.04 machine and elasticsearch was installed using a .deb package from elastic-download-link.
Elasticsearch was using a service startup script from
/etc/init.d/elasticsearch
in which the configuration was mentioned as:
# Elasticsearch configuration directory
CONF_DIR=/etc/$NAME
But when i tried to install shield plugin on elasticsearch from this-link
and tried to add user on shield by following es-docs using this command.
sudo bin/shield/esusers useradd es_admin -r admin
shield configuration was being updated in
/usr/share/elasticsearch/config/shield/
but elasticsearch server was expecting configuration files to be in
/etc/elasticsearch/shield/
due to this mismatch in read configuration file for shield and new updated file with newly added users on shield causing this authentication failure.
This can be solved either by moving
/usr/share/elasticsearch/config/shield/
to
/etc/elasticsearch/shield/
or by changing conf file location in
/etc/init.d/elasticsearch
as
# Elasticsearch configuration directory
CONF_DIR=/usr/share/elasticsearch/config/