Hello,
Could you tell me what are the resources of the machine especially CPU and RAM ?
It seems that ES could not start in time. It can be either a service running on the same port as I thought before but it seems that not. So it can be either that ElasticSearch had not enough time to start and the start script exits.
You can try to edit manually the file /opt/datafari/bin/start-datafari.sh :
Lines 68 to 72 there is a code block related to ELK :
# Configure ELK
echo "Configure ELK"
cd $ELASTICSEARCH_HOME/bin
sudo -E su datafari -p -c "bash elasticsearch -p $ELASTICSEARCH_PID_FILE" &
sleep 10
#Test if Elasticsearch is up, if not then exit
curl -s --fail -XGET
http://localhost:9200/ || { echo "Fail to reach Elasticsearch on localhost:9200"; echo "Please check your network connection and, in case a proxy is configured, that a proxy exception exists for 'localhost' and '127.0.0.1' !"; sudo -E su datafari -p -c "kill $(cat $ELASTICSEARCH_PID_FILE)"; exit 1; }
First you can try to increase the sleep value to 120 so change sleep 10 to
sleep 120
If it still does not work, you can comment the line :
curl -s --fail -XGET
http://localhost:9200/ || { echo "Fail to reach Elasticsearch on localhost:9200"; echo "Please check your network connection and, in case a proxy is configured, that a proxy exception exists for 'localhost' and '127.0.0.1' !"; sudo -E su datafari -p -c "kill $(cat $ELASTICSEARCH_PID_FILE)"; exit 1; }
Just add # before the line :
#curl -s --fail -XGET http://localhost:9200/ || { echo "Fail to reach Elasticsearch on localhost:9200"; echo "Please check your network connection and, in case a proxy is configured, that a proxy exception exists for 'localhost' and '127.0.0.1' !"; sudo -E su datafari -p -c "kill $(cat $ELASTICSEARCH_PID_FILE)"; exit 1; }
We added another check mechanism in Datafari 4.1 to avoid this problem and be more verbose in the log.
Let me know if it solves your issue meantime.
Thanks,
Best regards,
Olivier Tavard