# Elasticsearch fails to start after upgrade to 1.4.4

**URL:** <https://discuss.elastic.co/t/elasticsearch-fails-to-start-after-upgrade-to-1-4-4/22322>\
**Category:** Elasticsearch\
**Created:** [February 23, 2015, 7:58am UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-after-upgrade-to-1-4-4/22322 "2015-02-23T07:58:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Feinstein\_2](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@Daniel\_Feinstein\_2](https://discuss.elastic.co/u/Daniel_Feinstein_2)\
**Post date:** [February 23, 2015, 7:58am UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-after-upgrade-to-1-4-4/22322/1 "2015-02-23T07:58:02Z")

</div>

Hi,

I have an instance of Elasticsearch 1.4.1 on AWS, Amazon Linux OS. The  
version has been installed with yum. I try to upgrade the version of  
elasticsearch to the latest 1.4.4.

Since the installation is not production yet downtime is not an issue. So I  
do not need to do a rolling upgrade but could shutdown the service and run  
yum:

```
   *sudo yum update elasticsearch-1.4.1-1.noarch*

```

The command was executed with no errors. However when I start the  
elasticsearch service it fails with the following error:

_[ec2-user]$ {1.4.1}: pid Failed ..._  
_- FileNotFoundException[/var/run/elasticsearch/elasticsearch.pid  
(Permission denied)]_  
_java.io.FileNotFoundException: /var/run/elasticsearch/elasticsearch.pid  
(Permission denied)_

- 

```
   at java.io.FileOutputStream.open(Native Method)*

```

- 

```
   at java.io.FileOutputStream.<init>(FileOutputStream.java:221)*

```

- 

```
   at java.io.FileOutputStream.<init>(FileOutputStream.java:171)*

```

- 

```
   at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:156)*

```

- 

```
   at 

```

org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32)\*

After this failure I have tried to downgrade the version of elasticsearch  
to 1.4.1 by:

```
  *sudo yum downgrade elasticsearch-1.4.1-1.noarch*

```

but it did not help and the error is still there.

Any idea how to fix the installation?

Thanks

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1fdab1cb-784a-405d-85c2-f07c7fca0526%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1fdab1cb-784a-405d-85c2-f07c7fca0526%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Daniel\_Feinstein\_2](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@Daniel\_Feinstein\_2](https://discuss.elastic.co/u/Daniel_Feinstein_2)\
**Post date:** [February 23, 2015, 9:55am UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-after-upgrade-to-1-4-4/22322/2 "2015-02-23T09:55:39Z")

</div>

The problem was in permissions on /var/run/elasticsearch folder. The folder  
is owned by elasticsearch user while service has been running as root. yum  
installation has removed non-owner write permissions on the folder and  
hence the process was not able to create the pid file.

On Monday, February 23, 2015 at 9:58:02 AM UTC+2, Daniel Feinstein wrote:

> Hi,
> 
> I have an instance of Elasticsearch 1.4.1 on AWS, Amazon Linux OS. The  
> version has been installed with yum. I try to upgrade the version of  
> elasticsearch to the latest 1.4.4.
> 
> Since the installation is not production yet downtime is not an issue. So  
> I do not need to do a rolling upgrade but could shutdown the service and  
> run yum:
> 
> ```
> *sudo yum update elasticsearch-1.4.1-1.noarch*
> 
> ```
> 
> The command was executed with no errors. However when I start the  
> elasticsearch service it fails with the following error:
> 
> _[ec2-user]$ {1.4.1}: pid Failed ..._  
> _- FileNotFoundException[/var/run/elasticsearch/elasticsearch.pid  
> (Permission denied)]_  
> _java.io.FileNotFoundException: /var/run/elasticsearch/elasticsearch.pid  
> (Permission denied)_
> 
> - 
> 
> ```
> at java.io.FileOutputStream.open(Native Method)*
> 
> ```
> 
> - 
> 
> ```
> at java.io.FileOutputStream.<init>(FileOutputStream.java:221)*
> 
> ```
> 
> - 
> 
> ```
> at java.io.FileOutputStream.<init>(FileOutputStream.java:171)*
> 
> ```
> 
> - 
> 
> ```
> at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:156)*
> 
> ```
> 
> - 
> 
> ```
> at 
> 
> ```
> 
> org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32)\*
> 
> After this failure I have tried to downgrade the version of elasticsearch  
> to 1.4.1 by:
> 
> ```
> *sudo yum downgrade elasticsearch-1.4.1-1.noarch*
> 
> ```
> 
> but it did not help and the error is still there.
> 
> Any idea how to fix the installation?
> 
> Thanks

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d0ba25a1-8edf-4d9a-8aae-085ec400a329%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d0ba25a1-8edf-4d9a-8aae-085ec400a329%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 12:30am UTC](https://discuss.elastic.co/t/elasticsearch-fails-to-start-after-upgrade-to-1-4-4/22322/3 "2017-07-06T00:30:51Z")

</div>


