Hi I am having some issues to configure ES and GrayLog on EC2. I am attempting a unicast connection setup (both ES and Gray are on the same machine).
I have followed this documentation. http://support.torch.sh/help/kb/graylog2-server/configuring-and-tuning-elasticsearch-for-graylog2-v0200 ES log. Es seems to be running correctly. [2014-03-24 07:11:46,823][INFO ][node ] [Mother Night] {0.90.1}[2994]: initializing ... [2014-03-24 07:11:46,834][INFO ][plugins ] [Mother Night] loaded [], sites [] [2014-03-24 07:11:51,163][INFO ][node ] [Mother Night] {0.90.1}[2994]: initialized [2014-03-24 07:11:51,164][INFO ][node ] [Mother Night] {0.90.1}[2994]: starting ... [2014-03-24 07:11:51,314][INFO ][transport ] [Mother Night] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.235.39.91:9300]} [2014-03-24 07:11:54,366][INFO ][cluster.service ] [Mother Night] new_master [Mother Night][FpWGZg8XQvaNPTJ9DYTdyw][inet[/10.235.39.91:9300]]{data=false, master=true}, reason: zen-disco-join (elected_as_master) [2014-03-24 07:11:54,380][INFO ][discovery ] [Mother Night] graylog2/FpWGZg8XQvaNPTJ9DYTdyw [2014-03-24 07:11:54,409][INFO ][http ] [Mother Night] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.235.39.91:9200]} [2014-03-24 07:11:54,410][INFO ][node ] [Mother Night] {0.90.1}[2994]: started [2014-03-24 07:11:54,466][INFO ][gateway ] [Mother Night] recovered [1] indices into cluster_state GrayLog for connection attempt. 2014-03-24 07:12:14,186 DEBUG: org.elasticsearch.monitor.fs - [graylog2-server] Using probe [org.elasticsearch.monitor.fs.JmxFsProbe@3874afa7] with refresh_interval [1s] 2014-03-24 07:12:14,953 DEBUG: org.elasticsearch.indices.store - [graylog2-server] using indices.store.throttle.type [MERGE], with index.store.throttle.max_bytes_per_sec [20mb] 2014-03-24 07:12:14,961 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-03-24 07:12:14,971 DEBUG: org.elasticsearch.script - [graylog2-server] using script cache with max_size [500], expire [null] 2014-03-24 07:12:14,978 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using node_concurrent_recoveries [2], node_initial_primaries_recoveries [4] 2014-03-24 07:12:14,979 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster.routing.allocation.allow_rebalance] with [indices_all_active] 2014-03-24 07:12:14,980 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster_concurrent_rebalance] with [2] 2014-03-24 07:12:14,985 DEBUG: org.elasticsearch.gateway.local - [graylog2-server] using initial_shards [quorum], list_timeout [30s] 2014-03-24 07:12:15,246 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-03-24 07:12:15,347 DEBUG: org.elasticsearch.indices.memory - [graylog2-server] using index_buffer_size [48mb], with min_shard_index_buffer_size [4mb], max_shard_index_buffer_size [512mb], shard_inactive_time [30m] 2014-03-24 07:12:15,353 DEBUG: org.elasticsearch.indices.cache.filter - [graylog2-server] using [node] weighted filter cache with size [20%], actual_size [57.6mb], expire [null], clean_interval [1m] 2014-03-24 07:12:15,355 DEBUG: org.elasticsearch.indices.fielddata.cache - [graylog2-server] using size [-1] [-1b], expire [null] 2014-03-24 07:12:15,377 DEBUG: org.elasticsearch.gateway.local.state.meta - [graylog2-server] using gateway.local.auto_import_dangled [YES], with gateway.local.dangling_timeout [2h] 2014-03-24 07:12:15,385 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-03-24 07:12:15,390 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using node_concurrent_recoveries [2], node_initial_primaries_recoveries [4] 2014-03-24 07:12:15,391 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster.routing.allocation.allow_rebalance] with [indices_all_active] 2014-03-24 07:12:15,391 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster_concurrent_rebalance] with [2] 2014-03-24 07:12:15,392 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using node_concurrent_recoveries [2], node_initial_primaries_recoveries [4] 2014-03-24 07:12:15,393 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster.routing.allocation.allow_rebalance] with [indices_all_active] 2014-03-24 07:12:15,393 DEBUG: org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using [cluster_concurrent_rebalance] with [2] 2014-03-24 07:12:15,409 INFO : org.elasticsearch.node - [graylog2-server] initialized 2014-03-24 07:12:15,410 INFO : org.elasticsearch.node - [graylog2-server] starting ... 2014-03-24 07:12:15,435 DEBUG: org.elasticsearch.netty.channel.socket.nio.SelectorUtil - Using select timeout of 500 2014-03-24 07:12:15,441 DEBUG: org.elasticsearch.netty.channel.socket.nio.SelectorUtil - Epoll-bug workaround enabled = false 2014-03-24 07:12:15,544 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] Bound to address [/10.235.39.91:9350] 2014-03-24 07:12:15,545 INFO : org.elasticsearch.transport - [graylog2-server] bound_address {inet[/10.235.39.91:9350]}, publish_address {inet[ec2-54-244-91-145.us-west-2.compute.amazonaws.com/10.235.39.91:9350]} 2014-03-24 07:12:15,583 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] connected to node [[#zen_unicast_1#][inet[/10.235.39.91:9300]]] 2014-03-24 07:12:18,553 WARN : org.elasticsearch.discovery - [graylog2-server] waited for 3s and no initial state was set by the discovery 2014-03-24 07:12:18,554 INFO : org.elasticsearch.discovery - [graylog2-server] graylog2/iTirwl5ZRw-IICt9p9gwkg 2014-03-24 07:12:18,554 DEBUG: org.elasticsearch.gateway - [graylog2-server] can't wait on start for (possibly) reading state from gateway, will do it asynchronously 2014-03-24 07:12:18,555 INFO : org.elasticsearch.node - [graylog2-server] started 2014-03-24 07:12:18,568 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] disconnected from [[#zen_unicast_1#][inet[/10.235.39.91:9300]]] 2014-03-24 07:12:18,572 DEBUG: org.elasticsearch.discovery.zen - [graylog2-server] filtered ping responses: (filter_client[true], filter_data[false]) --> target [[Mother Night][FpWGZg8XQvaNPTJ9DYTdyw][inet[/10.235.39.91:9300]]{data=false, master=true}], master [[Mother Night][FpWGZg8XQvaNPTJ9DYTdyw][inet[/10.235.39.91:9300]]{data=false, master=true}] 2014-03-24 07:12:18,592 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] connected to node [[Mother Night][FpWGZg8XQvaNPTJ9DYTdyw][inet[/10.235.39.91:9300]]{data=false, master=true}] 2014-03-24 07:12:18,693 WARN : org.elasticsearch.transport.netty - [graylog2-server] Message not fully read (request) for [3] and action [discovery/zen/join/validate], resetting 2014-03-24 07:12:18,790 INFO : org.elasticsearch.discovery.zen - [graylog2-server] failed to send join request to master [[Mother Night][FpWGZg8XQvaNPTJ9DYTdyw][inet[/10.235.39.91:9300]]{data=false, master=true}], reason [org.elasticsearch.transport.RemoteTransportException: [Mother Night][inet[/10.235.39.91:9300]][discovery/zen/join]; org.elasticsearch.transport.RemoteTransportException: [graylog2-server][inet[/10.235.39.91:9350]][discovery/zen/join/validate]; java.io.IOException: Expected handle header, got [7]] 2014-03-24 07:12:18,792 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] connected to node [[#zen_unicast_1#][inet[/10.235.39.91:9300]]] 2014-03-24 07:12:21,795 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] disconnected from [[#zen_unicast_1#][inet[/10.235.39.91:9300]]] 2014-03-24 07:12:21,797 DEBUG: org.elasticsearch.discovery.zen - [graylog2-server] filtered ping responses: (filter_client[true], filter_data[false]) --> target [[Mother Night][FpWGZg8XQvaNPTJ9DYTdyw][inet[/10.235.39.91:9300]]{data=false, master=true}], master [[Mother Night][FpWGZg8XQvaNPTJ9DYTdyw][inet[/10.235.39.91:9300]]{data=false, master=true}] 2014-03-24 07:12:21,808 WARN : org.elasticsearch.transport.netty - [graylog2-server] Message not fully read (request) for [4] and action [discovery/zen/join/validate], resetting 2014-03-24 07:12:21,816 INFO : org.elasticsearch.discovery.zen - [graylog2-server] failed to send join request to master [[Mother Night][FpWGZg8XQvaNPTJ9DYTdyw][inet[/10.235.39.91:9300]]{data=false, master=true}], reason [org.elasticsearch.transport.RemoteTransportException: [Mother Night][inet[/10.235.39.91:9300]][discovery/zen/join]; org.elasticsearch.transport.RemoteTransportException: [graylog2-server][inet[/10.235.39.91:9350]][discovery/zen/join/validate]; java.io.IOException: Expected handle header, got [7]] 2014-03-24 07:12:21,921 DEBUG: org.elasticsearch.transport.netty - [graylog2-server] connected to node [[#zen_unicast_1#][inet[/10.235.39.91:9300]]] 2014-03-24 07:12:23,591 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. :( ################################################################################ -- 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/d/optout.
# 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 = clue amos nu omen mug mit volt pea knot kind set sigh tide jo need sunk nap kim swum torn tan sang army sock book cub only year cat mace owly tied mort hell area fee cuff dint sun grew nibs cot goof ply ada rim lien slam navy arts from mend vain sown bach pew ohio din tick set liar when hoff hiss ivan verb lest is gage ohio hut suds jane dash tote bits pam nary aunt soda top nest nibs trag neon ream to fay read fig nave dud see duct join due ;ENTROPY=1056.00 bits # 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) # This password cannot be changed using the API or via the web interface. If you need to change it, # modify it in this file. # 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 = cec32406e54bd4768ca8f1fc2f85f16898e37b4ce2d82d09016812afc55fc355 # 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/ # Enable CORS headers for REST api. This is necessary for JS-clients accessing the server directly. # If these are disabled, modern browsers will not be able to retrieve resources from the server. # This is disabled by default. Uncomment the next line to enable it. #rest_enable_cors = true # Enable GZIP support for REST api. This compresses API responses and therefore helps to reduce # overall round trip times. This is disabled by default. Uncomment the next line to enable it. #rest_enable_gzip = true # Embedded elasticsearch configuration file # pay attention to the working directory of the server, maybe use an absolute path here #elasticsearch_config_file = /etc/graylog2-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 = 1 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 # 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 = 10.235.39.91:9300 # the following settings allow to change the bind addresses for the elasticsearch client in graylog2 # these settings are empty by default, letting elasticsearch choose automatically, # override them here or in the 'elasticsearch_config_file' if you need to bind to a special address # refer to http://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/modules-network.html for special values here # elasticsearch_network_host = 10.235.39.91 # elasticsearch_network_bind_host = 10.235.39.91 # elasticsearch_network_publish_host = 10.235.39.91 # 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 # EXPERIMENTAL: Dead Letters # Every failed indexing attempt is logged by default and made visible in the web-interface. You can enable # the experimental dead letters feature to write every message that was not successfully indexed into the # MongoDB "dead_letters" collection to make sure that you never lose a message. The actual writing of dead # letter should work fine already but it is not heavily tested yet and will get more features in future # releases. dead_letters_enabled = false # MongoDB Configuration # mongodb_useauth = true # mongodb_user = grayloguser # mongodb_password = graylogpass 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] # HTTP proxy for outgoing HTTP calls #http_proxy_uri =
elasticsearch.yml
Description: Binary data
