Hi Matt, I haven't seen this error before, but my guess is that ES itself is having issues.
If you're using the service defined in Ambari, I'm surprised you even made it to this point on a single node. It requires, per the metainfo.xml, 3 data only nodes to be installed on the cluster. If you did manage to make it through the install of ES onto a single node it won't work regardless because the master node and data nodes have slightly different (and conflicting) settings. You'll have to spin up a separate ES instance. Assuming that ES is not an Ambari installed one, can you hit ES's _cluster/health endpoint to get the cluster status? I haven't seen those logs from Kibana before, but I'm guessing that it doesn't mean that Kibana is having issues, but that ES is based on "Status changed from uninitialized to yellow - Waiting for Elasticsearch" and ":"Status changed from yellow to red - Service Unavailable" If you do need to create a separate ES instance, Kibana should still be able to be managed through Ambari. A couple things would have to happen before ES can comfortably exist on a single node cluster, specifically we'd have to have master / data nodes optionally coexist and we'd have to make sure that everything works if datanodes < 3. Justin On Wed, Nov 30, 2016 at 9:18 PM, Matt Foley <[email protected]> wrote: > Apropos of the discussion of documenting the install procedure, I was > experiencing a lot of instability with the vagrant quick-dev-platform on my > Mac due to memory pressure, so I fired up a 16GB cloud vm and installed a > single-node “cluster” for Metron, using Ambari metron-mpack and rpms built > on my mac. I followed the instructions at https://community.hortonworks. > com/content/kbentry/60805/deploying-a-fresh-metron- > cluster-using-ambari-serv.html and just installed all services on the > single available node. The node is Centos 7, the browser is Firefox, and I > managed to get Python 2.7.11 on it. > > > > It all worked just fine, and all services including Metron are green in > Ambari. > > > > However, when I access localhost:5000, Kibana complains that > “plugin:elasticsearch” is “Service Unavailable”. (Red) > > In Kibana config, kibana_es_url is http://mfoley-metron-1. > openstacklocal:9200 > > In Elasticsearch config, http_port is “9200-9300” and transport_tcp_port > is “9300-9400” > > > > If I just point the browser at http://mfoley-metron-1.openstacklocal:9200 > , it responds: > > { > > "name" : "mfoley-metron-1.openstacklocal", > > "cluster_name" : "metron", > > "version" : { > > "number" : "2.3.3", > > "build_hash" : "218bdf10790eef486ff2c41a3df5cfa32dadcfde", > > "build_timestamp" : "2016-05-17T15:40:04Z", > > "build_snapshot" : false, > > "lucene_version" : "5.5.0" > > }, > > "tagline" : "You Know, for Search" > > } > > so Elasticsearch is listening on that port. > > > > Has anyone had experience how to resolve this problem with the Kibana > elasticsearch plugin? > > > > I’ve tried starting and stopping both elasticsearch and kibana; tried the > URL with and without a slash at the end; tried port 9300 as well as 9200 > (9300 doesn’t work in browser, nor in kibana either); and tried > un-commenting the set of elasticsearch-related timeouts in > kibana/config/kibana.yml. Nothing helped. Even with logging.verbose=true, > log only contains: > > > > {"type":"log","@timestamp":"2016-12-01T02:10:45+00:00"," > tags":["plugins","debug"],"pid":4863,"plugin":{"name":" > elasticsearch","version":"1.0.0"},"message":"Initializing plugin > elasticsearch"} > > > > {"type":"log","@timestamp":"2016-12-01T02:10:45+00:00"," > tags":["status","plugin:elasticsearch","info"],"pid":4863,"name":"plugin: > elasticsearch","state":"yellow","message":"Status changed from > uninitialized to yellow - Waiting for Elasticsearch","prevState":" > uninitialized","prevMsg":"uninitialized"} > > > > {"type":"log","@timestamp":"2016-12-01T02:10:45+00:00"," > tags":["status","plugin:elasticsearch","error"],"pid":4863,"name":"plugin: > elasticsearch","state":"red","message":"Status changed from yellow to red > - Service Unavailable","prevState":"yellow","prevMsg":"Waiting for > Elasticsearch"} > > > > which looks like it did NOT wait, even tho I left the timeouts set to many > seconds: > > > > # Time in milliseconds to wait for elasticsearch to respond to pings, > defaults to > > # request_timeout setting > > elasticsearch.pingTimeout: 1500 > > > > # Time in milliseconds to wait for responses from the back end or > elasticsearch. > > # This must be > 0 > > elasticsearch.requestTimeout: 30000 > > > > # Time in milliseconds for Elasticsearch to wait for responses from shards. > > # Set to 0 to disable. > > elasticsearch.shardTimeout: 0 > > > > # Time in milliseconds to wait for Elasticsearch at Kibana startup before > retrying > > elasticsearch.startupTimeout: 5000 > > > > Thanks in advance for any help, > > --Matt > > > > > > > >
