Hi, <https://lh3.googleusercontent.com/-m8Va2NDbxjo/WJMQeq3sbwI/AAAAAAAAOKg/3-gSrjwOWHceKYD9IuByQ5aADw-BAAlMACLcB/s1600/GRLG_HELP.PNG>
*graylog.conf on GRAYLOG SERVER:* is_master = true node_id_file = /var/opt/graylog/graylog-server-node-id rest_listen_uri = http://0.0.0.0:9000/api web_listen_uri = http://0.0.0.0:9000/ elasticsearch_shards = 4 elasticsearch_replicas = 1 elasticsearch_discovery_zen_ping_unicast_hosts = 192.168.1.XX:9300,192.168.1.XX:9300,192.168.1.XX:9300 elasticsearch_cluster_discovery_timeout = 5000 elasticsearch_network_host = 0.0.0.0 *http://192.168.1.xx:9200/_cluster/state?human&pretty* "nodes" : { "VqnZug3bTe-SYeYEJTxbbg" : { "name" : "Servidor Graylog", "transport_address" : "192.168.1.xx:9300", "attributes" : { "data" : "false", "master" : "true" } }, "HD4nGhhfTNuj323-4vzJ8A" : { "name" : "Servidor Elasticsearch 01", "transport_address" : "192.168.1.xx:9300", "attributes" : { "master" : "true" } }, "A6tbkcVMQC6X3ogr7LBCBw" : { "name" : "graylog-d84e9b91-9e4e-4ca9-a13f-09e824f26e0b", "transport_address" : "192.168.1.xx:9350", "attributes" : { "client" : "true", "data" : "false", "master" : "false" } }, "z1xsgIoQSDqie4Wj3xT10w" : { "name" : "Servidor Elasticsearch 02", "transport_address" : "192.168.1.xx:9300", "attributes" : { "master" : "true" } } }, */etc/elasticsearch/elasticsearch.yml on ES1:* <https://lh3.googleusercontent.com/-yPMH7f6kHWk/WJMSQSUPFII/AAAAAAAAOKw/CjkwDxUfdoEs9ES0jeLMjUI4gpqghNs7QCLcB/s1600/alerts.PNG> cluster.name: graylog node.name: "Servidor Elasticsearch 01" node.master: true node.data: true network.host: 192.168.1.x1 network.bind_host: 192.168.1.x1 network.publish_host: 192.168.1.x1 discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["192.168.1.x1:9300" , "192.168.1.x2:9300" , "192.168.1.x3:9300"] index.number_of_replicas: 1 index.number_of_shards: 2 Thanks El jueves, 2 de febrero de 2017, 10:30:04 (UTC+1), Jochen Schalanda escribió: > > Hi Aitor, > > please post the logs of your Graylog node, your Graylog configuration > (including JVM settings), and some details about the hardware of the > machine running Graylog. > > Cheers, > Jochen > > On Thursday, 2 February 2017 07:57:34 UTC+1, Aitor Mendoza wrote: >> >> Hello, >> >> Since I configured my Graylog server sometimes appears this alert: >> *Notification condition [NO_MASTER] has been fixed.* >> I have *one Graylog server* with *two ElasticSearch nodes*. I already >> check the server.conf to verify that is_master is correct. >> >> Yesterday I found that it could also be because I did not have >> synchronized time (I always had it correctly), but I also installed NTP and >> configured the 3 hosts with the same NTP servers configuration. >> But it seems that the warning still appears ... >> >> I appreciate any help, thank you in advance! >> > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/99f968cb-8093-446b-b475-2966ad4adf37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
