# Upgraded from 2.4 to 2.5, still running 2.4 after restart

**URL:** <https://community.graylog.org/t/upgraded-from-2-4-to-2-5-still-running-2-4-after-restart/7910>\
**Category:** Graylog Central (peer support)\
**Created:** [December 5, 2018, 2:39pm UTC](https://community.graylog.org/t/upgraded-from-2-4-to-2-5-still-running-2-4-after-restart/7910 "2018-12-05T14:39:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rhp](https://avatars.discourse-cdn.com/v4/letter/r/58956e/32.png) [@rhp](https://community.graylog.org/u/rhp)\
**Post date:** [December 5, 2018, 2:39pm UTC](https://community.graylog.org/t/upgraded-from-2-4-to-2-5-still-running-2-4-after-restart/7910/1 "2018-12-05T14:39:51Z")

</div>

Hi,

I just upgraded from 2.4 to 2.5 using the deb repository and upgrade docs. Everything seemed to go fine, but when I either issue a systemctl restart or reboot the server, it still comes back up running the older 2.4.6 version. How can I get it to switch over to 2.5?

Thanks!

---

<div class="post-metadata">

**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:** [December 5, 2018, 2:49pm UTC](https://community.graylog.org/t/upgraded-from-2-4-to-2-5-still-running-2-4-after-restart/7910/2 "2018-12-05T14:49:48Z")

</div>

He

did you reload your browser? It can happen that if you leave your browser window open during the update and the reboot and did not do a “full reload” of the page it looks like you have not updated.

What can you see in your Graylog `server.log`? Graylog is writing it’s version to the logfile.

Jan

---

<div class="post-metadata">

**Author:** ![rhp](https://avatars.discourse-cdn.com/v4/letter/r/58956e/32.png) [@rhp](https://community.graylog.org/u/rhp)\
**Post date:** [December 5, 2018, 2:56pm UTC](https://community.graylog.org/t/upgraded-from-2-4-to-2-5-still-running-2-4-after-restart/7910/3 "2018-12-05T14:56:13Z")

</div>

Hi Jan,

Reloading my browser did it, I should’ve tried that before posting. Thank you!

---

<div class="post-metadata">

**Author:** ![prakasha](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/prakasha/32/3422_2.png) [@prakasha](https://community.graylog.org/u/prakasha)\
**Post date:** [December 6, 2018, 7:30am UTC](https://community.graylog.org/t/upgraded-from-2-4-to-2-5-still-running-2-4-after-restart/7910/4 "2018-12-06T07:30:14Z")

</div>

Dear @rhp, Could you please check the /usr/share/graylog-server/plugin/ folders. Maybe we can see if the graylog has been updated properly then you will get the updated plugins like graylog-plugin-threatintel-2.5.0.jar. This is also one option from CLI.

 ![comparison%20path](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/e/e84d891bc1ac73a8d880397ca6ae02d06c1bb246.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [December 20, 2018, 7:30am UTC](https://community.graylog.org/t/upgraded-from-2-4-to-2-5-still-running-2-4-after-restart/7910/5 "2018-12-20T07:30:15Z")

</div>

Closed on December 20, 2018, 7:30am UTC

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