Hello team and sorry for the late response. Sharing with you some steps that solved this issue. 1- First, you will need to create any user differently from the root. If you are trying to start from root user, it will fail. 2- Set the write, read and executable privileges for this new user to the appd directory. 3- Then, with the new user, change the property values in your events-services-api-store.properties file to IP address instead of hostnames. egrep "dw.http.host|es.node.unicast.hosts|es.cluster.initial_master_nodes|es.cluster.http.hosts" ../conf/events-service-api-store.properties ad.dw.http.host=X.X.X.X ad.es.node.unicast.hosts=X.X.X.X:9300 ad.es.cluster.initial_master_nodes=X.X.X.X ad.es.cluster.http.hosts:X.X.X.X:9200 4- Add the following environment variable to the new user. export INSTALL_BOOTSTRAP_MASTER_ES8=true  5- Restart the Event-Service(ES) manually. Proceed with the steps below: (From events-service/processor directory) -> Need to run from this directory otherwise will fail bin/events-service.sh stop -f && rm -r events-service-api-store.id && rm -r elasticsearch.id If you have more than one cluster, run the following command on each node in the cluster. In my setup there is only one ES node. nohup bin/events-service.sh start -p conf/events-service-api-store.properties & After two or three minutes, check the opened ports. netstat -ant|egrep "9080|9081|9200|9300" -a -> all ports -n -> numeric ports -t -> tcp ports Thanks, Luiz Polli ... View more