Failed to start ES 2.1.1 after upgrading to Ubuntu 15.10


#1

Hi everyone,

ES fails to start after updating to Ubuntu 15.10, any hints would be appreciated...
Was working fine before update.

● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since lun 2016-01-11 11:09:06 CET; 34s ago
     Docs: http://www.elastic.co
  Process: 2867 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -Des.pidfile=${PID_DIR}/elasticsearch.pid -Des.default.path.home=${ES_HOME} -Des.default.path.logs=${LOG_DIR} -Des.default.path.data=${DATA_DIR} -Des.default.path.conf=${CONF_DIR} (code=exited, status=1/FAILURE)
  Process: 2863 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
 Main PID: 2867 (code=exited, status=1/FAILURE)

ene 11 11:09:05 Pavilion systemd[1]: Stopped Elasticsearch.
ene 11 11:09:05 Pavilion systemd[1]: Starting Elasticsearch...
ene 11 11:09:05 Pavilion systemd[1]: Started Elasticsearch.
ene 11 11:09:06 Pavilion elasticsearch[2867]: Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x000000008...no=12)
ene 11 11:09:06 Pavilion systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
ene 11 11:09:06 Pavilion systemd[1]: elasticsearch.service: Unit entered failed state.
ene 11 11:09:06 Pavilion systemd[1]: elasticsearch.service: Failed with result 'exit-code'.

Java version 1.8.0_66-b17


(Mike Simos) #2

Hi,

You should check /var/log/elasticsearch/clustername.log and /var/log/messages for any error messages.


#3

Thanks Mike but no clue there. Guess is something about user permissions. Had to reinstall ES. Back to normal now.


(system) #4