The master node cannot join the cluster

Graylog Central (peer support)
1

Hello. I have a cluster of 2 graylog nodes (1 master node and one slave node), a replica of monga was made on these 2 servers, and an elastic cluster of 3 nodes. The master node does not join the cluster, it gives this error in the logs:

2021-07-14T09:03:04.412Z ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-14T09:03:04.702Z ERROR [EnterpriseJobSchedulerConfig] Couldn't find current node <54f41dcd-5125-4677-a4bf-fa2261d05eb3> in the database
org.graylog2.cluster.NodeNotFoundException: Unable to find node 54f41dcd-5125-4677-a4bf-fa2261d05eb3
        at org.graylog2.cluster.NodeServiceImpl.byNodeId(NodeServiceImpl.java:76) ~[graylog.jar:?]
        at org.graylog2.cluster.NodeServiceImpl.byNodeId(NodeServiceImpl.java:84) ~[graylog.jar:?]
        at org.graylog.plugins.scheduler.EnterpriseJobSchedulerConfig$1.load(EnterpriseJobSchedulerConfig.java:46) [graylog-plugin-enterprise-4.1.0.jar:?]
        at org.graylog.plugins.scheduler.EnterpriseJobSchedulerConfig$1.load(EnterpriseJobSchedulerConfig.java:39) [graylog-plugin-enterprise-4.1.0.jar:?]
        at com.google.common.cache.CacheLoader.reload(CacheLoader.java:100) [graylog.jar:?]
        at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3532) [graylog.jar:?]
        at com.google.common.cache.LocalCache$Segment.loadAsync(LocalCache.java:2287) [graylog.jar:?]
        at com.google.common.cache.LocalCache$Segment.refresh(LocalCache.java:2360) [graylog.jar:?]
        at com.google.common.cache.LocalCache$Segment.scheduleRefresh(LocalCache.java:2338) [graylog.jar:?]
        at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2035) [graylog.jar:?]
        at com.google.common.cache.LocalCache.get(LocalCache.java:3951) [graylog.jar:?]
        at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3974) [graylog.jar:?]
        at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4958) [graylog.jar:?]
        at org.graylog.plugins.scheduler.EnterpriseJobSchedulerConfig.canExecute(EnterpriseJobSchedulerConfig.java:73) [graylog-plugin-enterprise-4.1.0.jar:?]
        at org.graylog.scheduler.JobSchedulerService.run(JobSchedulerService.java:92) [graylog.jar:?]
        at com.google.common.util.concurrent.AbstractExecutionThreadService$1$2.run(AbstractExecutionThreadService.java:66) [graylog.jar:?]
        at com.google.common.util.concurrent.Callables$4.run(Callables.java:119) [graylog.jar:?]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_292]
2021-07-14T09:03:05.404Z WARN  [NodePingThread] Did not find meta info of this node. Re-registering.
2021-07-14T09:03:05.413Z ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-14T09:03:06.403Z WARN  [NodePingThread] Did not find meta info of this node. Re-registering.

What is this error and how can I solve this problem?

2

Hello,

I assuming your trying to run the Enterprise version of Graylog?

You could either apply for enterprise license or you could remove the Enterprise plugins.

If you could describe your environment so we have a better idea what’s going on. Like maybe some configuration files, log files. Or explain how you set you set up your cluster in greater detail.

3

I put graylog according to the instructions from here (this is not a enterprise license): CentOS installation — Graylog 4.1.0 documentation
I have 3 servers with elastic on two of them there is a graylog. Mongo replication is made between these 2 servers.
Configuration file from 1 server: server.conf - Pastebin.com
From 2nd server: server.conf - Pastebin.com

4

I looked in /usr/share/graylog-server/plugin and enterprise plugins were installed there. These errors disappeared after I cleaned the plugins. Now there is a new error: [NodePingThread] Did not find meta info of this node. Re-registering. And the master node is still shutting down.

5

The problem was solved. It was necessary to simply synchronize the time using NTP.

1 Like
6

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