# Upgrade fleet server to 7.16.2 - failing **URL:** \ **Category:** Endpoint Security\ **Tags:** fleet\ **Created:** [January 20, 2022, 1:59am UTC](https://discuss.elastic.co/t/upgrade-fleet-server-to-7-16-2-failing/294889 "2022-01-20T01:59:37Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Ross\_Wakelin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross_wakelin/32/100578_2.png) [@Ross\_Wakelin](https://discuss.elastic.co/u/Ross_Wakelin)\ **Post date:** [January 20, 2022, 1:59am UTC](https://discuss.elastic.co/t/upgrade-fleet-server-to-7-16-2-failing/294889/1 "2022-01-20T01:59:37Z")
We have been running fleet for a couple of months, starting with a stack running 7.15.0. We have upgraded our stack (including Kibana) to 7.16.2, and now want to upgrade our elastic-agents. On the fleet console, our agents are showing as "Upgrade available" but the fleet server is not. If we try to upgrade a remote agent, it says its going to upgrade to 7.16.2, but the upgrade agent never reconnects to the fleet server. If I try and upgrade the fleet server from the UI, it says its going to upgrade to 7.16.2, but then fails, with the really helpful error message that says upgrade failed. Is there some special sauce, or magic incantation required before I can upgrade a fleet server, and then the remote agents? Thanks Ross ---
**Author:** ![joshdover](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshdover/32/42020_2.png) [@joshdover](https://discuss.elastic.co/u/joshdover)\ **Post date:** [January 20, 2022, 10:51am UTC](https://discuss.elastic.co/t/upgrade-fleet-server-to-7-16-2-failing/294889/2 "2022-01-20T10:51:15Z")
Hi Ross, Sorry to hear you're having trouble. Just want to note that the remote upgrade feature is still in beta so we still have some improvements to make (like [better error messages](https://github.com/elastic/beats/issues/29407)), but in general it should work. You will need to upgrade Fleet Server before upgrading the other Agents. One thing I'd suggest is turn on verbose Agent logging on the Agent that is running Fleet Server, and then attempting the upgrade again. Then you should be able to see more detailed information about why the upgrade may be failing in the Agent logs for your Fleet Server agent. You can do this by changing the log level drop down in the bottom right corner of the Agent detail view: ![Screen Shot 2022-01-20 at 11.48.39](https://us1.discourse-cdn.com/elastic/original/3X/4/f/4f2c98824e2541e89104af3bddc070d3b2468f2c.png) Feel free to post whatever you logs you're getting during the upgrade failure and we'll try to help as we can. ---
**Author:** ![Ross\_Wakelin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross_wakelin/32/100578_2.png) [@Ross\_Wakelin](https://discuss.elastic.co/u/Ross_Wakelin)\ **Post date:** [January 20, 2022, 10:06pm UTC](https://discuss.elastic.co/t/upgrade-fleet-server-to-7-16-2-failing/294889/3 "2022-01-20T22:06:27Z")
Thanks for the response. After trying to upgrade with debug turned on, this is the first line of the log, and it says it all.... `2022-01-21T09:03:23.374+1300 DEBUG upgrade/rollback.go:103 agent is not upgradable, not starting watcher ` This is the UI view: ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/4/a43244796d9519bb9f5236e3c69bfd566a7cb7d1.png) ![EA1](https://us1.discourse-cdn.com/elastic/original/3X/7/8/786b49ef37df5ca0bd5ec86898ecc0c410d6f359.png) ---
**Author:** ![joshdover](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joshdover/32/42020_2.png) [@joshdover](https://discuss.elastic.co/u/joshdover)\ **Post date:** [January 24, 2022, 12:02pm UTC](https://discuss.elastic.co/t/upgrade-fleet-server-to-7-16-2-failing/294889/4 "2022-01-24T12:02:20Z")
Thanks for posting the error message. Depending on how the Agent is installed, it may not eligible for remote upgrades. [See the docs](https://www.elastic.co/guide/en/fleet/master/upgrade-elastic-agent.html#upgrade-elastic-agent) for more information, but in general, remote upgrades are not supported for Agents that are installed via DEB or RPM packages, or Docker containers since those are managed externally. If you'd like to be able remote upgrade an Agent, we recommend installing via our binary tar.gz distributable directly. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 21, 2022, 12:02pm UTC](https://discuss.elastic.co/t/upgrade-fleet-server-to-7-16-2-failing/294889/5 "2022-02-21T12:02:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.