Logstash status (Bad):logstash is not running This type of error is indicated by the following log entry: If you see a user was not found error, the user does not exist in the htpasswd file. To look at the recent Nginx errors, use this command: If you have basic authentication enabled, and you are having trouble passing the authentication step, you should look at the Nginx error logs to determine the specifics of the problem. This should tell you exactly why Nginx can’t connect to Kibana. You can check the Nginx error logs for clues:
FILEBEATS ERR CONNECTING ERROR PUBLISHING EVENTS INSTALL
You should review the configuration portion of the Install Nginx section of the ELK stack tutorial. If that doesn’t resolve the issue, you may have an issue with your Nginx configuration. If Kibana isn’t running or not recognized, follow the instructions of the Install Kibana section of the ELK stack tutorial. The first step to resolving this issue is to check if Kibana is running with this command: If Kibana is not accessible, and you receive a 502 Bad Gateway error, Nginx is running but it’s unable to connect to Kibana. Cause: Nginx Is Running But Can’t Connect to Kibana If it reports that the service is running, you need to reconfigure Nginx, following the same instructions. If it reports that the service is not running or not recognized, resolve your issue by following the instructions of the Install Nginx section of the ELK stack tutorial.
You can check the status of the Nginx service with this command: This usually indicates that Nginx isn’t running. Nginx Error:This webpage is not available When accessing Kibana via a web browser, you may encounter a page with this error: Issue: Kibana Unable to connect to Elasticsearch If you configured Logstash to use a non-default index pattern, you can resolve the issue by specifying the proper index pattern in the text box. To resolve communication issues between Filebeat and Logstash, run through the Filebeat troubleshooting sections. To resolve communication issues between Logstash and Elasticsearch, run through the Logstash troubleshooting sections. In other words, your logs aren’t making it through the chain from Filebeat, to Logstash, to Elasticsearch for some reason. Typically, this means that your logs are not being stored in Elasticsearch due to communication issues from Logstash to Elasticsearch, and/or from your log shipper (e.g. “Unable to fetch mapping” indicates that Elasticsearch does not contain any entries that match the default logstash-* pattern. Do you have indices matching the pattern? You must select or create one to continue. That show the error msg in the title about SAN ips.Kibana warning:Warning No default index pattern. I followed this tutorial for ELK / filebeat installation This shows : T15:47:22+01:00 ERR Connecting error publishing events (retrying): x509: certificate is valid for, not .comĢ.using ip certs by putting 'subjectAltName = IP: ELK_server_private_IP' in openssl configuration then using: sudo openssl req -config /etc/ssl/openssl.cnf -x509 -days 3650 -batch -nodes -newkey rsa:2048 -keyout private/logstash-forwarder.key -out certs/logstash-forwarder.crt
T15:57:37+01:00 ERR Connecting error publishing events (retrying): x509: cannot validate certificate for because it doesn't contain any IP SANsġ.using FQDN for creating the ssl certs: sudo openssl req -subj '/CN=/' -x509 -days 3650 -batch -nodes -newkey rsa:2048 -keyout private/logstash-forwarder.key -out certs/logstash-forwarder.crt T15:57:36+01:00 ERR Connecting error publishing events (retrying): x509: cannot validate certificate for because it doesn't contain any IP SANs Metricbeats don't want to connect at all and show: Installation went well, filebeat is runing OK on the client and sending information to logstash (thanks to 'insecure: true). I'm trying to implement an ELK stack while gathering information with Filebeat and MetricBeat on clients.
0 kommentar(er)
