After Upgrade to 4.3.7: No leader Graylog server node

After the Upgrade from 4.3.3 to 4.3.7 I get periodic error messages that I have no leader Graylog server node in my cluster.

In the Graylog Node view (https:///system/nodes) I can see that my master node is there, than disappears, than appears again … and so on.

Version 4.3.3 was running perfectly fine.

Please help.

What is written in the log?
And just for sure: Did you notice the change in configuration " Configuration File Changes"? →

You can post you config file if you like:

  • Use the </> forum tool to make the code readable
  • Obfuscate where needed
  • take out the comments with:
    ** cat /etc/graylog/server/server.conf | egrep -v "^\s*(#|$)"
1 Like


I’ve a similar problem.
I’m running a 3 node cluster with docker. I tried to upgrade from 4.2.3 to 4.3.7, I know it is a big step :slight_smile:
I downloaded all the plugins for 4.3.7, made change in the config file is_master → is_leader and restarted my graylog docker master node.
When logging into the new master node in system/overview it says: unknown (no_master)
and Cluster ID: Not available
number of nodes: 0

in the log I gets this errors:

graylog_1  | 2022-09-29 06:15:24,628 ERROR: - Unhandled exception in REST resource
graylog_1  | java.lang.NullPointerException: null
graylog_1  |    at org.graylog2.cluster.NodeImpl.isLeader( ~[graylog.jar:?]
graylog_1  |    at ~[graylog.jar:?]
graylog_1  |    at ~[graylog.jar:?]
graylog_1  |    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_345]
graylog_1  |    at sun.reflect.NativeMethodAccessorImpl.invoke( ~[?:1.8.0_345]
graylog_1  |    at sun.reflect.DelegatingMethodAccessorImpl.invoke( ~[?:1.8.0_345]
graylog_1  |    at java.lang.reflect.Method.invoke( ~[?:1.8.0_345]
graylog_1  |    at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0( ~[graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$ ~[graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke( ~[graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch( ~[graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch( ~[graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke( ~[graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply( ~[graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply( ~[graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.ServerRuntime$ [graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.internal.Errors$ [graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.internal.Errors$ [graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.internal.Errors.process( [graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.internal.Errors.process( [graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.internal.Errors.process( [graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.process.internal.RequestScope.runInScope( [graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.ServerRuntime.process( [graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.server.ApplicationHandler.handle( [graylog.jar:?]
graylog_1  |    at org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service( [graylog.jar:?]
graylog_1  |    at org.glassfish.grizzly.http.server.HttpHandler$ [graylog.jar:?]
graylog_1  |    at com.codahale.metrics.InstrumentedExecutorService$ [graylog.jar:?]
graylog_1  |    at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:1.8.0_345]
graylog_1  |    at java.util.concurrent.ThreadPoolExecutor$ [?:1.8.0_345]
graylog_1  |    at [?:1.8.0_345]

kind regards
Jens M. Kofoed


It could be a couple different issues, hard to tell from just the information you gave.
BUT the Erro you See NO MASTER , you can check here.

or here

1 Like

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