rhino007US
commented
3 years ago I resolved this issue by installing the Chrome extension for Elasticsearch-head. But as an Engineer I still want to understand the questions above.
Open rhino007US opened 3 years ago
rhino007US
commented
3 years ago I resolved this issue by installing the Chrome extension for Elasticsearch-head. But as an Engineer I still want to understand the questions above.
Hi I have brought up Bitnami's ELK stack and installed Elasticsearch-heads. I think it is configured correctly, all of the required DEB libraries are there. I was able to install nodejs 14.17.0, Puppeteer, grunt, and chrome in headless mode (I do get the one error when I start it with grunt --force: (question 1) (node:6548) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! /root/elasticsearch-head-master/node_modules/puppeteer/.local-chromium/linux-856583/chrome-linux/chrome: error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file: No such file or directory
Which is a bit odd because supposedly that error was resolved at a lower level of nodejs. I have been using apt-get libatk-1.0.so.0, libtak, and libtak-1.0 is there a better way to add this library?
I don't know if that is causing the problem I'm having, but feedback about that would be welcome.
============================= THE MAIN QUESTION ============================== question #2:
I have it working to where I can access, from chrome:
http://NN.NN.NN.133/elastic-search-head?base_uri=http://NN.NN.NN.133/elastisearch
I opened the port in my firewall to only my Internet IP, for security, and I get a login prompt... But I can't login to it with the Bitnami application user, "user" and the password (which is found on the ELK stack server in /home/bitnami/bitnami_credentials file.)
not being sure if this is the required login I also set the Elasticsearch password to one I know and tried logging in as Elasticsearch that didn't work. Lastly I tried the bitnami user, the one you use to SSH onto the server box.
all of these give me the following message: "Unauthorized This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required."
Installing all this took a lot of brute force on my part, I wanted to bring it up quickly, too bad the plugin functionality has been removed... " cd /usr/share/elasticsearch/ ./bin/plugin -install mobz/elasticsearch-head."
Hopefully this is enough information to help me get some help on how to login to the Elasticsearch-head account.
Thank You, rhino007
question 3:
Our goal is to be able to replicate the data nodes in the ELK stack, by seeing beyond the single Ip of the instance in AWS. If someone knows more about how to do that another way we'd be interested. Perhaps in Kibana?
PPS: in the Bitnami documentation the Elasticsearch-head documentation says, "Elasticsearch-head is a Web front-end for an Elasticsearch cluster. For Elasticsearch 5.x, site plugins are not supported, so it needs to run as a standalone server.". I'm not 100% sure what this means.
Does it mean that it will only work in a deployment where elastic/logstash/kibani are on a single instance (as I suspect)
OR
Does it mean you need to build an second instance to watch the bitnami instance as we first thought? we think it is the first one because there are no instructions to set up communications between a second instance and the ELK stack server.