Problem: You receive an "Error starting elasticsearch-logging" when you attempt to run the start-unify.sh script. Subsequent restart attempts may also result in "NoNodeAvailableException" errors.
Cause: This error is most likely to be the result of Elasticsearch (elastic 5) logging shutting down incorrectly, which can corrupt the data directory for logs.
- Stop Tamr and its dependencies. See Restarting Tamr and Its Dependencies in the Tamr Documentation.
- Change to the Elasticsearch 5 directory and delete the data directory. Note: This is the data dictionary for logging, and is not used for user interface interactions.
- Start Tamr and its dependencies.
Updated 18 days ago