instance won't start on Ubuntu 14.04

[lsh-0]

I'm running a box attempting to configure elasticsearch, kibana and logstash.

I'm trying to determine if the elasticsearch instance is running, but it doesn't appear to be:

vagrant@env1:~$ sudo service elasticsearch status
 * elasticsearch is not running
vagrant@env1:~$ sudo service elasticsearch start
 * Starting Elasticsearch Server                                                             [ OK ] 
vagrant@env1:~$ sudo service elasticsearch status
 * elasticsearch is not running

and

vagrant@env1:~$ sudo /etc/init.d/elasticsearch status
 * elasticsearch is not running
vagrant@env1:~$ sudo /etc/init.d/elasticsearch start
 * Starting Elasticsearch Server                                                             [ OK ] 
vagrant@env1:~$ sudo /etc/init.d/elasticsearch status
 * elasticsearch is not running

and

vagrant@env1:~$ curl -XGET localhost:9200/_nodes/_all/process?pretty
curl: (7) Failed to connect to localhost port 9200: Connection refused

firewall rules:

vagrant@env1:~$ sudo iptables --list
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination    

my configuration is:

class { 'elasticsearch': 
    package_url => 'https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-1.3.2.deb',
}

elasticsearch::instance { 'es-01': }

and this doesn't work either:

vagrant@env1:~$ sudo /etc/init.d/elasticsearch-es-01 status
 * elasticsearch is not running
vagrant@env1:~$ sudo /etc/init.d/elasticsearch-es-01 start
 * Starting Elasticsearch Server es-01                                        [ OK ] 
vagrant@env1:~$ sudo /etc/init.d/elasticsearch-es-01 status
 * elasticsearch is not running

I'm new to Elasticsearch, puppet and this module and this is getting quite frustrating. Do you have any insight into what the problem might be or how I've managed to misconfigure your module?

[lsh-0]

Here is my source for the vagrant box and the elasticsearch config (puppet/manifests/site.pp):
https://bitbucket.org/lskibinski/kibana-logstash-elasticsearch/src/

[lsh-0]

I found the solution to this after finally getting some (any) output from elasticsearch by running it directly:

vagrant@env1:/usr/share/elasticsearch/bin$ ./elasticsearch
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/elasticsearch/bootstrap/Elasticsearch : Unsupported major.minor version 51.0
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:643)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
    at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
Could not find the main class: org.elasticsearch.bootstrap.Elasticsearch. Program will exit.

It was a version mismatch between the upgraded version of Elasticsearch (1.2.1 -> 1.3.2) I was using and the older version of OpenJDK I was running (1.6). I replaced the puppet module I was using to install java and OpenJDK 1.7 now is installed and I can see the instance running correctly:

vagrant@env1:/usr/share/elasticsearch/bin$ sudo /etc/init.d/elasticsearch status
 * elasticsearch is not running
vagrant@env1:/usr/share/elasticsearch/bin$ sudo /etc/init.d/elasticsearch-es-01 status
 * elasticsearch is running

[lsh-0]

perhaps having the elasticsearch instance fail more noisily would be a good thing? might be outside the scope of this module though.

[electrical]

Hi,

Very good point.
As far as i know the run should fail since its unable to start ES right?
Or doesn't it do that?
If that's not the case it would be a bug in the init script ( not exiting correctly )

[lsh-0]

Or doesn't it do that?

Nope ;)

Provisioning was working perfectly, however elasticsearch wasn't coming up. I should have tried running it directly earlier, but this had never given a problem before. I investigated the init script and made it echo the command it ran instead of running it, then ran it by hand and it gave no output whatsoever. I suspect it probably returned a successful response as well - which is why the service elasticsearch-es-01 start command in the OP was saying [OK], instead of failing.

If puppet is supposed to fail then it is a bug. Re-opening. Let me know if I can provide any further help.

[electrical]

If the init script returns an OK ( exit code 0 ) then puppet assumes it was all fine.
Seems to be an issue in the init script assuming we can catch it in there somehow.
Will do some further investigation tomorrow on this.

[lsh-0]

