Node cannot be found among active nodes

Graylog Central (peer support)
1

Hello,
I’ve updated Graylog 5.2.9 to 6.1.1.
I’ve got an error on some api endpoints (so some functionalities doesn’t work):
Node aaa… cannot be found among active nodes.
The configuration points to /etc/graylog/server/node-id. This file exists, is readalbe by the graylog user and contains the same value as the error.
When I curl http://:9000/api it’s also the same node_id.
I don’t understand why it can’t found the node.
(There is no cluster, it’s just one Graylog server)

2

Hello @frantz,

Did you incrementally update to 6.0 and then 6.1?

What is the full error you see in the logs?

If you go to System/Nodes and click through to the node information, does it display?

3

I updated directly from 5.1 to 6.1, that’s maybe the issue.
I’ll revert the snapshot and try to update to 6.0 before 6.1.
If it doesn’t work I’ll add the full logs.
Node is not displayed in System/Nodes.

4

Typically this means the missing graylog node either cannot connect to its mongo db or cannot properly update its state in MongoDB collection nodes

Do you see a record for your missing node in nodes and if the last_seen value is up-to-date?

you can use something like:

mongosh <mongo_uri_from_server_conf> --eval "db.nodes.find()"

Should return something like:

[
  {
    _id: ObjectId('<oid>'),
    node_id: '<nodeid>',
    hostname: '<hostname>',
    is_leader: true,
    last_seen: Timestamp({ t: 1730738346, i: 1 }),
    transport_address: 'https://<hostname>:443/api/'
  }
]
5

The nodes collection seems fine, the node_id is the same as other places, hostname and transport_address are good, is_leader is true, last_seen is now.

6

I’ve reverted the snapshot and the issue was already here in 5.1.
I’ve deleted the VM and installed a 6.1 from scratch.
Thanks for trying to help me.

1 Like
7

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