# You are running an outdated Graylog version (Space Moose)

**URL:** <https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212>\
**Category:** Graylog Central (peer support)\
**Created:** [May 1, 2019, 6:28pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212 "2019-05-01T18:28:10Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![j.cudilla](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@j.cudilla](https://community.graylog.org/u/j.cudilla)\
**Post date:** [May 1, 2019, 6:28pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/1 "2019-05-01T18:28:10Z")

</div>

== Web UI says ==  
You are running an outdated Graylog version  
The most recent stable Graylog version is 3.0.1 (Space Moose) release at 2019-0401T00:00:00:000Z

But our server is already on 3.0.1-2 coz it’s our initial build using the latest version:

== rpm -qa|grep graylog ==  
graylog-server-3.0.1-2.noarch  
graylog-3.0-repository-1-6.noarch

---

<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:** [May 1, 2019, 8:47pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/2 "2019-05-01T20:47:43Z")

</div>

did you restart the server after the rpm upgrade?

---

<div class="post-metadata">

**Author:** ![j.cudilla](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@j.cudilla](https://community.graylog.org/u/j.cudilla)\
**Post date:** [May 1, 2019, 9:27pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/3 "2019-05-01T21:27:04Z")

</div>

it’s not an upgrade but an initial setup from this latest version and yes we restarted the service several times

---

<div class="post-metadata">

**Author:** ![PaulRegan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/paulregan/32/4380_2.png) [@PaulRegan](https://community.graylog.org/u/PaulRegan)\
**Post date:** [May 2, 2019, 9:11am UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/4 "2019-05-02T09:11:17Z")

</div>

Same issue. 3.0 appliance which we upgraded yesterday as per docs. Now have the same banner message in the GUI:

The most recent stable Graylog version is 3.0.1 (Space Moose) release at 2019-0401T00:00:00:000Z

ubuntu@graylog:~$ sudo apt list | grep graylog

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

graylog-3.0-repository/stable,stable,now 1-6 all [installed]  
graylog-enterprise-integrations-plugins/stable,stable 3.0.1-2 all  
graylog-enterprise-plugins/stable,stable,now 3.0.1-2 all [installed]  
graylog-integrations-plugins/stable,stable 3.0.1-2 all  
graylog-server/stable,stable,now 3.0.1-2 all [installed]

---

<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:** [May 2, 2019, 8:15pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/5 "2019-05-02T20:15:29Z")

</div>

does that message have a “x” in the left right? that you can remove that message?

---

<div class="post-metadata">

**Author:** ![j.cudilla](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@j.cudilla](https://community.graylog.org/u/j.cudilla)\
**Post date:** [May 2, 2019, 8:20pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/6 "2019-05-02T20:20:54Z")

</div>

Yes there is. The “x” icon is for deleting the notification which we did (for example yesterday but the same notification came back today morning)

---

<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:** [May 2, 2019, 8:30pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/7 "2019-05-02T20:30:07Z")

</div>

what is the current time on your system?

---

<div class="post-metadata">

**Author:** ![j.cudilla](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@j.cudilla](https://community.graylog.org/u/j.cudilla)\
**Post date:** [May 2, 2019, 8:34pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/8 "2019-05-02T20:34:57Z")

</div>

== timedatectl ;date ==  
Local time: Thu 2019-05-02 13:33:22 PDT  
Universal time: Thu 2019-05-02 20:33:22 UTC  
RTC time: Thu 2019-05-02 20:33:22  
Time zone: America/Los\_Angeles (PDT, -0700)  
NTP enabled: yes  
NTP synchronized: yes  
RTC in local TZ: no  
DST active: yes  
Last DST change: DST began at  
Sun 2019-03-10 01:59:59 PST  
Sun 2019-03-10 03:00:00 PDT  
Next DST change: DST ends (the clock jumps one hour backwards) at  
Sun 2019-11-03 01:59:59 PDT  
Sun 2019-11-03 01:00:00 PST  
Thu May 2 13:33:22 PDT 2019

---

<div class="post-metadata">

**Author:** ![kay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/kay/32/7_2.png) [@kay](https://community.graylog.org/u/kay)\
**Post date:** [May 3, 2019, 9:20am UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/9 "2019-05-03T09:20:34Z")

</div>

Hi!

Could you please enable debug logging for the version check to help us figure out what is happening here?  
You’d need to supply a log4j configuration to the master node (e.g. taking the default file from [https://github.com/Graylog2/graylog2-server/blob/3.0/graylog2-server/src/main/resources/log4j2.xml](https://github.com/Graylog2/graylog2-server/blob/3.0/graylog2-server/src/main/resources/log4j2.xml) ) as explained at [http://docs.graylog.org/en/3.0/pages/installation/manual\_setup.html?highlight=logging#supplying-external-logging-configuration](http://docs.graylog.org/en/3.0/pages/installation/manual_setup.html?highlight=logging#supplying-external-logging-configuration) and change the line [https://github.com/Graylog2/graylog2-server/blob/3.0/graylog2-server/src/main/resources/log4j2.xml#L20](https://github.com/Graylog2/graylog2-server/blob/3.0/graylog2-server/src/main/resources/log4j2.xml#L20) from `off` to `debug` and restart the master node.

After about 5 minutes there should be information in the server log file about the performed version check. This check only runs on the configured master node and you only need to make the change there.

Thanks!

---

<div class="post-metadata">

**Author:** ![PaulRegan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/paulregan/32/4380_2.png) [@PaulRegan](https://community.graylog.org/u/PaulRegan)\
**Post date:** [May 8, 2019, 12:36pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/10 "2019-05-08T12:36:46Z")

</div>

Just for the chain. My message cleared after a couple of restarts.

---

<div class="post-metadata">

**Author:** ![j.cudilla](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@j.cudilla](https://community.graylog.org/u/j.cudilla)\
**Post date:** [May 8, 2019, 8:36pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/11 "2019-05-08T20:36:18Z")

</div>

This is what the log says using the debug option:

== /var/log/graylog-server/server.log ==  
2019-05-08T13:25:05.912-07:00 DEBUG [VersionCheckThread] Version check reports current version: 3.0.1 (Space Moose) released at 2019-04-01T00:00:00.000Z  
2019-05-08T13:25:05.913-07:00 DEBUG [VersionCheckThread] Reported version is not higher than ours (3.0.2+1686930).

Few mins after bouncing the service, the annoying notification is also gone in the UI. Consider this resolved if you don’t hear back from us in a day or two, we’ll observe for now.

---

<div class="post-metadata">

**Author:** ![j.cudilla](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@j.cudilla](https://community.graylog.org/u/j.cudilla)\
**Post date:** [May 10, 2019, 8:08pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/12 "2019-05-10T20:08:53Z")

</div>

we have two separate instances and both worked after a quick service restart, no more annoying false notification. Can’t believe I missed that but thanks…

---

<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:** [May 24, 2019, 8:08pm UTC](https://community.graylog.org/t/you-are-running-an-outdated-graylog-version-space-moose/10212/13 "2019-05-24T20:08:56Z")

</div>

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