Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question. Don’t forget to select tags to help index your topic! 1. Describe your incident: After the graylog version was upgraded from 4.2 to 4.3, the cl…

in your server.conf, try changing: is_master= true to is_leader= true

@l1125262511 I fixed your post, it was hard to read the log file, also take a look here. Graylog 4.2 and message - Notification condition [NO_MASTER] has been fixed

After the graylog version was upgraded from 4.2 to 4.3, the cluster could not find the master node

Graylog Central (peer support)

gsmith (GSmith) July 1, 2022, 11:47pm 4

@l1125262511

I fixed your post, it was hard to read the log file, also take a look here.

Graylog 4.2 and message - Notification condition [NO_MASTER] has been fixed

Topic		Replies	Views
After Upgrade to 4.3.7: No leader Graylog server node Graylog Central (peer support)	4	2625	September 29, 2022
Error after upgrade from 4.2.7 to 4.3.3 Graylog Central (peer support)	4	829	August 5, 2022
Graylog 4.2 and message - Notification condition [NO_MASTER] has been fixed Graylog Central (peer support)	1	1509	November 8, 2021
Graylog 2.2 Cluster Issue Graylog Central (peer support)	6	4393	April 10, 2017
Notification condition [NO_MASTER] has been fixed Graylog Central (peer support)	19	5596	April 27, 2020

After the graylog version was upgraded from 4.2 to 4.3, the cluster could not find the master node

Related topics