# Maintenance Mode enabled after upgrade

**URL:** <https://discuss.elastic.co/t/maintenance-mode-enabled-after-upgrade/108125>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [November 17, 2017, 12:27pm UTC](https://discuss.elastic.co/t/maintenance-mode-enabled-after-upgrade/108125 "2017-11-17T12:27:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lafunamor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lafunamor/32/22571_2.png) [@Lafunamor](https://discuss.elastic.co/u/Lafunamor)\
**Post date:** [November 17, 2017, 12:27pm UTC](https://discuss.elastic.co/t/maintenance-mode-enabled-after-upgrade/108125/1 "2017-11-17T12:27:25Z")

</div>

Hi there

After upgrading my ECE installation from version 1.0.2 to 1.1.0 all allocator nodes which have clusters on them are in maintenance mode. Allocator nodes without any elasticsearch deployments aren't.  
Is this behavior by design or is there some missing "disable maintenance mode" step in the upgrade process. So far I was unable to find any mentioning of this in the documentation.

---

<div class="post-metadata">

**Author:** ![Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuri/32/52458_2.png) [@Yuri](https://discuss.elastic.co/u/Yuri)\
**Post date:** [November 20, 2017, 4:10pm UTC](https://discuss.elastic.co/t/maintenance-mode-enabled-after-upgrade/108125/2 "2017-11-20T16:10:48Z")

</div>

Hello,  
ECE upgrade does not switch allocator's maintenance mode. To help you troubleshoot the issue, I need to check logs of a host where one of the allocators went to the maintenance mode during upgrade. You can find logs in `host_storage_path` (default `/mnt/data/elastic`). Can you please send them to me via direct message? Everything in this directory would be helpful.

Thanks.

---

<div class="post-metadata">

**Author:** ![Lafunamor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lafunamor/32/22571_2.png) [@Lafunamor](https://discuss.elastic.co/u/Lafunamor)\
**Post date:** [November 20, 2017, 4:28pm UTC](https://discuss.elastic.co/t/maintenance-mode-enabled-after-upgrade/108125/3 "2017-11-20T16:28:05Z")

</div>

Hi @Yuri

Sorry for the wrong alert. I realized that I had an error in my scripts and this caused the maintenance mode to be enabled.

---

<div class="post-metadata">

**Author:** ![Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuri/32/52458_2.png) [@Yuri](https://discuss.elastic.co/u/Yuri)\
**Post date:** [November 20, 2017, 4:53pm UTC](https://discuss.elastic.co/t/maintenance-mode-enabled-after-upgrade/108125/4 "2017-11-20T16:53:00Z")

</div>

Thanks for letting me know!  
We have discovered an issue that is caused by the upgrade from 1.0.x to 1.1.0. It affects Kibana clusters that cannot find corresponding Elasticsearch cluster.  
There is a script that fixes the problem [fix-service-forwarder.sh](https://gist.github.com/yuri-tceretian/53e68dcd31ae761934d391d12fd814fd).  
I apologize for the inconvenience.

---

<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:** [December 4, 2017, 4:53pm UTC](https://discuss.elastic.co/t/maintenance-mode-enabled-after-upgrade/108125/5 "2017-12-04T16:53:17Z")

</div>

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