Error code 127 updating the master archive
If Logstash isn't running, you won't be able to receive and parse logs from log shippers, such as Filebeat, and store the processed logs in Elasticsearch.
This section will show you how to check if Logstash is functioning normally.
The Nginx component of the ELK stack serves as a reverse proxy to Kibana.
If Nginx is not running or configured properly, you will not be able to access the Kibana interface.
Elasticsearch may not be running, or Kibana may be configured to look for Elasticsearch on the wrong host and port.
To resolve this issue, make sure that Elasticsearch is running by following the Elasticsearch troubleshooting sections.
If it reports that the service is running, you need to reconfigure Nginx, following the same instructions.
If Kibana is not accessible, and you receive a If Kibana isn't running or not recognized, follow the instructions of the Install Kibana section of the ELK stack tutorial.
For example, if Elasticsearch is running on After Kibana has restarted, open Kibana in a web browser and verify that the error was resolved.If Logstash has errors in its configuration files, which are located in the directory, the service will not be able to start properly.The best thing to do is check the Logstash logs for clues about why it is failing.If you see log entries that include error messages, try and read the message(s) to figure out what is going wrong.Here is an example of the error logs you might see if the Logstash configuration has a syntax error (mismatched curly braces): The last message that says that we might be interested in validating the configuration indicates that the configuration contains a syntax error.
If it reports as "not running", it is probably misconfigured.