Hi all, I am new to Graylog2 and just follow the instruction here to install for the first time: https://www.digitalocean.com/community/tutorials/how-to-install-graylog2-and-centralize-logs-on-ubuntu-14-04
I just got an error when running graylog2-server
2014-07-23 12:25:02,807 DEBUG: org.elasticsearch.discovery.zen -
[graylog2-server] filtered ping responses: (filter_client[true],
filter_data[false]) {none}
2014-07-23 12:25:04,803 ERROR: org.graylog2.Main -
################################################################################
ERROR: Could not successfully connect to ElasticSearch. Check that your
cluster state is not RED and that ElasticSearch is running properly.
elasticsearch health show green?
curl -XGET 'http://localhost:9200/_cluster/health?pretty=true'
{
"cluster_name" : "graylog2",
"status" : "green",
"timed_out" : false,
"number_of_nodes" : 1,
"number_of_data_nodes" : 1,
"active_primary_shards" : 0,
"active_shards" : 0,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 0
}
Much appreciate if anyone could help showing some direction!
Wayne
--
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 graylog2+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
2014-07-23 12:29:37,874 INFO : org.graylog2.Main - Graylog2 0.20.2 starting up.
(JRE: Oracle Corporation 1.7.0_65 on Linux 3.13.0-32-generic)
2014-07-23 12:29:37,952 INFO : org.graylog2.plugin.system.NodeId - Node ID:
19595853-c869-4f6d-9d66-497a9fb710e7
2014-07-23 12:29:38,162 INFO : org.graylog2.buffers.ProcessBuffer - Initialized
ProcessBuffer with ring size <1024> and wait strategy <BlockingWaitStrategy>.
2014-07-23 12:29:38,181 INFO : org.graylog2.buffers.OutputBuffer - Initialized
OutputBuffer with ring size <1024> and wait strategy <BlockingWaitStrategy>.
2014-07-23 12:29:38,486 DEBUG:
com.ning.http.client.providers.netty.NettyAsyncHttpProvider - Number of
application's worker threads is 4
2014-07-23 12:29:38,772 INFO : org.elasticsearch.node - [graylog2-server]
version[0.90.10], pid[6046], build[0a5781f/2014-01-10T10:18:37Z]
2014-07-23 12:29:38,772 INFO : org.elasticsearch.node - [graylog2-server]
initializing ...
2014-07-23 12:29:38,772 DEBUG: org.elasticsearch.node - [graylog2-server] using
home [/opt], config [/opt/config], data [[/opt/data]], logs [/opt/logs], work
[/opt/work], plugins [/opt/plugins]
2014-07-23 12:29:38,779 INFO : org.elasticsearch.plugins - [graylog2-server]
loaded [], sites []
2014-07-23 12:29:38,809 DEBUG: org.elasticsearch.common.compress.lzf - using
[UnsafeChunkDecoder] decoder
2014-07-23 12:29:40,347 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [generic], type [cached], keep_alive [30s]
2014-07-23 12:29:40,357 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [index], type [fixed], size [2], queue_size [200]
2014-07-23 12:29:40,362 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [bulk], type [fixed], size [2], queue_size [50]
2014-07-23 12:29:40,362 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [get], type [fixed], size [2], queue_size [1k]
2014-07-23 12:29:40,362 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [search], type [fixed], size [6], queue_size [1k]
2014-07-23 12:29:40,362 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [suggest], type [fixed], size [2], queue_size [1k]
2014-07-23 12:29:40,362 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [percolate], type [fixed], size [2], queue_size [1k]
2014-07-23 12:29:40,363 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [management], type [scaling], min [1], size [5],
keep_alive [5m]
2014-07-23 12:29:40,364 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [flush], type [scaling], min [1], size [1], keep_alive [5m]
2014-07-23 12:29:40,364 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [merge], type [scaling], min [1], size [1], keep_alive [5m]
2014-07-23 12:29:40,364 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [refresh], type [scaling], min [1], size [1], keep_alive
[5m]
2014-07-23 12:29:40,364 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [warmer], type [scaling], min [1], size [1], keep_alive
[5m]
2014-07-23 12:29:40,364 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [snapshot], type [scaling], min [1], size [1], keep_alive
[5m]
2014-07-23 12:29:40,365 DEBUG: org.elasticsearch.threadpool - [graylog2-server]
creating thread_pool [optimize], type [fixed], size [1], queue_size [null]
2014-07-23 12:29:40,384 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-07-23 12:29:40,398 DEBUG: org.elasticsearch.discovery.zen.ping.multicast -
[graylog2-server] using group [224.2.2.4], with port [54328], ttl [3], and
address [null]
2014-07-23 12:29:40,402 DEBUG: org.elasticsearch.discovery.zen.ping.unicast -
[graylog2-server] using initial hosts [], with concurrent_connects [10]
2014-07-23 12:29:40,404 DEBUG: org.elasticsearch.discovery.zen -
[graylog2-server] using ping.timeout [3s], master_election.filter_client
[true], master_election.filter_data [false]
2014-07-23 12:29:40,405 DEBUG: org.elasticsearch.discovery.zen.elect -
[graylog2-server] using minimum_master_nodes [-1]
2014-07-23 12:29:40,406 DEBUG: org.elasticsearch.discovery.zen.fd -
[graylog2-server] [master] uses ping_interval [1s], ping_timeout [30s],
ping_retries [3]
2014-07-23 12:29:40,420 DEBUG: org.elasticsearch.discovery.zen.fd -
[graylog2-server] [node ] uses ping_interval [1s], ping_timeout [30s],
ping_retries [3]
2014-07-23 12:29:40,459 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-07-23 12:29:40,460 DEBUG: org.elasticsearch.monitor.os - [graylog2-server]
Using probe [org.elasticsearch.monitor.os.JmxOsProbe@2e4b4e64] with
refresh_interval [1s]
2014-07-23 12:29:40,462 DEBUG: org.elasticsearch.monitor.process -
[graylog2-server] Using probe
[org.elasticsearch.monitor.process.JmxProcessProbe@257ded07] with
refresh_interval [1s]
2014-07-23 12:29:40,466 DEBUG: org.elasticsearch.monitor.jvm -
[graylog2-server] Using refresh_interval [1s]
2014-07-23 12:29:40,467 DEBUG: org.elasticsearch.monitor.network -
[graylog2-server] Using probe
[org.elasticsearch.monitor.network.JmxNetworkProbe@1662e91d] with
refresh_interval [5s]
2014-07-23 12:29:40,470 DEBUG: org.elasticsearch.monitor.network -
[graylog2-server] net_info
host [GH21]
eth0 display_name [eth0]
address [/fe80:0:0:0:250:56ff:fead:6d%2] [/158.132.160.117]
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 [65536] multicast [false] ptp [false] loopback [true] up
[true] virtual [false]
2014-07-23 12:29:40,471 DEBUG: org.elasticsearch.monitor.fs - [graylog2-server]
Using probe [org.elasticsearch.monitor.fs.JmxFsProbe@1ae91dff] with
refresh_interval [1s]
2014-07-23 12:29:40,844 DEBUG: org.elasticsearch.indices.store -
[graylog2-server] using indices.store.throttle.type [MERGE], with
index.store.throttle.max_bytes_per_sec [20mb]
2014-07-23 12:29:40,852 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-07-23 12:29:40,862 DEBUG: org.elasticsearch.script - [graylog2-server]
using script cache with max_size [500], expire [null]
2014-07-23 12:29:40,868 DEBUG:
org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using
node_concurrent_recoveries [2], node_initial_primaries_recoveries [4]
2014-07-23 12:29:40,869 DEBUG:
org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using
[cluster.routing.allocation.allow_rebalance] with [indices_all_active]
2014-07-23 12:29:40,869 DEBUG:
org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using
[cluster_concurrent_rebalance] with [2]
2014-07-23 12:29:40,874 DEBUG: org.elasticsearch.gateway.local -
[graylog2-server] using initial_shards [quorum], list_timeout [30s]
2014-07-23 12:29:41,004 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-07-23 12:29:41,098 DEBUG: org.elasticsearch.indices.memory -
[graylog2-server] using index_buffer_size [88mb], with
min_shard_index_buffer_size [4mb], max_shard_index_buffer_size [512mb],
shard_inactive_time [30m]
2014-07-23 12:29:41,100 DEBUG: org.elasticsearch.indices.cache.filter -
[graylog2-server] using [node] weighted filter cache with size [20%],
actual_size [176mb], expire [null], clean_interval [1m]
2014-07-23 12:29:41,101 DEBUG: org.elasticsearch.indices.fielddata.cache -
[graylog2-server] using size [-1] [-1b], expire [null]
2014-07-23 12:29:41,120 DEBUG: org.elasticsearch.gateway.local.state.meta -
[graylog2-server] using gateway.local.auto_import_dangled [YES], with
gateway.local.dangling_timeout [2h]
2014-07-23 12:29:41,125 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-07-23 12:29:41,129 DEBUG:
org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using
node_concurrent_recoveries [2], node_initial_primaries_recoveries [4]
2014-07-23 12:29:41,130 DEBUG:
org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using
[cluster.routing.allocation.allow_rebalance] with [indices_all_active]
2014-07-23 12:29:41,130 DEBUG:
org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using
[cluster_concurrent_rebalance] with [2]
2014-07-23 12:29:41,131 DEBUG:
org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using
node_concurrent_recoveries [2], node_initial_primaries_recoveries [4]
2014-07-23 12:29:41,131 DEBUG:
org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using
[cluster.routing.allocation.allow_rebalance] with [indices_all_active]
2014-07-23 12:29:41,131 DEBUG:
org.elasticsearch.cluster.routing.allocation.decider - [graylog2-server] using
[cluster_concurrent_rebalance] with [2]
2014-07-23 12:29:41,148 INFO : org.elasticsearch.node - [graylog2-server]
initialized
2014-07-23 12:29:41,148 INFO : org.elasticsearch.node - [graylog2-server]
starting ...
2014-07-23 12:29:41,193 DEBUG:
org.elasticsearch.netty.channel.socket.nio.SelectorUtil - Using select timeout
of 500
2014-07-23 12:29:41,193 DEBUG:
org.elasticsearch.netty.channel.socket.nio.SelectorUtil - Epoll-bug workaround
enabled = false
2014-07-23 12:29:41,262 DEBUG: org.elasticsearch.transport.netty -
[graylog2-server] Bound to address [/0:0:0:0:0:0:0:0:9350]
2014-07-23 12:29:41,266 INFO : org.elasticsearch.transport - [graylog2-server]
bound_address {inet[/0:0:0:0:0:0:0:0:9350]}, publish_address
{inet[/158.132.160.117:9350]}
2014-07-23 12:29:44,278 WARN : org.elasticsearch.discovery - [graylog2-server]
waited for 3s and no initial state was set by the discovery
2014-07-23 12:29:44,278 INFO : org.elasticsearch.discovery - [graylog2-server]
graylog2/UJJWEsqQS8-EjJf0-RvCWw
2014-07-23 12:29:44,278 DEBUG: org.elasticsearch.gateway - [graylog2-server]
can't wait on start for (possibly) reading state from gateway, will do it
asynchronously
2014-07-23 12:29:44,279 INFO : org.elasticsearch.node - [graylog2-server]
started
2014-07-23 12:29:44,291 DEBUG: org.elasticsearch.discovery.zen -
[graylog2-server] filtered ping responses: (filter_client[true],
filter_data[false]) {none}
2014-07-23 12:29:47,292 DEBUG: org.elasticsearch.discovery.zen -
[graylog2-server] filtered ping responses: (filter_client[true],
filter_data[false]) {none}
2014-07-23 12:29:49,287 ERROR: org.graylog2.Main -
################################################################################
ERROR: Could not successfully connect to ElasticSearch. Check that your cluster
state is not RED and that ElasticSearch is running properly.
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. :(
################################################################################
elasticsearch.yml
Description: Binary data
# 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 = ufI2KS4zmkyyMjZdJoy7ndLIDiHGrLbV82BLN14bonnAp4ndfLT2UuvjOZZol0qju0S2X9Lo7Dq6sJa4wgB3z0C0ezvznv9q # 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 = 5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8 # 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://127.0.0.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 # Do you want to allow searches to be highlighted? Depending on the size of your messages this can be memory hungry and # should only be enabled after making sure your elasticsearch cluster has enough memory. allow_highlighting = 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 = 192.168.1.203: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 = # elasticsearch_network_bind_host = # elasticsearch_network_publish_host = # 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 # How many seconds to wait between marking node as DEAD for possible load balancers and starting the actual # shutdown process. Set to 0 if you have no status checking load balancers in front. lb_recognition_period_seconds = 3 # 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 = y...@example.com transport_email_auth_password = secret transport_email_subject_prefix = [graylog2] transport_email_from_email = grayl...@example.com # Specify and uncomment this if you want to include links to the stream in your stream alert mails. # This should define the fully qualified base url to your web interface exactly the same way as it is accessed by your users. # # transport_email_web_interface_url = https://graylog2.example.com # HTTP proxy for outgoing HTTP calls #http_proxy_uri =
