How to resolve mission control 3.0 install failures due to ElasticSearch forbidding Root user to run it
JFrog Mission Control 3.0+
Some environments use Root user to perform installs. ElasticSearch 6.1.1 has several bootstrap checks that prevent Root from executing elasticSearch.
The install script uses the logged-in-user that executes the script, and as such will fail when it tries to start Elasticsearch if Root ran the install.
- create service ID (AD) *
- add service ID to sudo wheel group
- login as step #1 service ID
- Run this command to install Mission Control: ‘sudo [service ID] ./path to mission control installation script/installJFMC-redhat.sh –‘
Mission control can then be run as any qualified user, as ElasticSearch will now use an internal MissionControl user.