# Failed Upgrade - Graylog version? **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [May 4, 2017, 11:55pm UTC](https://community.graylog.org/t/failed-upgrade-graylog-version/1044 "2017-05-04T23:55:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![OlympiaLady](https://avatars.discourse-cdn.com/v4/letter/o/8491ac/32.png) [@OlympiaLady](https://community.graylog.org/u/OlympiaLady)\ **Post date:** [May 4, 2017, 11:55pm UTC](https://community.graylog.org/t/failed-upgrade-graylog-version/1044/1 "2017-05-04T23:55:10Z")
I am using Debian Jesse. My repository is set up as described in the Graylog documentation. A few weeks ago I upgraded my test instance of Graylog from v2.2.2+691b4b7 to v2.2.3+7adc951. I also updated my OS and elasticsearch. Everything went very smoothly. I just did a: aptitude update aptitude safe-upgrade Today I tried to update my production. Everything was the same including my graylog repository in my production. After the update, I noticed Graylog did not update, but everything else updated. I downloaded the latest respository: wget [https://packages.graylog2.org/repo/packages/graylog-2.3-repository\_latest.deb](https://packages.graylog2.org/repo/packages/graylog-2.3-repository_latest.deb) I noticed the directions in the documentation were for 2.2, but I just changed everything to 2.3. I then did another aptitute update/safe-upgrade. Everything upgraded with no error messages, and the services appeared to start. Nothing was listening (when viewed with netstat) however, and the error logs were not very helpful other than a message about a corrupted index rebuilding. I could not get the graylog web interface to respond. Elasticsearch was showing everything was healthy, however. I finally gave up and rolled back to a snapshot, but lost some messages. Does anyone know why an upgrade two weeks ago would be successful and today it would fail for virtually identical systems? I would like to try again, but I don’t want another failed upgrade. Thank you, Beth ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [May 5, 2017, 6:43am UTC](https://community.graylog.org/t/failed-upgrade-graylog-version/1044/2 "2017-05-05T06:43:31Z")
Hej @OlympiaLady without any Logfiles all we can do is ask the 🔮 regards Jan ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [May 5, 2017, 8:18am UTC](https://community.graylog.org/t/failed-upgrade-graylog-version/1044/3 "2017-05-05T08:18:31Z")
> [@OlympiaLady](#): > > Does anyone know why an upgrade two weeks ago would be successful and today it would fail for virtually identical systems? Graylog 2.3.0 hasn’t been released yet and there’s only a (broken) alpha out yet. If you plan to build a production setup, go with Graylog 2.2.x. ---
**Author:** ![OlympiaLady](https://avatars.discourse-cdn.com/v4/letter/o/8491ac/32.png) [@OlympiaLady](https://community.graylog.org/u/OlympiaLady)\ **Post date:** [May 5, 2017, 3:31pm UTC](https://community.graylog.org/t/failed-upgrade-graylog-version/1044/4 "2017-05-05T15:31:14Z")
Thank you as always Jochen! I have been getting the message to upgrade to 2.3.0. ![](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/1X/94af45b41e0d99cefcf429f1bf369a07cda482d8.png) Beth ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [May 5, 2017, 3:44pm UTC](https://community.graylog.org/t/failed-upgrade-graylog-version/1044/5 "2017-05-05T15:44:51Z")
As far as I see it says “Graylog 2.2.3”. 😉 And the message was “triggered a month ago”, so you can simply dismiss it by clicking on the [X] in the upper right corner of the notification.