Version Mismatch Warning After Updating to Graylog 6.2.2

Graylog Central (peer support)
,
1

Body: Hi everyone,

I’m experiencing an issue with my Graylog setup after updating to version 6.2.2. Despite updating both the Graylog server and Data Node to the latest version, I still receive the following warnings:

Outdated Version Warning:

You are running an outdated Graylog version (triggered 2 days ago). The most recent stable Graylog version is 6.2.2 (Noir) released at 2025-05-07T00:00:00.000Z. See what’s new in the Open and Operations changelogs!

Data Node Version Mismatch:

You are running at least one Data Node which runs on a different version than your Graylog server. While this might not impose a problem, it is recommended to run Graylog server and Data Nodes on the same version.

Here are the details of my setup:

Graylog Server: graylog/graylog:6.2.2
Data Node: graylog/graylog-datanode:6.2.2
MongoDB: mongo:6.0
All containers are running in the same Docker network (docker-install_graylog). Here are the relevant parts of my docker-compose.yml:

services:
  mongodb:
    image: "mongo:6.0"
    networks:
      - graylog

  datanode:
    image: "graylog/graylog-datanode:6.2.2"
    networks:
      - graylog

  graylog:
    image: "graylog/graylog:6.2.2"
    networks:
      - graylog

I have verified that no other containers are running and that all containers are in the same network. Here are the network details:

Graylog Server IP: 172.18.0.3
Data Node IP: 172.18.0.2
MongoDB IP: 172.18.0.1
Despite this, I still receive the version mismatch warning. Any help or suggestions on how to resolve this issue would be greatly appreciated!

Thank you!

2

Hey @ustaub,
I suspect that your docker-compose setup is actually not upgraded, even if the yaml file contains the latest version numbers.

You should be able to verify that in logs of the server or data node.

Have you triggered docker compose pull after you replaced versions in the yaml file?

1 Like
3

Thanks for your help, the container has the both containers has the same version number.
Solution was simpler as i expect, i clear the massage over x, then they was dissapeard.

1 Like