# Dremio Upgrade 2.1 Issue

**URL:** <https://community.dremio.com/t/dremio-upgrade-2-1-issue/1774>\
**Category:** Uncategorized\
**Created:** [September 6, 2018, 12:45am UTC](https://community.dremio.com/t/dremio-upgrade-2-1-issue/1774 "2018-09-06T00:45:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![akikax](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@akikax](https://community.dremio.com/u/akikax)\
**Post date:** [September 6, 2018, 12:45am UTC](https://community.dremio.com/t/dremio-upgrade-2-1-issue/1774/1 "2018-09-06T00:45:50Z")

</div>

Hey Guys,

I just tried to upgrade my Dremio Cluster and unfortunately I am not able to provision again the workers.

I am attaching screenshot of the issue and error log.

[Dremio Upgrade 2.1 Issue.zip](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/1X/c4ab1f447be495a5e5f1bb120e8916836dbe2fb2.zip) (48.8 KB)

Upgrade details: CentOS, RPM, from 2.0.5 to 2.1.4

---

<div class="post-metadata">

**Author:** ![yufeldman](https://avatars.discourse-cdn.com/v4/letter/y/c77e96/32.png) [@yufeldman](https://community.dremio.com/u/yufeldman)\
**Post date:** [September 6, 2018, 2:05am UTC](https://community.dremio.com/t/dremio-upgrade-2-1-issue/1774/2 "2018-09-06T02:05:44Z")

</div>

I recommend you to take a look at RM and DremioDaemon YARN application to see what error does it show.

---

<div class="post-metadata">

**Author:** ![akikax](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@akikax](https://community.dremio.com/u/akikax)\
**Post date:** [September 6, 2018, 3:34am UTC](https://community.dremio.com/t/dremio-upgrade-2-1-issue/1774/3 "2018-09-06T03:34:06Z")

</div>

Okay I found the problem. The upgrade process didn’t seem to backup and restore properly my dremio-env file. from “/etc/dremio/dremio-env.rpmsave” back to “/etc/dremio/dremio-env.”; as a result, the coordinator node was using the vanilla and incorrect version of the file. After doing a manual rename everything seemed back to normal. Perhaps an issue with the upgrades scripts?

I am continue the testing of the upgrade, I’ll keep you posted guys…
