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

Description of your problem

Good morning,
I wanted to ask for help to solve a problem that has been happening to me for about 10 days.
Looking at my Graylog logs from the Overview screen I notice this error message:

  • Notification condition [NO_MASTER] has been fixed.

I don’t see any other error messages that can help me understand their meaning.
I have no “index Failure” errors, I have no MenoryHeap or Buffer problems
The only anomaly that presents itself to me is the reset / refresh of the dashboards in display
If I restart my machine the problem goes away for a few days and then returns

Environmental information

Operating system information

  • Ubuntu 20.04.3 virtual on Virtualbox version 6.1.28 with Guest Addictions and Extension Pack installed - 64Gb ram, 8 Processor and 600Gb of Virtual Disk Space
  • Ubuntu 20.04.3 phisical machine with 2 1TB HDD - RAID1 - 256 Gb ram

Package versions

  • Graylog 4.2
  • MongoDB 4.0.27
  • Elasticsearch 7.10.2
1 Like

Hello @alessio.dapelo

I did a quick google search for Notification condition [NO_MASTER] has been fixed.. I came across several post on this issue and it seams a couple different methods of resolving it. Please take a look at below and see if they help resolved your issue. If not, please post your full Graylog and elasticsearch log file using the markdown. Thanks

Periodic "Notification condition [NO_MASTER] has been fixed.

https://graylog2.narkive.com/waXhnhYg/how-to-solve-this-alert-notification-condition-no-master-has-been-fixed

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