if it helps, you can clone this revision of that repo mentioned above to
replicate the problem:

hg clone https://bitbucket.org/lskibinski/kibana-logstash-elasticsearch/src/ -r 9

On 2014-09-07 19:06, Richard Pijnenburg wrote:

If the init script returns an OK ( exit code 0 ) then puppet assumes
it was all fine.
Seems to be an issue in the init script assuming we can catch it in
there somehow.
Will do some further investigation tomorrow on this.

Reply to this email directly or view it on GitHub [1].

Links:

[1]
#182 (comment)

[cestinger]

I am experiencing this same issue on ubuntu 14.04. I can run the start-stop-daemon command directly on the command line and the elasticsearch instance starts up fine. Using 'service elasticsearch start, produces an OK on the command line, but the service is not starting and is not logging anything to the log.

running the command that the init script runs directly on the command line:
root@xxxx1:/var/log/elasticsearch# start-stop-daemon --start -b --user elasticsearch -c elasticsearch --pidfile /var/run/elasticsearch.pid --exec /usr/share/elasticsearch/bin/elasticsearch -- -d -p /var/run/elasticsearch.pid -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch
root@xxxx1:/var/log/elasticsearch# ps -ef |grep ela
elastic+ 27509 1 99 18:07 ? 00:00:03 /usr/local/java/jre1.7.0_55/bin/java -Xms256m -Xmx1g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Delasticsearch -Des.pidfile=/var/run/elasticsearch.pid -Des.path.home=/usr/share/elasticsearch -cp :/usr/share/elasticsearch/lib/elasticsearch-1.3.2.jar:/usr/share/elasticsearch/lib/:/usr/share/elasticsearch/lib/sigar/ -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch org.elasticsearch.bootstrap.Elasticsearch
root 27552 2079 0 18:07 pts/1 00:00:00 grep --color=auto ela

now trying to run it with the service framework with tracing turned on:
root@xxxx1:/var/log/elasticsearch# service elasticsearch restart

