[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch || [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessibl
Hi Bernadette, please refer to http://docs.graylog.org/en/2.1/pages/configuration/elasticsearch.html#elasticsearch-versions for the list of Elasticsearch versions used by Graylog. Please keep in mind that Graylog 1.1.3 is a pretty old version and I'd recommend upgrading to at least Graylog 1.3.3 or even better to the latest stable release (Graylog 2.1.1 at the time of writing). Cheers, Jochen On Monday, 24 October 2016 22:00:22 UTC+2, bernadet...@wavestrike.com wrote: > > we have a similar issue with graylog-server 1.1.3-1 and ES 1.7.5. Where is > there a compatibility chart listed ? > > Thanks in advance, Bernadette > -- 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/60a88a27-e086-4a7d-9da6-ff71bc28b0aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch || [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessibl
Hi, which error message do you get? What's your Graylog and your Elasticsearch configuration? Cheers, Jochen On Friday, 3 June 2016 05:17:00 UTC+2, Sgt Mako wrote: > > Also bumping, as I have the exact same problem, and have tried many > different fixes, all to no avail. > -- 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/e7d15a05-758c-4172-9798-f13a41deadb1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch || [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessibl
Hi,
make sure to use the exact same ES cluster name in your Graylog
configuration and in your Elasticsearch configuration (see
https://github.com/Graylog2/graylog2-server/blob/2.0.2/misc/graylog.conf#L210-L213
)
Cheers,
Jochen
On Wednesday, 18 May 2016 15:41:08 UTC+2, EP wrote:
>
> Jochen,
>
> Yes, elasticsearch is running on the same machine. I made the changes
> as suggested:
>
> elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300
>
>
> But I'm still receiving the same error:
>
> 2016-05-18T09:38:48.996-04:00 INFO [IndexRangesCleanupPeriodical]
> Skipping index range cleanup because the Elasticsearch cluster is
> unreachable or unhealthy
> 2016-05-18T09:39:33.994-04:00 INFO [IndexerClusterCheckerThread] Indexer
> not fully initialized yet. Skipping periodic cluster check.
>
> But when running curl on the server:
>
> curl -X GET http://127.0.0.1:9200
> {
> "name" : "SuperPro",
> "cluster_name" : "graylog2",
> "version" : {
> "number" : "2.3.2",
> "build_hash" : "b9e4a6acad4008027e4038f6abed7f7dba346f94",
> "build_timestamp" : "2016-04-21T16:03:47Z",
> "build_snapshot" : false,
> "lucene_version" : "5.5.0"
> },
> "tagline" : "You Know, for Search"
> }
>
>
> 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,
> "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
> }
>
>
> Thanks
>
--
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/affc7b6c-5a82-4311-96a8-5e5dc19b05a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch || [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessibl
Also bumping, as I have the exact same problem, and have tried many different fixes, all to no avail. -- 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/b3efb3e8-0777-4c5f-aeb7-fe6f0ae9263a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch || [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessibl
Bump for assistance. Thanks! -- 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/d9cd6cea-2afc-429b-a18c-76ea413de96e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch || [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessibl
Jochen,
Yes, elasticsearch is running on the same machine. I made the changes
as suggested:
elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300
But I'm still receiving the same error:
2016-05-18T09:38:48.996-04:00 INFO [IndexRangesCleanupPeriodical] Skipping
index range cleanup because the Elasticsearch cluster is unreachable or
unhealthy
2016-05-18T09:39:33.994-04:00 INFO [IndexerClusterCheckerThread] Indexer
not fully initialized yet. Skipping periodic cluster check.
But when running curl on the server:
curl -X GET http://127.0.0.1:9200
{
"name" : "SuperPro",
"cluster_name" : "graylog2",
"version" : {
"number" : "2.3.2",
"build_hash" : "b9e4a6acad4008027e4038f6abed7f7dba346f94",
"build_timestamp" : "2016-04-21T16:03:47Z",
"build_snapshot" : false,
"lucene_version" : "5.5.0"
},
"tagline" : "You Know, for Search"
}
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,
"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
}
Thanks
--
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/14702937-908a-4178-bc0f-20ae88858627%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch || [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessibl
Hi, is Elasticsearch running on the same machine as Graylog? You might also want to change elasticsearch_discovery_zen_ping_unicast_hosts to 127.0.0.1:9300 ($IP_ADDR:$PORT). Cheers, Jochen On Tuesday, 17 May 2016 17:25:39 UTC+2, EP wrote: > > Jochen, > > Thanks for the reply. Please see version info below: > > > yum info graylog-server | grep Version && yum info elasticsearch | grep > Version > Version : 2.0.1 > Version : 2.3.2 > > -- 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/3cfcae25-b92f-4231-b591-ffeab123c1de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch || [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessibl
Hi Jochen,
Thanks for replying. See versions below:
yum info graylog-server | grep Version && yum info elasticsearch | grep
Version
Version : 2.0.1
Version : 2.3.2
On Monday, May 16, 2016 at 2:26:53 PM UTC-5, EP wrote:
>
> First time setting up Graylog and Elasticsearch
>
> Receiving the errors in the subject line.
>
> Configs and logs below:
>
> ES yml
>
> cluster.name: graylog2
> network.bind_host: localhost
> http.port: 9200
> discovery.zen.ping.unicast.hosts: 127.0.0.1
> script.inline: off
> script.indexed: off
>
>
> Graylog server.conf
>
> is_master = true
> node_id_file = /etc/graylog/server/node-id
> password_secret =
> root_password_sha2 =
> plugin_dir = /usr/share/graylog-server/plugin
> rest_listen_uri = http://127.0.0.1:12900/
> rotation_strategy = count
> elasticsearch_max_docs_per_index = 2000
> rotation_strategy = count
> elasticsearch_max_docs_per_index = 2000
> elasticsearch_max_number_of_indices = 20
> retention_strategy = delete
> elasticsearch_max_number_of_indices = 20
> retention_strategy = delete
> elasticsearch_shards = 4
> elasticsearch_replicas = 0
> elasticsearch_index_prefix = graylog
> allow_leading_wildcard_searches = false
> allow_highlighting = false
> elasticsearch_discovery_zen_ping_unicast_hosts = 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
> lb_recognition_period_seconds = 3
> mongodb_uri = mongodb://localhost/graylog
> mongodb_max_connections = 1000
> mongodb_threads_allowed_to_block_multiplier = 5
> content_packs_dir = /usr/share/graylog-server/contentpacks
> content_packs_auto_load = grok-patterns.json
>
>
>
> graylog-server.log
>
> 2016-05-16T15:06:11.556-04:00 INFO [CmdLineTool] Loaded plugins:
> [Anonymous Usage Statistics 2.0.1
> [org.graylog.plugins.usagestatistics.UsageStatsPlugin], Pipeline Processor
> Plugin 1.0.0-beta.3
> [org.graylog.plugins.pipelineprocessor.ProcessorPlugin], Collector 1.0.1
> [org.graylog.plugins.collector.CollectorPlugin], MapWidgetPlugin 1.0.1
> [org.graylog.plugins.map.MapWidgetPlugin], Enterprise Integration Plugin
> 1.0.1
> [org.graylog.plugins.enterprise_integration.EnterpriseIntegrationPlugin]]
> 2016-05-16T15:06:11.666-04:00 INFO [CmdLineTool] Running with JVM
> arguments: -Xms1g -Xmx1g -XX:NewRatio=1 -XX:+ResizeTLAB
> -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled
> -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC
> -XX:-OmitStackTraceInFastThrow
> -Dlog4j.configurationFile=file:///etc/graylog/server/log4j2.xml
> -Djava.library.path=/usr/share/graylog-server/lib/sigar
> -Dgraylog2.installation_source=rpm
> 2016-05-16T15:06:14.252-04:00 INFO [InputBufferImpl] Message journal is
> enabled.
> 2016-05-16T15:06:14.480-04:00 INFO [LogManager] Loading logs.
> 2016-05-16T15:06:14.579-04:00 INFO [LogManager] Logs loading complete.
> 2016-05-16T15:06:14.580-04:00 INFO [KafkaJournal] Initialized Kafka based
> journal at /var/lib/graylog-server/journal
> 2016-05-16T15:06:14.614-04:00 INFO [InputBufferImpl] Initialized
> InputBufferImpl with ring size <65536> and wait strategy
> , running 2 parallel message handlers.
> 2016-05-16T15:06:14.657-04:00 INFO [cluster] Cluster created with
> settings {hosts=[localhost:27017], mode=SINGLE,
> requiredClusterType=UNKNOWN, serverSelectionTimeout='3 ms',
> maxWaitQueueSize=5000}
> 2016-05-16T15:06:14.694-04:00 INFO [cluster] No server chosen by
> ReadPreferenceServerSelector{readPreference=primary} from cluster
> description ClusterDescription{type=UNKNOWN, connectionMode=SINGLE,
> all=[ServerDescription{address=localhost:27017, type=UNKNOWN,
> state=CONNECTING}]}. Waiting for 3 ms before timing out
> 2016-05-16T15:06:14.738-04:00 INFO [connection] Opened connection
> [connectionId{localValue:1, serverValue:93}] to localhost:27017
> 2016-05-16T15:06:14.740-04:00 INFO [cluster] Monitor thread successfully
> connected to server with description
> ServerDescription{address=localhost:27017, type=STANDALONE,
> state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 2, 6]},
> minWireVersion=0, maxWireVersion=4, maxDocumentSize=16777216,
> roundTripTimeNanos=694440}
> 2016-05-16T15:06:14.750-04:00 INFO [connection] Opened connection
> [connectionId{localValue:2, serverValue:94}] to localhost:27017
> 2016-05-16T15:06:15.005-04:00 INFO [NodeId] Node ID:
> b8f9b2e6-ce5f-451a-b8b4-4109281c831d
> 2016-05-16T15:06:15.106-04:00 INFO [node]
> [graylog-b8f9b2e6-ce5f-451a-b8b4-4109281c831d] version[2.3.2], pid[9867],
> build[b9e4a6a/2016-04-21T16:03:47Z]
> 2016-05-16T15:06:15.106-04:00 INFO
[graylog2] Re: [IndexerSetupService] Could not connect to Elasticsearch || [IndexerSetupService] If you're using multicast, check that it is working in your network and that Elasticsearch is accessibl
Hi,
which version of Graylog and which version of Elasticsearch are you running?
Cheers,
Jochen
On Monday, 16 May 2016 21:26:53 UTC+2, EP wrote:
>
> First time setting up Graylog and Elasticsearch
>
> Receiving the errors in the subject line.
>
> Configs and logs below:
>
> ES yml
>
> cluster.name: graylog2
> network.bind_host: localhost
> http.port: 9200
> discovery.zen.ping.unicast.hosts: 127.0.0.1
> script.inline: off
> script.indexed: off
>
>
> Graylog server.conf
>
> is_master = true
> node_id_file = /etc/graylog/server/node-id
> password_secret =
> root_password_sha2 =
> plugin_dir = /usr/share/graylog-server/plugin
> rest_listen_uri = http://127.0.0.1:12900/
> rotation_strategy = count
> elasticsearch_max_docs_per_index = 2000
> rotation_strategy = count
> elasticsearch_max_docs_per_index = 2000
> elasticsearch_max_number_of_indices = 20
> retention_strategy = delete
> elasticsearch_max_number_of_indices = 20
> retention_strategy = delete
> elasticsearch_shards = 4
> elasticsearch_replicas = 0
> elasticsearch_index_prefix = graylog
> allow_leading_wildcard_searches = false
> allow_highlighting = false
> elasticsearch_discovery_zen_ping_unicast_hosts = 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
> lb_recognition_period_seconds = 3
> mongodb_uri = mongodb://localhost/graylog
> mongodb_max_connections = 1000
> mongodb_threads_allowed_to_block_multiplier = 5
> content_packs_dir = /usr/share/graylog-server/contentpacks
> content_packs_auto_load = grok-patterns.json
>
>
>
> graylog-server.log
>
> 2016-05-16T15:06:11.556-04:00 INFO [CmdLineTool] Loaded plugins:
> [Anonymous Usage Statistics 2.0.1
> [org.graylog.plugins.usagestatistics.UsageStatsPlugin], Pipeline Processor
> Plugin 1.0.0-beta.3
> [org.graylog.plugins.pipelineprocessor.ProcessorPlugin], Collector 1.0.1
> [org.graylog.plugins.collector.CollectorPlugin], MapWidgetPlugin 1.0.1
> [org.graylog.plugins.map.MapWidgetPlugin], Enterprise Integration Plugin
> 1.0.1
> [org.graylog.plugins.enterprise_integration.EnterpriseIntegrationPlugin]]
> 2016-05-16T15:06:11.666-04:00 INFO [CmdLineTool] Running with JVM
> arguments: -Xms1g -Xmx1g -XX:NewRatio=1 -XX:+ResizeTLAB
> -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled
> -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC
> -XX:-OmitStackTraceInFastThrow
> -Dlog4j.configurationFile=file:///etc/graylog/server/log4j2.xml
> -Djava.library.path=/usr/share/graylog-server/lib/sigar
> -Dgraylog2.installation_source=rpm
> 2016-05-16T15:06:14.252-04:00 INFO [InputBufferImpl] Message journal is
> enabled.
> 2016-05-16T15:06:14.480-04:00 INFO [LogManager] Loading logs.
> 2016-05-16T15:06:14.579-04:00 INFO [LogManager] Logs loading complete.
> 2016-05-16T15:06:14.580-04:00 INFO [KafkaJournal] Initialized Kafka based
> journal at /var/lib/graylog-server/journal
> 2016-05-16T15:06:14.614-04:00 INFO [InputBufferImpl] Initialized
> InputBufferImpl with ring size <65536> and wait strategy
> , running 2 parallel message handlers.
> 2016-05-16T15:06:14.657-04:00 INFO [cluster] Cluster created with
> settings {hosts=[localhost:27017], mode=SINGLE,
> requiredClusterType=UNKNOWN, serverSelectionTimeout='3 ms',
> maxWaitQueueSize=5000}
> 2016-05-16T15:06:14.694-04:00 INFO [cluster] No server chosen by
> ReadPreferenceServerSelector{readPreference=primary} from cluster
> description ClusterDescription{type=UNKNOWN, connectionMode=SINGLE,
> all=[ServerDescription{address=localhost:27017, type=UNKNOWN,
> state=CONNECTING}]}. Waiting for 3 ms before timing out
> 2016-05-16T15:06:14.738-04:00 INFO [connection] Opened connection
> [connectionId{localValue:1, serverValue:93}] to localhost:27017
> 2016-05-16T15:06:14.740-04:00 INFO [cluster] Monitor thread successfully
> connected to server with description
> ServerDescription{address=localhost:27017, type=STANDALONE,
> state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 2, 6]},
> minWireVersion=0, maxWireVersion=4, maxDocumentSize=16777216,
> roundTripTimeNanos=694440}
> 2016-05-16T15:06:14.750-04:00 INFO [connection] Opened connection
> [connectionId{localValue:2, serverValue:94}] to localhost:27017
> 2016-05-16T15:06:15.005-04:00 INFO [NodeId] Node ID:
> b8f9b2e6-ce5f-451a-b8b4-4109281c831d
> 2016-05-16T15:06:15.106-04:00 INFO [node]
> [graylog-b8f9b2e6-ce5f-451a-b8b4-4109281c831d] version[2.3.2], pid[9867],
> build[b9e4a6a/2016-04-21T16:03:47Z]
> 2016-05-16T15:06:15.106-04:00 INFO [node]
> [graylog-b8f9b2e6-ce5f-451a-b8b4-4109281c831d] initializing ...
>
