AnsweredAssumed Answered

warden.servicename.conf file

Question asked by anthony_alteom on Sep 11, 2014
Latest reply on Sep 29, 2014 by anthony_alteom
Hi,

I tried to add a warden.servicename.conf file for ElasticSearch :

    services=elasticsearch:1:nfs
    service.displayname=ElasticSearch
    service.command.start=/opt/mapr/elasticsearch/bin/elasticsearch.sh start
    service.command.stop=/opt/mapr/elasticsearch/bin/elasticsearch.sh stop
    service.command.monitorcommand=/opt/mapr/elasticsearch/bin/elasticsearch.sh status
    service.command.type=BACKGROUND
    service.port=9200
    service.ui.port=9200
    service.uri=/
    service.logs.location=/var/log/elasticsearch/
    service.process.type=JAVA
    service.alarm.tersename=naelasticsearch
    service.alarm.label=ELASTICSEARCHDOWNALARM

I copied /etc/init.d/elasticsearch in /opt/mapr/initscripts and created the file : /opt/mapr/elasticsearch/bin/elasticsearch.sh

    #!/bin/bash
    /usr/bin/sudo su -c "/opt/mapr/initscripts/elasticsearch $*"
    exit $?

The script /opt/mapr/elasticsearch/bin/elasticsearch.sh works from command line (with mapr user).
But it doesn't work from the maprcli or from the admin webui.

Cluster Version : 3.1.1.26113.GA

Outcomes