• PATH=/bin:/usr/bin:/sbin:/usr/sbin
• NAME=elasticsearch
• DESC=Elasticsearch Server
• DEFAULT=/etc/default/elasticsearch
• id -u
• [ 0 -ne 0 ]
• . /lib/lsb/init-functions
• run-parts --lsbsysinit --list /lib/lsb/init-functions.d
• [ -r /lib/lsb/init-functions.d/20-left-info-blocks ]
• . /lib/lsb/init-functions.d/20-left-info-blocks
• [ -r /lib/lsb/init-functions.d/50-ubuntu-logging ]
• . /lib/lsb/init-functions.d/50-ubuntu-logging
• LOG_DAEMON_MSG=
• FANCYTTY=
• [ -e /etc/lsb-base-logging.sh ]
• true
• [ -r /etc/default/rcS ]
• . /etc/default/rcS
• UTC=yes
• ES_USER=elasticsearch
• ES_GROUP=elasticsearch
• JDK_DIRS=/usr/local/java/jre1.7.0_55
• [ -r /usr/local/java/jre1.7.0_55/bin/java -a -z ]
• JAVA_HOME=/usr/local/java/jre1.7.0_55
• export JAVA_HOME
• . /etc/profile
• [ # ]
• [ ]
• id -u
• [ 0 -eq 0 ]
• PS1=#
• [ -d /etc/profile.d ]
• [ -r /etc/profile.d/Z97-byobu.sh ]
• . /etc/profile.d/Z97-byobu.sh
• [ -n ]
• [ = byobu ]
• [ = byobu-screen ]
• [ = byobu-tmux ]
• [ -r /etc/profile.d/bash_completion.sh ]
• . /etc/profile.d/bash_completion.sh
• [ -n -a -n # -a -z ]
• unset i
• JAVA_HOME=/usr/local/java/jre1.7.0_55
• PATH=/bin:/usr/bin:/sbin:/usr/sbin:/bin:/usr/local/java/jre1.7.0_55/bin
• export JAVA_HOME
• export PATH
• ES_HOME=/usr/share/elasticsearch
• MAX_OPEN_FILES=65535
• LOG_DIR=/var/log/elasticsearch
• DATA_DIR=/var/lib/elasticsearch
• WORK_DIR=/tmp/elasticsearch
• CONF_DIR=/etc/elasticsearch
• CONF_FILE=/etc/elasticsearch/elasticsearch.yml
• MAX_MAP_COUNT=262144
• [ -f /etc/default/elasticsearch ]
• . /etc/default/elasticsearch
• ES_HEAP_SIZE=32
• PID_FILE=/var/run/elasticsearch.pid
• DAEMON=/usr/share/elasticsearch/bin/elasticsearch
• DAEMON_OPTS=-d -p /var/run/elasticsearch.pid -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch
• export ES_HEAP_SIZE
• export ES_HEAP_NEWSIZE
• export ES_DIRECT_SIZE
• export ES_JAVA_OPTS
• test -x /usr/share/elasticsearch/bin/elasticsearch
• [ -f /var/run/elasticsearch.pid ]
• /etc/init.d/elasticsearch stop
• PATH=/bin:/usr/bin:/sbin:/usr/sbin
• NAME=elasticsearch
• DESC=Elasticsearch Server
• DEFAULT=/etc/default/elasticsearch
• id -u
• [ 0 -ne 0 ]
• . /lib/lsb/init-functions
• run-parts --lsbsysinit --list /lib/lsb/init-functions.d
• [ -r /lib/lsb/init-functions.d/20-left-info-blocks ]
• . /lib/lsb/init-functions.d/20-left-info-blocks
• [ -r /lib/lsb/init-functions.d/50-ubuntu-logging ]
• . /lib/lsb/init-functions.d/50-ubuntu-logging
• LOG_DAEMON_MSG=
• FANCYTTY=
• [ -e /etc/lsb-base-logging.sh ]
• true
• [ -r /etc/default/rcS ]
• . /etc/default/rcS
• UTC=yes
• ES_USER=elasticsearch
• ES_GROUP=elasticsearch
• JDK_DIRS=/usr/local/java/jre1.7.0_55
• [ -r /usr/local/java/jre1.7.0_55/bin/java -a -z /usr/local/java/jre1.7.0_55 ]
• export JAVA_HOME
• . /etc/profile
• [ # ]
• [ ]
• id -u
• [ 0 -eq 0 ]
• PS1=#
• [ -d /etc/profile.d ]
• [ -r /etc/profile.d/Z97-byobu.sh ]
• . /etc/profile.d/Z97-byobu.sh
• [ -n ]
• [ = byobu ]
• [ = byobu-screen ]
• [ = byobu-tmux ]
• [ -r /etc/profile.d/bash_completion.sh ]
• . /etc/profile.d/bash_completion.sh
• [ -n -a -n # -a -z ]
• unset i
• JAVA_HOME=/usr/local/java/jre1.7.0_55
• PATH=/bin:/usr/bin:/sbin:/usr/sbin:/bin:/usr/local/java/jre1.7.0_55/bin
• export JAVA_HOME
• export PATH
• ES_HOME=/usr/share/elasticsearch
• MAX_OPEN_FILES=65535
• LOG_DIR=/var/log/elasticsearch
• DATA_DIR=/var/lib/elasticsearch
• WORK_DIR=/tmp/elasticsearch
• CONF_DIR=/etc/elasticsearch
• CONF_FILE=/etc/elasticsearch/elasticsearch.yml
• MAX_MAP_COUNT=262144
• [ -f /etc/default/elasticsearch ]
• . /etc/default/elasticsearch
• ES_HEAP_SIZE=32
• PID_FILE=/var/run/elasticsearch.pid
• DAEMON=/usr/share/elasticsearch/bin/elasticsearch
• DAEMON_OPTS=-d -p /var/run/elasticsearch.pid -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch
• export ES_HEAP_SIZE
• export ES_HEAP_NEWSIZE
• export ES_DIRECT_SIZE
• export ES_JAVA_OPTS
• test -x /usr/share/elasticsearch/bin/elasticsearch
• log_daemon_msg Stopping Elasticsearch Server
• [ -z Stopping Elasticsearch Server ]
• log_use_fancy_output
• TPUT=/usr/bin/tput
• EXPR=/usr/bin/expr
• [ -t 1 ]
• [ xxterm != x ]
• [ xxterm != xdumb ]
• [ -x /usr/bin/tput ]
• [ -x /usr/bin/expr ]
• /usr/bin/tput hpa 60
• /usr/bin/tput setaf 1
• [ -z ]
• FANCYTTY=1
• true
• /usr/bin/tput xenl
• /usr/bin/tput cols
• COLS=80
• [ 80 ]
• [ 80 -gt 6 ]
• /usr/bin/expr 80 - 7
• COL=73
• log_use_plymouth
• [ n = y ]
• plymouth --ping
• printf * Stopping Elasticsearch Server
  • Stopping Elasticsearch Server + /usr/bin/expr 80 - 1
• /usr/bin/tput hpa 79
  + printf
  • [ -f /var/run/elasticsearch.pid ]
• start-stop-daemon --stop --pidfile /var/run/elasticsearch.pid --user elasticsearch --retry=TERM/20/KILL/5
• [ 0 -eq 1 ]
• [ 1 -eq 3 ]
• rm -f /var/run/elasticsearch.pid
• log_end_msg 0
• [ -z 0 ]
• [ 73 ]
• [ -x /usr/bin/tput ]
• log_use_plymouth
• [ n = y ]
• plymouth --ping
• printf \r
• /usr/bin/tput hpa 73
  + [ 0 -eq 0 ]
• echo [ OK ]
  [ OK ]
• return 0
• exit 0
• sleep 1
• /etc/init.d/elasticsearch start
• PATH=/bin:/usr/bin:/sbin:/usr/sbin
• NAME=elasticsearch
• DESC=Elasticsearch Server
• DEFAULT=/etc/default/elasticsearch
• id -u
• [ 0 -ne 0 ]
• . /lib/lsb/init-functions
• run-parts --lsbsysinit --list /lib/lsb/init-functions.d
• [ -r /lib/lsb/init-functions.d/20-left-info-blocks ]
• . /lib/lsb/init-functions.d/20-left-info-blocks
• [ -r /lib/lsb/init-functions.d/50-ubuntu-logging ]
• . /lib/lsb/init-functions.d/50-ubuntu-logging
• LOG_DAEMON_MSG=
• FANCYTTY=
• [ -e /etc/lsb-base-logging.sh ]
• true
• [ -r /etc/default/rcS ]
• . /etc/default/rcS
• UTC=yes
• ES_USER=elasticsearch
• ES_GROUP=elasticsearch
• JDK_DIRS=/usr/local/java/jre1.7.0_55
• [ -r /usr/local/java/jre1.7.0_55/bin/java -a -z /usr/local/java/jre1.7.0_55 ]
• export JAVA_HOME
• . /etc/profile
• [ # ]
• [ ]
• id -u
• [ 0 -eq 0 ]
• PS1=#
• [ -d /etc/profile.d ]
• [ -r /etc/profile.d/Z97-byobu.sh ]
• . /etc/profile.d/Z97-byobu.sh
• [ -n ]
• [ = byobu ]
• [ = byobu-screen ]
• [ = byobu-tmux ]
• [ -r /etc/profile.d/bash_completion.sh ]
• . /etc/profile.d/bash_completion.sh
• [ -n -a -n # -a -z ]
• unset i
• JAVA_HOME=/usr/local/java/jre1.7.0_55
• PATH=/bin:/usr/bin:/sbin:/usr/sbin:/bin:/usr/local/java/jre1.7.0_55/bin
• export JAVA_HOME
• export PATH
• ES_HOME=/usr/share/elasticsearch
• MAX_OPEN_FILES=65535
• LOG_DIR=/var/log/elasticsearch
• DATA_DIR=/var/lib/elasticsearch
• WORK_DIR=/tmp/elasticsearch
• CONF_DIR=/etc/elasticsearch
• CONF_FILE=/etc/elasticsearch/elasticsearch.yml
• MAX_MAP_COUNT=262144
• [ -f /etc/default/elasticsearch ]
• . /etc/default/elasticsearch
• ES_HEAP_SIZE=32
• PID_FILE=/var/run/elasticsearch.pid
• DAEMON=/usr/share/elasticsearch/bin/elasticsearch
• DAEMON_OPTS=-d -p /var/run/elasticsearch.pid -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch
• export ES_HEAP_SIZE
• export ES_HEAP_NEWSIZE
• export ES_DIRECT_SIZE
• export ES_JAVA_OPTS
• test -x /usr/share/elasticsearch/bin/elasticsearch
• checkJava
• [ -x /usr/local/java/jre1.7.0_55/bin/java ]
• JAVA=/usr/local/java/jre1.7.0_55/bin/java
• [ ! -x /usr/local/java/jre1.7.0_55/bin/java ]
• [ -n -a -z 32 ]
• log_daemon_msg Starting Elasticsearch Server
• [ -z Starting Elasticsearch Server ]
• log_use_fancy_output
• TPUT=/usr/bin/tput
• EXPR=/usr/bin/expr
• [ -t 1 ]
• [ xxterm != x ]
• [ xxterm != xdumb ]
• [ -x /usr/bin/tput ]
• [ -x /usr/bin/expr ]
• /usr/bin/tput hpa 60
• /usr/bin/tput setaf 1
• [ -z ]
• FANCYTTY=1
• true
• /usr/bin/tput xenl
• /usr/bin/tput cols
• COLS=80
• [ 80 ]
• [ 80 -gt 6 ]
• /usr/bin/expr 80 - 7
• COL=73
• log_use_plymouth
• [ n = y ]
• plymouth --ping
• printf * Starting Elasticsearch Server
  • Starting Elasticsearch Server + /usr/bin/expr 80 - 1
• /usr/bin/tput hpa 79
  + printf
  • pidofproc -p /var/run/elasticsearch.pid elasticsearch
• local pidfile base status specified pid OPTIND
• pidfile=
• specified=
• OPTIND=1
• getopts p: opt
• pidfile=/var/run/elasticsearch.pid
• specified=specified
• getopts p: opt
• shift 2
• [ 1 -ne 1 ]
• base=elasticsearch
• [ ! specified ]
• [ -n /var/run/elasticsearch.pid -a -r /var/run/elasticsearch.pid ]
• [ -n specified ]
• [ -e /var/run/elasticsearch.pid -a ! -r /var/run/elasticsearch.pid ]
• return 3
• pid=
• [ -n ]
• mkdir -p /var/log/elasticsearch /var/lib/elasticsearch /tmp/elasticsearch
• chown elasticsearch:elasticsearch /var/log/elasticsearch /var/lib/elasticsearch /tmp/elasticsearch
• touch /var/run/elasticsearch.pid
• chown elasticsearch:elasticsearch /var/run/elasticsearch.pid
• [ -n 65535 ]
• ulimit -n 65535
• [ -n ]
• [ -n 262144 ]
• sysctl -q -w vm.max_map_count=262144
• start-stop-daemon --start -b --user elasticsearch -c elasticsearch --pidfile /var/run/elasticsearch.pid --exec /usr/share/elasticsearch/bin/elasticsearch -- -d -p /var/run/elasticsearch.pid -Des.default.config=/etc/elasticsearch/elasticsearch.yml -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/var/lib/elasticsearch -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch
• log_end_msg 0
• [ -z 0 ]
• [ 73 ]
• [ -x /usr/bin/tput ]
• log_use_plymouth
• [ n = y ]
• plymouth --ping
• printf \r
• /usr/bin/tput hpa 73
  + [ 0 -eq 0 ]
• echo [ OK ]
  [ OK ]
• return 0
• exit 0
• exit 0
  root@xxxx1:/var/log/elasticsearch# ps -ef |grep ela
  root 27823 2079 0 18:08 pts/1 00:00:00 grep --color=auto ela

[edwardsmit]

I have the same problem on Ubuntu 12.04. Both with master as well as 0.3.2 of this provider.
I've narrowed it down to "When I've got a ES_HEAP_SIZE specified in /etc/default/elasticsearch the service won't start"
@cestinger can you confirm my observation? So does your service start when you comment-out ES_HEAP_SIZE in the default file?
BTW when you run the start-stop-daemon yourself you are not exporting ES_HEAP_SIZE so the default is used.
[update] Oh, forget my observation, I haven't got sufficient memory free for the memory I requested, taht's why it won't start. Would be nice if the service-script could echo the problem detected by the bin/elasticsearch script

[ericmenard]

I observed the same behaviour without any settings about the ES_HEAP_SIZE.
sudo /etc/init.d/elasticsearch start --> [OK]
and sudo /etc/init.d/elasticsearch status --> * elasticsearch is not running

But if I'm doing (command extracted by adding this line in the /etc/init.d/elasticsearch script just above the line starting the daemon -> echo start-stop-daemon --start -b --user "$ES_USER" -c "$ES_USER" --pidfile "$PID_FILE" --exec $DAEMON -- $DAEMON_OPTS
start-stop-daemon --start -b --user "$ES_USER" -c "$ES_USER" --pidfile "$PID_FILE" --exec $DAEMON -- $DAEMON_OPTS)
and from the printout of sudo /etc/init.d/elasticsearch start in the command line i"m doing:
sudo start-stop-daemon --start -b --user elasticsearch -c elasticsearch --pidfile /var/run/elasticsearch.pid --exec /usr/share/elasticsearch/bin/elasticsearch -- -d -p /var/run/elasticsearch.pid --default.config=/etc/elasticsearch/elasticsearch.yml --default.path.home=/usr/share/elasticsearch --default.path.logs=/var/log/elasticsearch --default.path.data=/var/lib/elasticsearch --default.path.work=/tmp/elasticsearch --default.path.conf=/etc/elasticsearch

then I got sudo /etc/init.d/elasticsearch status --> * elasticsearch is running
However, if I stop it, I cannot restart it unless I re-run sudo /etc/init.d/elasticsearch start and relaunch the long command: sudo start-stop-daemon --start -b --user elasticsearch -c elasticsearch --pidfile /var/run/elasticsearch.pid --exec /usr/share/elasticsearch/bin/elasticsearch -- -d -p /var/run/elasticsearch.pid --default.config=/etc/elasticsearch/elasticsearch.yml --default.path.home=/usr/share/elasticsearch --default.path.logs=/var/log/elasticsearch --default.path.data=/var/lib/elasticsearch --default.path.work=/tmp/elasticsearch --default.path.conf=/etc/elasticsearch

Conclusion, I'm lost

[electrical]

Do remember that with the instance parts the normal init script should not be used and most likely won't start indeed.
You'll need to use the /etc/init.d/elasticsearch-$instance_name script.

Cheers.

[cestinger]

What I found on mine was that I was not specifying g for gigabyte in the
ES_HEAP_SIZE definition in the /etc/default/elasticsearch file. Once I
fixed that, it started up fine.

ES_HEAP_SIZE=24g

took me quite a while to figure it out, it was giving no error messages at
all.

On Fri, Dec 5, 2014 at 5:18 AM, Edward Smit notifications@github.com
wrote:

I have the same problem on Ubuntu 12.04. Both with master as well as 0.3.2
of this provider.
I've narrowed it down to "When I've got a ES_HEAP_SIZE specified in
/etc/default/elasticsearch the service won't start"
@cestinger https://github.com/cestinger can you confirm my observation?
So does your service start when you comment-out ES_HEAP_SIZE in the default
file?

—
Reply to this email directly or view it on GitHub
#182 (comment)
.

[yasirbam]

I am having the same issue after deciding to restart elasticsearch that has been running for a couple of months! now I am not able to start it.
the start up service silently prints OK, when I run Sudo service elasticsearch start, but nothing in the logs
something must have upgraded while ES was running!
does Ubuntu update packages automatically similar to - Windows updates?