running version 0.20.0-rc.1-1 Hello.
I've had my graylog2 node running for a couple weeks and when i got into work this morning i saw that the cluster state was red so i decided to reboot the server to see if it would help. Now when i try to run the graylog2 server, I get the error message:* ERROR: No ElasticSearch master was found.* >From searching this group i stumbled across this thread: https://groups.google.com/forum/#!msg/graylog2/KyWfhRt22mM/9rrelarrF_0J and I tried the solution that was included in that thread. Unfortunately, I'm still coming across the the same error message. I was wondering if there is anyone out there that can give me some insight on this? I have attached the following files for analysis: elasticsearch.yml graylog2.conf graylog2-server.log graylog2_debug_log.txt -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
##################### ElasticSearch Configuration Example ##################### # This file contains an overview of various configuration settings, # targeted at operations staff. Application developers should # consult the guide at <http://elasticsearch.org/guide>. # # The installation procedure is covered at # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>. # # ElasticSearch comes with reasonable defaults for most settings, # so you can try it out without bothering with configuration. # # Most of the time, these defaults are just fine for running a production # cluster. If you're fine-tuning your cluster, or wondering about the # effect of certain configuration option, please _do ask_ on the # mailing list or IRC channel [http://elasticsearch.org/community]. # Any element in the configuration can be replaced with environment variables # by placing them in ${...} notation. For example: # # node.rack: ${RACK_ENV_VAR} # For information on supported formats and syntax for the config file, see # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html> ################################### Cluster ################################### # Cluster name identifies your cluster for auto-discovery. If you're running # multiple clusters on the same network, make sure you're using unique names. # cluster.name: graylog2-production #################################### Node ##################################### # Node names are generated dynamically on startup, so you're relieved # from configuring them manually. You can tie this node to a specific name: # # node.name: "Franz Kafka" # Every node can be configured to allow or deny being eligible as the master, # and to allow or deny to store the data. # # Allow this node to be eligible as a master node (enabled by default): # # node.master: true # # Allow this node to store data (enabled by default): # # node.data: true # You can exploit these settings to design advanced cluster topologies. # # 1. You want this node to never become a master node, only to hold data. # This will be the "workhorse" of your cluster. # # node.master: false # node.data: true # # 2. You want this node to only serve as a master: to not store any data and # to have free resources. This will be the "coordinator" of your cluster. # # node.master: true # node.data: false # # 3. You want this node to be neither master nor data node, but # to act as a "search load balancer" (fetching data from nodes, # aggregating results, etc.) # # node.master: false # node.data: false # Use the Cluster Health API [http://localhost:9200/_cluster/health], the # Node Info API [http://localhost:9200/_cluster/nodes] or GUI tools # such as <http://github.com/lukas-vlcek/bigdesk> and # <http://mobz.github.com/elasticsearch-head> to inspect the cluster state. # A node can have generic attributes associated with it, which can later be used # for customized shard allocation filtering, or allocation awareness. An attribute # is a simple key value pair, similar to node.key: value, here is an example: # # node.rack: rack314 # By default, multiple nodes are allowed to start from the same installation location # to disable it, set the following: # node.max_local_storage_nodes: 1 #################################### Index #################################### # You can set a number of options (such as shard/replica options, mapping # or analyzer definitions, translog settings, ...) for indices globally, # in this file. # # Note, that it makes more sense to configure index settings specifically for # a certain index, either when creating it or by using the index templates API. # # See <http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html> and # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html> # for more information. # Set the number of shards (splits) of an index (5 by default): # # index.number_of_shards: 5 # Set the number of replicas (additional copies) of an index (1 by default): # # index.number_of_replicas: 1 # Note, that for development on a local machine, with small indices, it usually # makes sense to "disable" the distributed features: # # index.number_of_shards: 1 # index.number_of_replicas: 0 # These settings directly affect the performance of index and search operations # in your cluster. Assuming you have enough machines to hold shards and # replicas, the rule of thumb is: # # 1. Having more *shards* enhances the _indexing_ performance and allows to # _distribute_ a big index across machines. # 2. Having more *replicas* enhances the _search_ performance and improves the # cluster _availability_. # # The "number_of_shards" is a one-time setting for an index. # # The "number_of_replicas" can be increased or decreased anytime, # by using the Index Update Settings API. # # ElasticSearch takes care about load balancing, relocating, gathering the # results from nodes, etc. Experiment with different settings to fine-tune # your setup. # Use the Index Status API (<http://localhost:9200/A/_status>) to inspect # the index status. #################################### Paths #################################### # Path to directory containing configuration (this file and logging.yml): # # path.conf: /path/to/conf # Path to directory where to store index data allocated for this node. # # path.data: /path/to/data # # Can optionally include more than one location, causing data to be striped across # the locations (a la RAID 0) on a file level, favouring locations with most free # space on creation. For example: # # path.data: /path/to/data1,/path/to/data2 # Path to temporary files: # # path.work: /path/to/work # Path to log files: # # path.logs: /path/to/logs # Path to where plugins are installed: # # path.plugins: /path/to/plugins #################################### Plugin ################################### # If a plugin listed here is not installed for current node, the node will not start. # # plugin.mandatory: mapper-attachments,lang-groovy ################################### Memory #################################### # ElasticSearch performs poorly when JVM starts swapping: you should ensure that # it _never_ swaps. # # Set this property to true to lock the memory: # # bootstrap.mlockall: true # Make sure that the ES_MIN_MEM and ES_MAX_MEM environment variables are set # to the same value, and that the machine has enough memory to allocate # for ElasticSearch, leaving enough memory for the operating system itself. # # You should also make sure that the ElasticSearch process is allowed to lock # the memory, eg. by using `ulimit -l unlimited`. ############################## Network And HTTP ############################### # ElasticSearch, by default, binds itself to the 0.0.0.0 address, and listens # on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node # communication. (the range means that if the port is busy, it will automatically # try the next port). # Set the bind address specifically (IPv4 or IPv6): # # network.bind_host: 192.168.0.1 # Set the address other nodes will use to communicate with this node. If not # set, it is automatically derived. It must point to an actual IP address. # # network.publish_host: 192.168.0.1 # Set both 'bind_host' and 'publish_host': # # network.host: 192.168.0.1 # Set a custom port for the node to node communication (9300 by default): # # transport.tcp.port: 9300 # Enable compression for all communication between nodes (disabled by default): # # transport.tcp.compress: true # Set a custom port to listen for HTTP traffic: # # http.port: 9200 # Set a custom allowed content length: # # http.max_content_length: 100mb # Disable HTTP completely: # # http.enabled: false ################################### Gateway ################################### # The gateway allows for persisting the cluster state between full cluster # restarts. Every change to the state (such as adding an index) will be stored # in the gateway, and when the cluster starts up for the first time, # it will read its state from the gateway. # There are several types of gateway implementations. For more information, see # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html>. # The default gateway type is the "local" gateway (recommended): # # gateway.type: local # Settings below control how and when to start the initial recovery process on # a full cluster restart (to reuse as much local data as possible when using shared # gateway). # Allow recovery process after N nodes in a cluster are up: # # gateway.recover_after_nodes: 1 # Set the timeout to initiate the recovery process, once the N nodes # from previous setting are up (accepts time value): # # gateway.recover_after_time: 5m # Set how many nodes are expected in this cluster. Once these N nodes # are up (and recover_after_nodes is met), begin recovery process immediately # (without waiting for recover_after_time to expire): # # gateway.expected_nodes: 2 ############################# Recovery Throttling ############################# # These settings allow to control the process of shards allocation between # nodes during initial recovery, replica allocation, rebalancing, # or when adding and removing nodes. # Set the number of concurrent recoveries happening on a node: # # 1. During the initial recovery # # cluster.routing.allocation.node_initial_primaries_recoveries: 4 # # 2. During adding/removing nodes, rebalancing, etc # # cluster.routing.allocation.node_concurrent_recoveries: 2 # Set to throttle throughput when recovering (eg. 100mb, by default 20mb): # # indices.recovery.max_bytes_per_sec: 20mb # Set to limit the number of open concurrent streams when # recovering a shard from a peer: # # indices.recovery.concurrent_streams: 5 ################################## Discovery ################################## # Discovery infrastructure ensures nodes can be found within a cluster # and master node is elected. Multicast discovery is the default. # Set to ensure a node sees N other master eligible nodes to be considered # operational within the cluster. Its recommended to set it to a higher value # than 1 when running more than 2 nodes in the cluster. # # discovery.zen.minimum_master_nodes: 1 # Set the time to wait for ping responses from other nodes when discovering. # Set this option to a higher value on a slow or congested network # to minimize discovery failures: # # discovery.zen.ping.timeout: 3s # For more information, see # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html> # Unicast discovery allows to explicitly control which nodes will be used # to discover the cluster. It can be used when multicast is not present, # or to restrict the cluster communication-wise. # # 1. Disable multicast discovery (enabled by default): # # discovery.zen.ping.multicast.enabled: false # # 2. Configure an initial list of master nodes in the cluster # to perform discovery when new nodes (master or data) are started: # # discovery.zen.ping.unicast.hosts: ["host1", "host2:port"] # EC2 discovery allows to use AWS EC2 API in order to perform discovery. # # You have to install the cloud-aws plugin for enabling the EC2 discovery. # # For more information, see # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html> # # See <http://elasticsearch.org/tutorials/elasticsearch-on-ec2/> # for a step-by-step tutorial. ################################## Slow Log ################################## # Shard level query and fetch threshold logging. #index.search.slowlog.threshold.query.warn: 10s #index.search.slowlog.threshold.query.info: 5s #index.search.slowlog.threshold.query.debug: 2s #index.search.slowlog.threshold.query.trace: 500ms #index.search.slowlog.threshold.fetch.warn: 1s #index.search.slowlog.threshold.fetch.info: 800ms #index.search.slowlog.threshold.fetch.debug: 500ms #index.search.slowlog.threshold.fetch.trace: 200ms #index.indexing.slowlog.threshold.index.warn: 10s #index.indexing.slowlog.threshold.index.info: 5s #index.indexing.slowlog.threshold.index.debug: 2s #index.indexing.slowlog.threshold.index.trace: 500ms ################################## GC Logging ################################ #monitor.jvm.gc.young.warn: 1000ms #monitor.jvm.gc.young.info: 700ms #monitor.jvm.gc.young.debug: 400ms #monitor.jvm.gc.old.warn: 10s #monitor.jvm.gc.old.info: 5s #monitor.jvm.gc.old.debug: 2s
# If you are running more than one instances of graylog2-server you have to select one of these # instances as master. The master will perform some periodical tasks that non-masters won't perform. is_master = true # The auto-generated node ID will be stored in this file and read after restarts. It is a good idea # to use an absolute file path here if you are starting graylog2-server from init scripts or similar. node_id_file = /etc/graylog2-server-node-id # You MUST set a secret to secure/pepper the stored user passwords here. Use at least 64 characters. # Generate one by using for example: pwgen -s 96 password_secret = qDsCCHOVyGSQGdgCHkXnIiKuJsQDiArafnAhPCk3403ZDuxNcB4NgHgljWkrLYgW0xlIogBow827HxjGGhnDzpDs5mcJt6Ac # the default root user is named 'admin' root_username = admin # You MUST specify a hash password for the root user (which you only need to initially set up the # system and in case you lose connectivity to your authentication backend) # Create one by using for example: echo -n yourpassword | shasum -a 256 # and put the resulting hash value into the following line root_password_sha2 = 8C6976E5B5410415BDE908BD4DEE15DFB167A9C873FC4BB8A81F6F2AB448A918 # Set plugin directory here (relative or absolute) plugin_dir = plugin # REST API listen URI. Must be reachable by other graylog2-server nodes if you run a cluster. rest_listen_uri = http://127.0.0.1:12900/ # REST API transport address. Defaults to first non-loopback IPv4 system address and port 12900. # This will be promoted in the cluster discovery APIs and other nodes may try to connect on this # address. (see rest_listen_uri) #rest_transport_uri = http://192.168.1.1:12900/ # Embedded elasticsearch configuration file # pay attention to the working directory of the server, maybe use an absolute path here elasticsearch_config_file = /opt/elasticsearch/elasticsearch-0.90.10/config/elasticsearch.yml elasticsearch_max_docs_per_index = 20000000 # How many indices do you want to keep? # elasticsearch_max_number_of_indices*elasticsearch_max_docs_per_index=total number of messages in your setup elasticsearch_max_number_of_indices = 20 # Decide what happens with the oldest indices when the maximum number of indices is reached. # The following strategies are availble: # - delete # Deletes the index completely (Default) # - close # Closes the index and hides it from the system. Can be re-opened later. retention_strategy = delete # How many ElasticSearch shards and replicas should be used per index? Note that this only applies to newly created indices. elasticsearch_shards = 4 elasticsearch_replicas = 0 elasticsearch_index_prefix = graylog2 # Do you want to allow searches with leading wildcards? This can be extremely resource hungry and should only # be enabled with care. See also: http://support.torch.sh/help/kb/graylog2-web-interface/the-search-bar-explained allow_leading_wildcard_searches = false # settings to be passed to elasticsearch's client (overriding those in the provided elasticsearch_config_file) # all these # this must be the same as for your elasticsearch cluster elasticsearch_cluster_name = graylog2-production # you could also leave this out, but makes it easier to identify the graylog2 client instance #elasticsearch_node_name = graylog2-server # we don't want the graylog2 server to store any data, or be master node #elasticsearch_node_master = false #elasticsearch_node_data = false # use a different port if you run multiple elasticsearch nodes on one machine #elasticsearch_transport_tcp_port = 9350 # we don't need to run the embedded HTTP server here #elasticsearch_http_enabled = false elasticsearch_discovery_zen_ping_multicast_enabled = false elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300 # Analyzer (tokenizer) to use for message and full_message field. The "standard" filter usually is a good idea. # All supported analyzers are: standard, simple, whitespace, stop, keyword, pattern, language, snowball, custom # ElasticSearch documentation: http://www.elasticsearch.org/guide/reference/index-modules/analysis/ # Note that this setting only takes effect on newly created indices. elasticsearch_analyzer = standard # Batch size for all outputs. This is the maximum (!) number of messages an output module will get at once. # For example, if this is set to 5000 (default), the ElasticSearch Output will not index more than 5000 messages # at once. After that index operation is performed, the next batch will be indexed. If there is only 1 message # waiting, it will only index that single message. It is important to raise this parameter if you send in so # many messages that it is not enough to index 5000 messages at once. (Only at *really* high message rates) output_batch_size = 5000 # The number of parallel running processors. # Raise this number if your buffers are filling up. processbuffer_processors = 5 outputbuffer_processors = 5 # Wait strategy describing how buffer processors wait on a cursor sequence. (default: sleeping) # Possible types: # - yielding # Compromise between performance and CPU usage. # - sleeping # Compromise between performance and CPU usage. Latency spikes can occur after quiet periods. # - blocking # High throughput, low latency, higher CPU usage. # - busy_spinning # Avoids syscalls which could introduce latency jitter. Best when threads can be bound to specific CPU cores. processor_wait_strategy = blocking # Size of internal ring buffers. Raise this if raising outputbuffer_processors does not help anymore. # For optimum performance your LogMessage objects in the ring buffer should fit in your CPU L3 cache. # Start server with --statistics flag to see buffer utilization. # Must be a power of 2. (512, 1024, 2048, ...) ring_size = 1024 # MongoDB Configuration mongodb_useauth = false #mongodb_user = grayloguser #mongodb_password = 123 mongodb_host = 127.0.0.1 #mongodb_replica_set = localhost:27017,localhost:27018,localhost:27019 mongodb_database = graylog2 mongodb_port = 27017 # Raise this according to the maximum connections your MongoDB server can handle if you encounter MongoDB connection problems. mongodb_max_connections = 100 # Number of threads allowed to be blocked by MongoDB connections multiplier. Default: 5 # If mongodb_max_connections is 100, and mongodb_threads_allowed_to_block_multiplier is 5, then 500 threads can block. More than that and an exception will be thrown. # http://api.mongodb.org/java/current/com/mongodb/MongoOptions.html#threadsAllowedToBlockForConnectionMultiplier mongodb_threads_allowed_to_block_multiplier = 5 # Drools Rule File (Use to rewrite incoming log messages) # See: http://support.torch.sh/help/kb/graylog2-server/custom-message-rewritingprocessing # rules_file = /etc/graylog2.drl # Email transport transport_email_enabled = false transport_email_hostname = mail.example.com transport_email_port = 587 transport_email_use_auth = true transport_email_use_tls = true transport_email_use_ssl = true transport_email_auth_username = [email protected] transport_email_auth_password = secret transport_email_subject_prefix = [graylog2] transport_email_from_email = [email protected]
root@testboxv2:/opt/graylog2-server-0.20.0-rc.1-1# java -jar graylog2-server.jar --debug 2014-02-17 11:19:48,103 INFO : org.graylog2.Main - Graylog2 0.20.0-rc.1-1 starting up. (JRE: Oracle Corporation 1.7.0_25 on Linux 3.2.0-4-686-pae) 2014-02-17 11:19:48,195 INFO : org.graylog2.plugin.system.NodeId - Node ID: f269c99b-f16f-43e2-bc21-64944becbc94 2014-02-17 11:19:48,197 INFO : org.graylog2.Core - No rest_transport_uri set. Falling back to [http://10.5.4.210:12900]. 2014-02-17 11:19:48,370 INFO : org.graylog2.buffers.ProcessBuffer - Initialized ProcessBuffer with ring size <1024> and wait strategy <BlockingWaitStrategy>. 2014-02-17 11:19:48,385 INFO : org.graylog2.buffers.OutputBuffer - Initialized OutputBuffer with ring size <1024> and wait strategy <BlockingWaitStrategy>. 2014-02-17 11:19:48,799 INFO : org.elasticsearch.node - [graylog2-server] version[0.90.10], pid[3553], build[0a5781f/2014-01-10T10:18:37Z] 2014-02-17 11:19:48,799 INFO : org.elasticsearch.node - [graylog2-server] initializing ... 2014-02-17 11:19:48,799 DEBUG: org.elasticsearch.node - [graylog2-server] using home [/opt/graylog2/graylog2-server-0.20.0-rc.1-1], config [/opt/graylog2/graylog2-server-0.20.0-rc.1-1/config], data [[/opt/graylog2/graylog2-server-0.20.0-rc.1-1/data]], logs [/opt/graylog2/graylog2-server-0.20.0-rc.1-1/logs], work [/opt/graylog2/graylog2-server-0.20.0-rc.1-1/work], plugins [/opt/graylog2/graylog2-server-0.20.0-rc.1-1/plugins] 2014-02-17 11:19:48,805 INFO : org.elasticsearch.plugins - [graylog2-server] loaded [], sites [] 2014-02-17 11:19:48,826 DEBUG: org.elasticsearch.common.compress.lzf - using [UnsafeChunkDecoder] decoder 2014-02-17 11:19:49,928 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [generic], type [cached], keep_alive [30s] 2014-02-17 11:19:49,942 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [index], type [fixed], size [2], queue_size [200] 2014-02-17 11:19:49,946 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [bulk], type [fixed], size [2], queue_size [50] 2014-02-17 11:19:49,946 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [get], type [fixed], size [2], queue_size [1k] 2014-02-17 11:19:49,946 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [search], type [fixed], size [6], queue_size [1k] 2014-02-17 11:19:49,946 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [suggest], type [fixed], size [2], queue_size [1k] 2014-02-17 11:19:49,947 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [percolate], type [fixed], size [2], queue_size [1k] 2014-02-17 11:19:49,947 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [management], type [scaling], min [1], size [5], keep_alive [5m] 2014-02-17 11:19:49,948 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [flush], type [scaling], min [1], size [1], keep_alive [5m] 2014-02-17 11:19:49,948 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [merge], type [scaling], min [1], size [1], keep_alive [5m] 2014-02-17 11:19:49,948 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [refresh], type [scaling], min [1], size [1], keep_alive [5m] 2014-02-17 11:19:49,949 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [warmer], type [scaling], min [1], size [1], keep_alive [5m] 2014-02-17 11:19:49,949 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [snapshot], type [scaling], min [1], size [1], keep_alive [5m] 2014-02-17 11:19:49,949 DEBUG: org.elasticsearch.threadpool - [graylog2-server] creating thread_pool [optimize], type [fixed], size [1], queue_size [null] 2014-02-17 11:19:49,966 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] using worker_count[4], port[9350], bind_host[null], publish_host[null], compress[false], connect_timeout[30s], connections_per_node[2/3/6/1/1], receive_predictor[512kb->512kb] 2014-02-17 11:19:49,977 DEBUG: org.elasticsearch.discovery.zen.ping.unicast - [graylog2-server] using initial hosts [127.0.0.1:9300], with concurrent_connects [10] 2014-02-17 11:19:49,978 DEBUG: org.elasticsearch.discovery.zen - [graylog2-server] using ping.timeout [3s], master_election.filter_client [true], master_election.filter_data [false] 2014-02-17 11:19:49,979 DEBUG: org.elasticsearch.discovery.zen.elect - [graylog2-server] using minimum_master_nodes [-1] 2014-02-17 11:19:49,980 DEBUG: org.elasticsearch.discovery.zen.fd - [graylog2-server] [master] uses ping_interval [1s], ping_timeout [30s], ping_retries [3] 2014-02-17 11:19:49,992 DEBUG: org.elasticsearch.discovery.zen.fd - [graylog2-server] [node ] uses ping_interval [1s], ping_timeout [30s], ping_retries [3] 2014-02-17 11:19:50,020 DEBUG: org.elasticsearch.monitor.jvm - [graylog2-server] enabled [true], last_gc_enabled [false], interval [1s], gc_threshold [{old=GcThreshold{name='old', warnThreshold=10000, infoThreshold=5000, debugThreshold=2000}, default=GcThreshold{name='default', warnThreshold=10000, infoThreshold=5000, debugThreshold=2000}, young=GcThreshold{name='young', warnThreshold=1000, infoThreshold=700, debugThreshold=400}}] 2014-02-17 11:19:50,022 DEBUG: org.elasticsearch.monitor.os - [graylog2-server] Using probe [org.elasticsearch.monitor.os.JmxOsProbe@19721a6] with refresh_interval [1s] 2014-02-17 11:19:50,023 DEBUG: org.elasticsearch.monitor.process - [graylog2-server] Using probe [org.elasticsearch.monitor.process.JmxProcessProbe@9c142a] with refresh_interval [1s] 2014-02-17 11:19:50,027 DEBUG: org.elasticsearch.monitor.jvm - [graylog2-server] Using refresh_interval [1s] 2014-02-17 11:19:50,028 DEBUG: org.elasticsearch.monitor.network - [graylog2-server] Using probe [org.elasticsearch.monitor.network.JmxNetworkProbe@1d304ac] with refresh_interval [5s] 2014-02-17 11:19:50,029 DEBUG: org.elasticsearch.monitor.network - [graylog2-server] net_info host [testboxv2] eth0 display_name [eth0] address [/fe80:0:0:0:21e:4fff:fed4:3143%2] [/10.5.4.210] mtu [1500] multicast [true] ptp [false] loopback [false] up [true] virtual [false] lo display_name [lo] address [/0:0:0:0:0:0:0:1%1] [/127.0.0.1] mtu [16436] multicast [false] ptp [false] loopback [true] up [true] virtual [false] 2014-02-17 11:19:50,031 DEBUG: org.elasticsearch.monitor.fs - [graylog2-server] Using probe [org.elasticsearch.monitor.fs.JmxFsProbe@14d874b] with refresh_interval [1s] 2014-02-17 11:19:50,346 DEBUG: org.elasticsearch.indices.store - [graylog2-server] using indices.store.throttle.type [MERGE], with index.store.throttle.max_bytes_per_sec [20mb] 2014-02-17 11:19:50,351 DEBUG: org.elasticsearch.cache.memory - [graylog2-server] using bytebuffer cache with small_buffer_size [1kb], large_buffer_size [1mb], small_cache_size [10mb], large_cache_size [500mb], direct [true] 2014-02-17 11:19:50,359 DEBUG: org.elasticsearch.script - [graylog2-server] using script cache with max_size [500], expire [null] 2014-02-17 11:19:50,364 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using node_concurrent_recoveries [2], node_initial_primaries_recoveries [4] 2014-02-17 11:19:50,365 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster.routing.allocation.allow_rebalance] with [indices_all_active] 2014-02-17 11:19:50,366 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster_concurrent_rebalance] with [2] 2014-02-17 11:19:50,369 DEBUG: org.elasticsearch.gateway.local - [graylog2-server] using initial_shards [quorum], list_timeout [30s] 2014-02-17 11:19:50,462 DEBUG: org.elasticsearch.indices.recovery - [graylog2-server] using max_bytes_per_sec[20mb], concurrent_streams [3], file_chunk_size [512kb], translog_size [512kb], translog_ops [1000], and compress [true] 2014-02-17 11:19:50,511 DEBUG: org.elasticsearch.indices.memory - [graylog2-server] using index_buffer_size [87.1mb], with min_shard_index_buffer_size [4mb], max_shard_index_buffer_size [512mb], shard_inactive_time [30m] 2014-02-17 11:19:50,512 DEBUG: org.elasticsearch.indices.cache.filter - [graylog2-server] using [node] weighted filter cache with size [20%], actual_size [174.2mb], expire [null], clean_interval [1m] 2014-02-17 11:19:50,514 DEBUG: org.elasticsearch.indices.fielddata.cache - [graylog2-server] using size [-1] [-1b], expire [null] 2014-02-17 11:19:50,531 DEBUG: org.elasticsearch.gateway.local.state.meta - [graylog2-server] using gateway.local.auto_import_dangled [YES], with gateway.local.dangling_timeout [2h] 2014-02-17 11:19:50,533 DEBUG: org.elasticsearch.bulk.udp - [graylog2-server] using enabled [false], host [null], port [9700-9800], bulk_actions [1000], bulk_size [5mb], flush_interval [5s], concurrent_requests [4] 2014-02-17 11:19:50,537 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using node_concurrent_recoveries [2], node_initial_primaries_recoveries [4] 2014-02-17 11:19:50,537 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster.routing.allocation.allow_rebalance] with [indices_all_active] 2014-02-17 11:19:50,537 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster_concurrent_rebalance] with [2] 2014-02-17 11:19:50,538 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using node_concurrent_recoveries [2], node_initial_primaries_recoveries [4] 2014-02-17 11:19:50,538 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster.routing.allocation.allow_rebalance] with [indices_all_active] 2014-02-17 11:19:50,538 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster_concurrent_rebalance] with [2] 2014-02-17 11:19:50,548 INFO : org.elasticsearch.node - [graylog2-server] initialized 2014-02-17 11:19:50,548 INFO : org.elasticsearch.node - [graylog2-server] starting ... 2014-02-17 11:19:50,569 DEBUG: org.elasticsearch.netty.channel.socket.nio.SelectorUtil - Using select timeout of 500 2014-02-17 11:19:50,570 DEBUG: org.elasticsearch.netty.channel.socket.nio.SelectorUtil - Epoll-bug workaround enabled = false 2014-02-17 11:19:50,642 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] Bound to address [/0:0:0:0:0:0:0:0:9350] 2014-02-17 11:19:50,645 INFO : org.elasticsearch.transport - [graylog2-server] bound_address {inet[/0:0:0:0:0:0:0:0:9350]}, publish_address {inet[/10.5.4.210:9350]} 2014-02-17 11:19:50,679 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] connected to node [[#zen_unicast_1#][inet[/127.0.0.1:9300]]] 2014-02-17 11:19:53,659 WARN : org.elasticsearch.discovery - [graylog2-server] waited for 3s and no initial state was set by the discovery 2014-02-17 11:19:53,660 INFO : org.elasticsearch.discovery - [graylog2-server] graylog2-production/cSjpkRtzRZm8HVJrjw1sHg 2014-02-17 11:19:53,660 DEBUG: org.elasticsearch.gateway - [graylog2-server] can't wait on start for (possibly) reading state from gateway, will do it asynchronously 2014-02-17 11:19:53,661 INFO : org.elasticsearch.node - [graylog2-server] started 2014-02-17 11:19:53,670 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] disconnected from [[#zen_unicast_1#][inet[/127.0.0.1:9300]]] 2014-02-17 11:19:53,671 DEBUG: org.elasticsearch.discovery.zen - [graylog2-server] filtered ping responses: (filter_client[true], filter_data[false]) --> target [[Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]]], master [[Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]]] 2014-02-17 11:19:53,677 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] connected to node [[Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]]] 2014-02-17 11:19:53,717 DEBUG: org.elasticsearch.discovery.zen.fd - [graylog2-server] [master] starting fault detection against master [[Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]]], reason [initial_join] 2014-02-17 11:19:53,725 DEBUG: org.elasticsearch.discovery.zen.publish - [graylog2-server] received cluster state version 4 2014-02-17 11:19:53,728 DEBUG: org.elasticsearch.cluster.service - [graylog2-server] processing [zen-disco-receive(from master [[Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]]])]: execute 2014-02-17 11:19:53,729 DEBUG: org.elasticsearch.cluster.service - [graylog2-server] got first state from fresh master [fKXrKhQSTE2nVUNeWaLQxg] 2014-02-17 11:19:53,729 DEBUG: org.elasticsearch.cluster.service - [graylog2-server] cluster state updated, version [4], source [zen-disco-receive(from master [[Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]]])] 2014-02-17 11:19:53,730 INFO : org.elasticsearch.cluster.service - [graylog2-server] detected_master [Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]], added {[Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]],}, reason: zen-disco-receive(from master [[Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]]]) 2014-02-17 11:19:53,730 DEBUG: org.elasticsearch.cluster.service - [graylog2-server] set local cluster state to version 4 2014-02-17 11:19:53,736 DEBUG: org.elasticsearch.cluster.service - [graylog2-server] processing [zen-disco-receive(from master [[Agent Axis][fKXrKhQSTE2nVUNeWaLQxg][inet[/10.5.4.210:9300]]])]: done applying updated cluster_state (version: 4) 2014-02-17 11:19:58,672 ERROR: org.graylog2.Main - ################################################################################ ERROR: No ElasticSearch master was found. Need help? * Official documentation: http://support.torch.sh/help/kb * Mailing list: http://support.torch.sh/help/kb/general/forums-mailing-list * Issue tracker: http://support.torch.sh/help/kb/general/issue-trackers * Commercial support: http://www.torch.sh/ But we also got some specific help pages that might help you in this case: * http://support.torch.sh/help/kb/graylog2-server/configuring-and-tuning-elasticsearch-for-graylog2-v0200 Terminating. :( ################################################################################
2014-02-17 09:35:14,535 INFO : org.graylog2.Main - Graylog2 0.20.0-rc.1-1 starting up. (JRE: Oracle Corporation 1.7.0_25 on Linux 3.2.0-4-686-pae) 2014-02-17 09:35:14,626 INFO : org.graylog2.plugin.system.NodeId - Node ID: f269c99b-f16f-43e2-bc21-64944becbc94 2014-02-17 09:35:14,628 INFO : org.graylog2.Core - No rest_transport_uri set. Falling back to [http://10.5.4.210:12900]. 2014-02-17 09:35:14,808 INFO : org.graylog2.buffers.ProcessBuffer - Initialized ProcessBuffer with ring size <1024> and wait strategy <BlockingWaitStrategy>. 2014-02-17 09:35:14,822 INFO : org.graylog2.buffers.OutputBuffer - Initialized OutputBuffer with ring size <1024> and wait strategy <BlockingWaitStrategy>. 2014-02-17 09:35:15,124 INFO : org.elasticsearch.node - [graylog2-server] version[0.90.10], pid[3538], build[0a5781f/2014-01-10T10:18:37Z] 2014-02-17 09:35:15,125 INFO : org.elasticsearch.node - [graylog2-server] initializing ... 2014-02-17 09:35:15,131 INFO : org.elasticsearch.plugins - [graylog2-server] loaded [], sites [] 2014-02-17 09:35:16,853 INFO : org.elasticsearch.node - [graylog2-server] initialized 2014-02-17 09:35:16,854 INFO : org.elasticsearch.node - [graylog2-server] starting ... 2014-02-17 09:35:16,942 INFO : org.elasticsearch.transport - [graylog2-server] bound_address {inet[/0:0:0:0:0:0:0:0:9350]}, publish_address {inet[/10.5.4.210:9350]} 2014-02-17 09:35:19,961 WARN : org.elasticsearch.discovery - [graylog2-server] waited for 3s and no initial state was set by the discovery 2014-02-17 09:35:19,961 INFO : org.elasticsearch.discovery - [graylog2-server] graylog2-production/dGjTSr_nTOWi3R53OlLxrA 2014-02-17 09:35:19,963 INFO : org.elasticsearch.node - [graylog2-server] started 2014-02-17 09:35:20,031 INFO : org.elasticsearch.cluster.service - [graylog2-server] detected_master [Bes][oJmOlVZZS6GVbIoOQtPTsQ][inet[/10.5.4.210:9300]], added {[Bes][oJmOlVZZS6GVbIoOQtPTsQ][inet[/10.5.4.210:9300]],}, reason: zen-disco-receive(from master [[Bes][oJmOlVZZS6GVbIoOQtPTsQ][inet[/10.5.4.210:9300]]]) 2014-02-17 09:35:24,973 ERROR: org.graylog2.Main - ################################################################################ ERROR: No ElasticSearch master was found. Need help? * Official documentation: http://support.torch.sh/help/kb * Mailing list: http://support.torch.sh/help/kb/general/forums-mailing-list * Issue tracker: http://support.torch.sh/help/kb/general/issue-trackers * Commercial support: http://www.torch.sh/ But we also got some specific help pages that might help you in this case: * http://support.torch.sh/help/kb/graylog2-server/configuring-and-tuning-elasticsearch-for-graylog2-v0200 Terminating. :( ################################################################################
