Elasticsearch 5.6.0 not starting (no logs in logfiles made)


(Luvpreet Singh) #1

I am having trouble starting elasticsearch.

I upgraded it to 5.6.0 2 days ago.

Today, I stopped it, and installed searchguard for 5.6.0.

Now, when I started elasticsearch, it is not getting started.

No logs are being made in the / var/log/elasticsearch/elasticsearch.log

monitoring-server@monitoring-server:/var/log/elasticsearch$ sudo service elasticsearch status
● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2017-09-18 07:40:58 UTC; 1h 0min ago
     Docs: http://www.elastic.co
  Process: 30809 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG_DIR} -E
  Process: 30796 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
 Main PID: 30809 (code=exited, status=1/FAILURE)

Sep 18 07:40:58 monitoring-server elasticsearch[30809]:         at org.elasticsearch.node.InternalSettingsPreparer.prepareEnvironment(InternalS
Sep 18 07:40:58 monitoring-server elasticsearch[30809]:         at org.elasticsearch.cli.EnvironmentAwareCommand.createEnv(EnvironmentAwareComm
Sep 18 07:40:58 monitoring-server elasticsearch[30809]:         at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareComman
Sep 18 07:40:58 monitoring-server elasticsearch[30809]:         at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:134)
Sep 18 07:40:58 monitoring-server elasticsearch[30809]:         at org.elasticsearch.cli.Command.main(Command.java:90)
Sep 18 07:40:58 monitoring-server elasticsearch[30809]:         at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91)
Sep 18 07:40:58 monitoring-server elasticsearch[30809]:         at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84)
Sep 18 07:40:58 monitoring-server systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
Sep 18 07:40:58 monitoring-server systemd[1]: elasticsearch.service: Unit entered failed state.
Sep 18 07:40:58 monitoring-server systemd[1]: elasticsearch.service: Failed with result 'exit-code'.

What is the problem here and how to solve it ?


(Mark Walkom) #2

Does it start if you remove the plugin?


(Luvpreet Singh) #3

yes, it did start when I remove the plugin.


(Mark Walkom) #4

Then it sounds like a problem with that plugin, you may want to contact the author of it for support.


(system) #5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.