Re: [graylog2] Healthy Elastisearch not connecting
Your Graylog web interface tries to contact a server in http://172.25.7.41:12900/, but looking at your server configuration, it is not listening there. That's why you get a timeout. Are you using a proxy or load balancer in front of your Graylog server? If so, please ensure you read http://docs.graylog.org/en/2.0/pages/configuring_webif.html#making-the-web-interface-work-with-load-balancers-proxies Edmundo > On 03 Jun 2016, at 17:32, Scott Johnwrote: > > Dev Console Output > > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:22664 > OPTIONS http://172.25.7.41:12900/system/sessions > net::ERR_CONNECTION_TIMED_OUTRequest.end @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:22664(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:16757tryCatcher > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:21388Promise._resolveFromResolver > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:19467Promise > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:19057Request.promise > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:16756Request.then > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:16791json > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:16637_validateSession > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:86153init > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:86120t > @ vendor.js:415e.exports @ vendor.js:415(anonymous function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:86109__webpack_require__ > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:20Session > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:2330getStore > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:2390(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:25453__webpack_require__ > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:20CurrentUser > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:2207getStore > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:2390(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:1987__webpack_require__ > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:20(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:1898__webpack_require__ > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:20(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:1776__webpack_require__ > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:20(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:1556__webpack_require__ > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:20(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:345__webpack_require__ > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:20(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:229__webpack_require__ > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:20(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:57__webpack_require__ > @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:20(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:40(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:43 > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:16591 > There was an error fetching a resource: Bad request. Additional information: > Not availableFetchError @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:16591(anonymous > function) @ > plugin.org.graylog.plugins.pipelineprocessor.PipelineProcessorPlugin.4a52dfb….js:16659tryCatcher > @ >
Re: [graylog2] Healthy Elastisearch not connecting
Hi Scott, That is most likely due to some misconfiguration. Would you be so kind as to share any errors in your server logs and your browser's developer console (https://developers.google.com/web/tools/chrome-devtools/)? Regards, Edmundo > On 03 Jun 2016, at 17:00, Scott Johnwrote: > > ok after adding the web_listen_uri value I now get a login prompt but if i > leave it alone on the login prompt or i try to login after a minute or so it > goes to the server unavailable message. > > On Thursday, June 2, 2016 at 4:37:24 PM UTC-4, Scott John wrote: > I am getting the following error in my graylog log file. > > 2016-06-02T16:16:55.327-04:00 WARN [BlockingBatchedESOutput] Error while > waiting for healthy Elasticsearch cluster. Not flushing. > java.util.concurrent.TimeoutException: Elasticsearch cluster didn't get > healthy within timeout > at > org.graylog2.indexer.cluster.Cluster.waitForConnectedAndHealthy(Cluster.java:179) > ~[graylog.jar:?] > at > org.graylog2.indexer.cluster.Cluster.waitForConnectedAndHealthy(Cluster.java:184) > ~[graylog.jar:?] > at > org.graylog2.outputs.BlockingBatchedESOutput.flush(BlockingBatchedESOutput.java:112) > [graylog.jar:?] > at > org.graylog2.outputs.BlockingBatchedESOutput.write(BlockingBatchedESOutput.java:105) > [graylog.jar:?] > at > org.graylog2.buffers.processors.OutputBufferProcessor$1.run(OutputBufferProcessor.java:189) > [graylog.jar:?] > at > com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:176) > [graylog.jar:?] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [?:1.8.0_91] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [?:1.8.0_91] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [?:1.8.0_91] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [?:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91] > > The web interface comes up but reports that it cannot connect to the server > on port 12900. > GL - 2.0.2 > ES - 2.3.3 > MDB - 3.0.12 > OS - RHEL 7.2 > Installed from repos. > > curl -XGET http://localhost:9200/_cluster/health?pretty > { > "cluster_name" : "graylog2", > "status" : "green", > "timed_out" : false, > "number_of_nodes" : 1, > "number_of_data_nodes" : 1, > "active_primary_shards" : 48, > "active_shards" : 48, > "relocating_shards" : 0, > "initializing_shards" : 0, > "unassigned_shards" : 0, > "delayed_unassigned_shards" : 0, > "number_of_pending_tasks" : 0, > "number_of_in_flight_fetch" : 0, > "task_max_waiting_in_queue_millis" : 0, > "active_shards_percent_as_number" : 100.0 > } > > elasticsearch.yml > > cluster.name: graylog2 > network.host: 127.0.0.1 > discovery.zen.ping.multicast.enabled: false > discovery.zen.ping.unicast.hosts: ["127.0.0.1:9300"] > script.inline: on > script.indexed: on > > server.conf > > is_master = true > node_id_file = /etc/graylog/server/node-id > password_secret = > root_password_sha2 = > root_email = "ad...@email.com" > root_timezone = UTC > rest_listen_uri = http://127.0.0.1:12900/ > rotation_strategy = count > elasticsearch_max_docs_per_index = 2000 > elasticsearch_max_number_of_indices = 20 > retention_strategy = delete > elasticsearch_shards = 4 > elasticsearch_replicas = 0 > elasticsearch_index_prefix = graylog2 > allow_leading_wildcard_searches = false > allow_highlighting = false > elasticsearch_http_enabled = false > elasticsearch_discovery_zen_ping_multicast_enabled = false > elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300 > elasticsearch_network_host = 127.0.0.1 > elasticsearch_analyzer = standard > output_batch_size = 500 > output_flush_interval = 1 > output_fault_count_threshold = 5 > output_fault_penalty_seconds = 30 > processbuffer_processors = 5 > outputbuffer_processors = 3 > processor_wait_strategy = blocking > ring_size = 65536 > inputbuffer_ring_size = 65536 > inputbuffer_processors = 2 > inputbuffer_wait_strategy = blocking > message_journal_enabled = true > message_journal_dir = /var/lib/graylog-server/journal > dead_letters_enabled = false > lb_recognition_period_seconds = 3 > mongodb_uri = mongodb://localhost/graylog2 > mongodb_max_connections = 100 > mongodb_threads_allowed_to_block_multiplier = 5 > mongodb_useauth = false > transport_email_enabled = false > transport_email_hostname = mailhost.email.com > transport_email_port = 587 > transport_email_use_auth = false > transport_email_use_tls = true > transport_email_subject_prefix = [graylog2] > transport_email_from_email = g...@email.com > transport_email_web_interface_url = https://glog.email.com > content_packs_dir = /usr/share/graylog-server/contentpacks > content_packs_auto_load = grok-patterns.json > > > What am I missing here? > > -- >
[graylog2] Healthy Elastisearch not connecting
I am getting the following error in my graylog log file. 2016-06-02T16:16:55.327-04:00 WARN [BlockingBatchedESOutput] Error while waiting for healthy Elasticsearch cluster. Not flushing. java.util.concurrent.TimeoutException: Elasticsearch cluster didn't get healthy within timeout at org.graylog2.indexer.cluster.Cluster.waitForConnectedAndHealthy(Cluster.java:179) ~[graylog.jar:?] at org.graylog2.indexer.cluster.Cluster.waitForConnectedAndHealthy(Cluster.java:184) ~[graylog.jar:?] at org.graylog2.outputs.BlockingBatchedESOutput.flush(BlockingBatchedESOutput.java:112) [graylog.jar:?] at org.graylog2.outputs.BlockingBatchedESOutput.write(BlockingBatchedESOutput.java:105) [graylog.jar:?] at org.graylog2.buffers.processors.OutputBufferProcessor$1.run(OutputBufferProcessor.java:189) [graylog.jar:?] at com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:176) [graylog.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_91] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_91] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_91] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_91] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91] The web interface comes up but reports that it cannot connect to the server on port 12900. GL - 2.0.2 ES - 2.3.3 MDB - 3.0.12 OS - RHEL 7.2 Installed from repos. curl -XGET http://localhost:9200/_cluster/health?pretty { "cluster_name" : "graylog2", "status" : "green", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 48, "active_shards" : 48, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 0, "active_shards_percent_as_number" : 100.0 } elasticsearch.yml cluster.name: graylog2 network.host: 127.0.0.1 discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["127.0.0.1:9300"] script.inline: on script.indexed: on server.conf is_master = true node_id_file = /etc/graylog/server/node-id password_secret = root_password_sha2 = root_email = "ad...@email.com" root_timezone = UTC rest_listen_uri = http://127.0.0.1:12900/ rotation_strategy = count elasticsearch_max_docs_per_index = 2000 elasticsearch_max_number_of_indices = 20 retention_strategy = delete elasticsearch_shards = 4 elasticsearch_replicas = 0 elasticsearch_index_prefix = graylog2 allow_leading_wildcard_searches = false allow_highlighting = false elasticsearch_http_enabled = false elasticsearch_discovery_zen_ping_multicast_enabled = false elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300 elasticsearch_network_host = 127.0.0.1 elasticsearch_analyzer = standard output_batch_size = 500 output_flush_interval = 1 output_fault_count_threshold = 5 output_fault_penalty_seconds = 30 processbuffer_processors = 5 outputbuffer_processors = 3 processor_wait_strategy = blocking ring_size = 65536 inputbuffer_ring_size = 65536 inputbuffer_processors = 2 inputbuffer_wait_strategy = blocking message_journal_enabled = true message_journal_dir = /var/lib/graylog-server/journal dead_letters_enabled = false lb_recognition_period_seconds = 3 mongodb_uri = mongodb://localhost/graylog2 mongodb_max_connections = 100 mongodb_threads_allowed_to_block_multiplier = 5 mongodb_useauth = false transport_email_enabled = false transport_email_hostname = mailhost.email.com transport_email_port = 587 transport_email_use_auth = false transport_email_use_tls = true transport_email_subject_prefix = [graylog2] transport_email_from_email = g...@email.com transport_email_web_interface_url = https://glog.email.com content_packs_dir = /usr/share/graylog-server/contentpacks content_packs_auto_load = grok-patterns.json What am I missing here? -- 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/340cf3bd-417a-4506-95cd-bdc661856293%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.