title: ElasticSearch Fails to Start on Ubuntu 16.04.3 - status=1 Failure
body: <p>The ElasticSearch 6.2.2 service on this Ubuntu 16.04.3 machine has been running fine for a few months.  I rebooted the machine today and found the ElasticSearch service had not started.  So I tried <code>sudo systemctl start elasticsearch.service</code>.  I was not given any error.  But I noticed it still hadn't started.</p>
  
  <p>Upon running <code>systemctl status elasticsearch</code> I get this:</p>
  
  <pre><code>`● elasticsearch.service - Elasticsearch
     Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/elasticsearch.service.d
             └─override.conf
     Active: inactive (dead) (Result: exit-code) since Tue 2018-09-18 02:35:58 UTC; 19min ago
       Docs: http://www.elastic.co
    Process: 14147 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
   Main PID: 14147 (code=exited, status=1/FAILURE)
  
  Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: elasticsearch.service: Unit entered failed state.
  Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: elasticsearch.service: Failed with result 'exit-code'.
  Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: elasticsearch.service: Service hold-off time over, scheduling restart.
  Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: Stopped Elasticsearch.
  Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: elasticsearch.service: Start request repeated too quickly.
  Sep 18 02:35:58 elastic-eu-vm-000 systemd[1]: Failed to start Elasticsearch.
  </code></pre>
  
  <p>The solution which seemed to help many people who couldn't start the ES service on Ubuntu found here (<a href="https://stackoverflow.com/questions/38674711/can-not-start-elasticsearch-as-a-service-in-ubuntu-16-04">Can not start elasticsearch as a service in ubuntu 16.04</a>), the one accepted as the answer, did not help me.</p>
  
  <p>This is a production machine so I hope someone can help!  Thanks!!</p>
  
  <p>EDIT 1 - after much pain trying to track down the log file, it's now at the following url per suggestion from @ArnavRay
  <a href="https://file.io/ASnEG4" rel="nofollow noreferrer">https://file.io/ASnEG4</a></p>