Debian elasticsearch.service: start operation timed out. Terminating

[Joel_wangolo]

I have a development machine that I use to develop production ready web apps. At first Elasticsearch worked very fine on my local development system, when developing the search of my Site. I stopped Elasticsearch because the rest of the work didn't need it.

But now am working on a new project that requires Elasticsearch but it's not starting. My main development system is Debian 10 fully updated and patched. But when I issue

systemctl start elasticsearch
I get this

Job for elasticsearch.service failed because a timeout was exceeded.
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.

When I run this
systemctl status elasticsearch.service

I get this
`
● elasticsearch.service - Elasticsearch
Loaded: loaded (/etc/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
Active: failed (Result: timeout) since Thu 2020-03-12 09:27:58 EAT; 17s ago
Docs: http://www.elastic.co
Process: 7593 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=143)
Main PID: 7593 (code=exited, status=143)

Mar 12 09:26:25 debian systemd[1]: Starting Elasticsearch...
Mar 12 09:26:26 debian elasticsearch[7593]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely>
Mar 12 09:27:55 debian systemd[1]: elasticsearch.service: start operation timed out. Terminating.
Mar 12 09:27:58 debian systemd[1]: elasticsearch.service: Failed with result 'timeout'.
Mar 12 09:27:58 debian systemd[1]: Failed to start Elasticsearch.

`

I have tried every possible solution including

TimeoutStopSec=900

But it's not working

SPECs
Debian: 10
RAM: 4gb

[Baris_Kiremitci (Barış Kiremitci)]

same error,
with ram 64 gb
debian

[jeroen1]

Same here, after manual upgrade (dpkg -i) to 7.6.1 in Ubuntu 16.04 LTS:

● elasticsearch.service - Elasticsearch
   Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/elasticsearch.service.d
           └─elasticsearch.conf
   Active: failed (Result: timeout) since Wed 2020-03-18 11:49:58 CET; 17s ago
     Docs: http://www.elastic.co
  Process: 25987 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=killed, signal=TERM)
 Main PID: 25987 (code=killed, signal=TERM)

Mar 18 11:48:26 <removed> systemd[1]: Starting Elasticsearch...
Mar 18 11:49:56 <removed> systemd[1]: elasticsearch.service: Start operation timed out. Terminating.
Mar 18 11:49:58 <removed> systemd[1]: Failed to start Elasticsearch.
Mar 18 11:49:58 <removed> systemd[1]: elasticsearch.service: Unit entered failed state.
Mar 18 11:49:58 <removed> systemd[1]: elasticsearch.service: Failed with result 'timeout'.

[rameshkr1994 (HadoopHelp)]

Hi @jeroen1 , @Baris_Kiremitci, @Joel_wangolo

````which Elasticsearch version you all are using?```

please also make sure about java compatibility with Elasticsearch version .

Thanks
HadoopHelp

[Baris_Kiremitci (Barış Kiremitci)]

I found solution from

https://blog.sleeplessbeastie.eu/2020/02/29/how-to-prevent-systemd-service-start-operation-from-timing-out/

Thanks,
Baris Kiremitci

[jeroen1]

Solution mentioned in post of Baris_Kiremitci works for me (timeout from 90 to 180s).

Open question: what's the reason that this issues occurs in 7.6.1? I'm running a static dataset on the same box this dataset was already running: so no data nor hardware changes. Only change: update to ES 7.6.1.