# Get "elasticesearch conflicts with elasticsearch-oss-0:6.6.1-1.noarch" during upgrade

**URL:** <https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701>\
**Category:** Elasticsearch\
**Created:** [March 18, 2019, 2:44am UTC](https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701 "2019-03-18T02:44:42Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_Zhang1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_zhang1/32/42200_2.png) [@John\_Zhang1](https://discuss.elastic.co/u/John_Zhang1)\
**Post date:** [March 18, 2019, 2:44am UTC](https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701/1 "2019-03-18T02:44:43Z")

</div>

Dears, I am new to ELK and just take over from another colleague.

I need to upgrade current Elasticsearch 6.2.3 to 6.6.1, and because of license limitation, have to use the opensource version. As the guide [https://www.elastic.co/guide/en/elasticsearch/reference/6.6/rpm.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.6/rpm.html), I stopped the service, and then run rpm command to install, but got errors:  
**[root@vagrant-elk-6 tmp]# rpm --install elasticsearch-oss-6.6.1.rpm**  
**error: Failed dependencies:**  
\*\* elasticsearch conflicts with elasticsearch-oss-0:6.6.1-1.noarch\*\*

I did some google search but can not find any clue, could you please help throw me some light? Thanks a lot!

The current installed Elasticsearch:  
[root@vagrant-elk-6 tmp]# curl -X GET "localhost:9200"  
{  
"name" : "A88CHvn",  
"cluster\_name" : "elasticsearch",  
"cluster\_uuid" : "YHA62fqkQiCd4g2IV32\_OQ",  
"version" : {  
"number" : "6.2.4",  
"build\_hash" : "ccec39f",  
"build\_date" : "2018-04-12T20:37:28.497551Z",  
"build\_snapshot" : false,  
"lucene\_version" : "7.2.1",  
"minimum\_wire\_compatibility\_version" : "5.6.0",  
"minimum\_index\_compatibility\_version" : "5.0.0"  
},  
"tagline" : "You Know, for Search"  
}

Java installed:  
[root@vagrant-elk-6 tmp]# java -version  
openjdk version "1.8.0\_191"  
OpenJDK Runtime Environment (build 1.8.0\_191-b12)  
OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 18, 2019, 2:52am UTC](https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701/2 "2019-03-18T02:52:14Z")

</div>

> [@John\_Zhang1](#):
>
> because of license limitation

Which limitation is that?

> [@John\_Zhang1](#):
>
> As the guide [Install Elasticsearch with RPM | Elasticsearch Guide [6.6] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/6.6/rpm.html), I stopped the service, and then run rpm command to install, but got errors:

What does `rpm -qi|grep -i elasticsearch` show?

---

<div class="post-metadata">

**Author:** ![John\_Zhang1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_zhang1/32/42200_2.png) [@John\_Zhang1](https://discuss.elastic.co/u/John_Zhang1)\
**Post date:** [March 18, 2019, 3:08am UTC](https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701/3 "2019-03-18T03:08:14Z")

</div>

@warkolm, thanks!  
currently can only use Apache license version, can not use the new Elastic license by now.

Here is the detailed info of installed version  
[root@vagrant-elk-6 tmp]# rpm -qi elasticsearch  
Name : elasticsearch  
Epoch : 0  
Version : 6.2.4  
Release : 1  
Architecture: noarch  
Install Date: Fri 09 Nov 2018 12:52:25 AM UTC  
Group : Application/Internet  
Size : 32278478  
License : 2009  
Signature : RSA/SHA512, Thu 12 Apr 2018 10:44:25 PM UTC, Key ID d27d666cd88e42b4  
Source RPM : elasticsearch-6.2.4-1-src.rpm  
Build Date : Thu 12 Apr 2018 08:39:15 PM UTC  
Build Host : packer-virtualbox-iso-1522340558  
Relocations : /usr  
Packager : Elasticsearch  
Vendor : Elasticsearch  
URL : [https://www.elastic.co/](https://www.elastic.co/)  
Summary : Elasticsearch is a distributed RESTful search engine built for the cloud. Reference documentation can be found at [https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html) and the 'Elasticsearch: The Definitive Guide' book can be found at [https://www.elastic.co/guide/en/elasticsearch/guide/current/index.html](https://www.elastic.co/guide/en/elasticsearch/guide/current/index.html)  
Description :  
Elasticsearch subproject :distribution:rpm

and here is the verbose info during install:  
[root@vagrant-elk-6 tmp]# rpm -ivv elasticsearch-oss-6.6.1.rpm  
D: ============== elasticsearch-oss-6.6.1.rpm  
D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/_.key  
D: couldn't find any keys in /var/lib/rpm/pubkeys/_.key  
D: loading keyring from rpmdb  
D: opening db environment /var/lib/rpm cdb:0x401  
D: opening db index /var/lib/rpm/Packages 0x400 mode=0x0  
D: locked db index /var/lib/rpm/Packages  
D: opening db index /var/lib/rpm/Name 0x400 mode=0x0  
D: read h# 307 Header SHA1 digest: OK (489efff35e604042709daf46fb78611fe90a75aa)  
D: added key gpg-pubkey-f4a80eb5-53a7ff4b to keyring  
D: read h# 399 Header SHA1 digest: OK (7607620a7fc71d534fe59a60dece8de02703e63c)  
D: added key gpg-pubkey-d88e42b4-52371eca to keyring  
D: Using legacy gpg-pubkey(s) from rpmdb  
D: Expected size: 34420403 = lead(96)+sigs(784)+pad(0)+data(34419523)  
D: Actual size: 34420403  
D: elasticsearch-oss-6.6.1.rpm: Header V4 RSA/SHA512 Signature, key ID d88e42b4: OK  
D: added binary package [0]  
D: found 0 source and 1 binary packages  
D: opening db index /var/lib/rpm/Conflictname 0x400 mode=0x0  
D: ========== +++ elasticsearch-oss-0:6.6.1-1 noarch/linux 0x0  
D: Requires: rpmlib(VersionedDependencies) \<= 3.0.3-1 YES (rpmlib provides)  
D: Requires: rpmlib(CompressedFileNames) \<= 3.0.4-1 YES (rpmlib provides)  
D: Requires: rpmlib(PayloadFilesHavePrefix) \<= 4.0-1 YES (rpmlib provides)  
D: opening db index /var/lib/rpm/Basenames 0x400 mode=0x0  
D: read h# 8 Header V3 RSA/SHA256 Signature, key ID f4a80eb5: OK  
D: Requires: /bin/bash YES (db files)  
D: opening db index /var/lib/rpm/Providename 0x400 mode=0x0  
D: read h# 44 Header V3 RSA/SHA256 Signature, key ID f4a80eb5: OK  
D: Requires: coreutils YES (db provides)  
D: read h# 387 Header V4 RSA/SHA512 Signature, key ID d88e42b4: OK  
D: Conflicts: elasticsearch YES (db provides)  
D: opening db index /var/lib/rpm/Obsoletename 0x400 mode=0x0  
error: Failed dependencies:  
elasticsearch conflicts with elasticsearch-oss-0:6.6.1-1.noarch  
D: closed db index /var/lib/rpm/Obsoletename  
D: closed db index /var/lib/rpm/Conflictname  
D: closed db index /var/lib/rpm/Providename  
D: closed db index /var/lib/rpm/Basenames  
D: closed db index /var/lib/rpm/Name  
D: closed db index /var/lib/rpm/Packages  
D: closed db environment /var/lib/rpm

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 18, 2019, 3:09am UTC](https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701/4 "2019-03-18T03:09:23Z")

</div>

You will likely need to remove that existing package and then install the one you want.

---

<div class="post-metadata">

**Author:** ![John\_Zhang1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_zhang1/32/42200_2.png) [@John\_Zhang1](https://discuss.elastic.co/u/John_Zhang1)\
**Post date:** [March 18, 2019, 3:21am UTC](https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701/5 "2019-03-18T03:21:24Z")

</div>

I had tried to run rpm -U to upgrade, resulted with same error.

To remove existing package with rpm -e, are the existing data and configuration files still there? need to keep the data and config, but upgrade the Elasticsearch version only....

thanks!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 18, 2019, 3:24am UTC](https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701/6 "2019-03-18T03:24:58Z")

</div>

I think that is the way it works, it will only remove the config and data if you use the purge option.

But I would check the documentation for `rpm` to be sure.

---

<div class="post-metadata">

**Author:** ![John\_Zhang1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john_zhang1/32/42200_2.png) [@John\_Zhang1](https://discuss.elastic.co/u/John_Zhang1)\
**Post date:** [March 18, 2019, 3:38am UTC](https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701/7 "2019-03-18T03:38:44Z")

</div>

@warkolm, Thanks very much for your kind and quick help!  
I did rpm -e, and then rpm -i, it seems working. I can still see the data in Kibana.  
One thing is that it will delete /etc/elasticsearch and keep a copy of elasticsearch.yml.rpmsave, but jvm.options and log4j2.properties are deleted, probably because I did not change them.

Thanks again!

---

<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:** [April 15, 2019, 3:38am UTC](https://discuss.elastic.co/t/get-elasticesearch-conflicts-with-elasticsearch-oss-0-6-6-1-1-noarch-during-upgrade/172701/8 "2019-04-15T03:38:44Z")

</div>

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