Hi Aman, this looks like a problem with the host name Elasticsearch (the embedded node in the Graylog server) announces on the network. According to your logs it announces the address 10.0.2.15:9350. Make sure that this is the correct address and that the other Elasticsearch nodes (192.168.33.10 and 192.168.33.11) can access this interface.
You can also override the announces host name using the elasticsearch_network_host or elasticsearch_network_publish_host setting (see https://github.com/Graylog2/graylog2-server/blob/1.3.2/misc/graylog2.conf#L179-L186 ). Cheers, Jochen On Friday, 8 January 2016 08:46:40 UTC+1, Aman Kumar wrote: > > Hi, > > I am using below setup: > Two vagrant boxes for elastic search* 192.168.33.10,192.168.33.11* > they have started fine: > > curl -XGET 'http://192.168.33.10:9200/_cluster/health?pretty=true' > > { > > "cluster_name" : "graylog-production", > > "status" : "green", > > "timed_out" : false, > > "number_of_nodes" : 2, > > "number_of_data_nodes" : 2, > > "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 > > } > > > On the third vagrant machine i am using graylog with below settings( > *192.168.33.12*): > > elasticsearch_cluster_name = graylog-production > > elasticsearch_discovery_zen_ping_multicast_enabled = false > > elasticsearch_discovery_zen_ping_unicast_hosts = 192.168.33.10:9300, > 192.168.33.11:9300 > > > > When i am running graylog-server i am getting below logs: > > 2016-01-08T07:45:09.038Z INFO [CmdLineTool] Loaded plugins: [Anonymous > Usage Statistics 1.1.1 > [org.graylog.plugins.usagestatistics.UsageStatsPlugin]] > > 2016-01-08T07:45:09.131Z INFO [CmdLineTool] Running with JVM arguments: > -Xms1g -Xmx1g -XX:NewRatio=1 -XX:PermSize=128m -XX:MaxPermSize=256m > -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled > -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC > -XX:-OmitStackTraceInFastThrow > -Dlog4j.configuration=file:///etc/graylog/server/log4j.xml > -Djava.library.path=/usr/share/graylog-server/lib/sigar > > 2016-01-08T07:45:12.952Z INFO [InputBufferImpl] Message journal is > enabled. > > 2016-01-08T07:45:13.162Z INFO [LogManager] Loading logs. > > 2016-01-08T07:45:13.244Z INFO [LogManager] Logs loading complete. > > 2016-01-08T07:45:13.244Z INFO [KafkaJournal] Initialized Kafka based > journal at /var/lib/graylog-server/journal > > 2016-01-08T07:45:13.261Z INFO [InputBufferImpl] Initialized > InputBufferImpl with ring size <65536> and wait strategy > <BlockingWaitStrategy>, running 2 parallel message handlers. > > 2016-01-08T07:45:13.479Z INFO [NodeId] Node ID: > 94270365-62d9-4028-a751-0b604f08de86 > > 2016-01-08T07:45:13.632Z INFO [node] [graylog2-server] version[1.7.1], > pid[6766], build[b88f43f/2015-07-29T09:54:16Z] > > 2016-01-08T07:45:13.638Z INFO [node] [graylog2-server] initializing ... > > 2016-01-08T07:45:13.729Z INFO [plugins] [graylog2-server] loaded > [graylog-monitor], sites [] > > 2016-01-08T07:45:16.398Z INFO [node] [graylog2-server] initialized > > 2016-01-08T07:45:16.475Z INFO [Version] HV000001: Hibernate Validator > 5.1.3.Final > > 2016-01-08T07:45:16.598Z INFO [ProcessBuffer] Initialized ProcessBuffer > with ring size <65536> and wait strategy <BlockingWaitStrategy>. > > 2016-01-08T07:45:18.444Z INFO [RulesEngineProvider] No static rules file > loaded. > > 2016-01-08T07:45:18.488Z INFO [OutputBuffer] Initialized OutputBuffer > with ring size <65536> and wait strategy <BlockingWaitStrategy>. > > 2016-01-08T07:45:19.654Z INFO [ServerBootstrap] Graylog server 1.2.2 > (91c7822) starting up. (JRE: Oracle Corporation 1.7.0_91 on Linux > 3.13.0-74-generic) > > 2016-01-08T07:45:19.699Z INFO [PeriodicalsService] Starting 23 > periodicals ... > > 2016-01-08T07:45:19.720Z INFO [Periodicals] Starting > [org.graylog2.periodical.ThroughputCalculator] periodical in [0s], polling > every [1s]. > > 2016-01-08T07:45:19.711Z INFO [node] [graylog2-server] starting ... > > 2016-01-08T07:45:19.724Z INFO [Periodicals] Starting > [org.graylog2.periodical.AlertScannerThread] periodical in [10s], polling > every [60s]. > > 2016-01-08T07:45:19.725Z INFO [Periodicals] Starting > [org.graylog2.periodical.BatchedElasticSearchOutputFlushThread] periodical > in [0s], polling every [1s]. > > 2016-01-08T07:45:19.746Z INFO [Periodicals] Starting > [org.graylog2.periodical.ClusterHealthCheckThread] periodical in [0s], > polling every [20s]. > > 2016-01-08T07:45:19.775Z INFO [Periodicals] Starting > [org.graylog2.periodical.ContentPackLoaderPeriodical] periodical, running > forever. > > 2016-01-08T07:45:19.782Z INFO [Periodicals] Starting > [org.graylog2.periodical.DeadLetterThread] periodical, running forever. > > 2016-01-08T07:45:19.791Z INFO [Periodicals] Starting > [org.graylog2.periodical.GarbageCollectionWarningThread] periodical, > running forever. > > 2016-01-08T07:45:19.809Z INFO [Periodicals] Starting > [org.graylog2.periodical.IndexerClusterCheckerThread] periodical in [0s], > polling every [30s]. > > 2016-01-08T07:45:19.811Z INFO [Periodicals] Starting > [org.graylog2.periodical.IndexRetentionThread] periodical in [0s], polling > every [300s]. > > 2016-01-08T07:45:19.812Z INFO [IndexRetentionThread] Elasticsearch > cluster not available, skipping index retention checks. > > 2016-01-08T07:45:19.813Z INFO [Periodicals] Starting > [org.graylog2.periodical.IndexRotationThread] periodical in [0s], polling > every [10s]. > > 2016-01-08T07:45:19.813Z INFO [Periodicals] Starting > [org.graylog2.periodical.NodePingThread] periodical in [0s], polling every > [1s]. > > 2016-01-08T07:45:19.823Z INFO [Periodicals] Starting > [org.graylog2.periodical.StreamThroughputCounterManagerThread] periodical > in [0s], polling every [1s]. > > 2016-01-08T07:45:19.858Z INFO [Periodicals] Starting > [org.graylog2.periodical.VersionCheckThread] periodical in [300s], polling > every [1800s]. > > 2016-01-08T07:45:19.862Z INFO [Periodicals] Starting > [org.graylog2.periodical.ThrottleStateUpdaterThread] periodical in [1s], > polling every [1s]. > > 2016-01-08T07:45:19.863Z INFO [Periodicals] Starting > [org.graylog2.events.ClusterEventPeriodical] periodical in [0s], polling > every [1s]. > > 2016-01-08T07:45:19.880Z INFO [Periodicals] Starting > [org.graylog2.events.ClusterEventCleanupPeriodical] periodical in [0s], > polling every [300s]. > > 2016-01-08T07:45:19.894Z INFO [Periodicals] Starting > [org.graylog2.periodical.ClusterIdGeneratorPeriodical] periodical, running > forever. > > 2016-01-08T07:45:19.908Z INFO [Periodicals] Starting > [org.graylog2.periodical.PurgeExpiredCollectorsThread] periodical in [0s], > polling every [3600s]. > > 2016-01-08T07:45:19.909Z INFO [Periodicals] Starting > [org.graylog2.periodical.IndexRangesMigrationPeriodical] periodical, > running forever. > > 2016-01-08T07:45:19.933Z INFO [IndexerClusterCheckerThread] Indexer not > fully initialized yet. Skipping periodic cluster check. > > 2016-01-08T07:45:19.937Z WARN [ClusterConfigServiceImpl] Couldn't find > cluster config of type > org.graylog2.periodical.IndexRangesMigrationPeriodical.MongoIndexRangesMigrationComplete > > 2016-01-08T07:45:20.029Z INFO [PeriodicalsService] Not starting > [org.graylog2.periodical.UserPermissionMigrationPeriodical] periodical. Not > configured to run on this node. > > 2016-01-08T07:45:20.032Z INFO [Periodicals] Starting > [org.graylog2.periodical.AlarmCallbacksMigrationPeriodical] periodical, > running forever. > > 2016-01-08T07:45:20.048Z INFO [Periodicals] Starting > [org.graylog.plugins.usagestatistics.UsageStatsNodePeriodical] periodical > in [300s], polling every [21600s]. > > 2016-01-08T07:45:20.048Z INFO [Periodicals] Starting > [org.graylog.plugins.usagestatistics.UsageStatsClusterPeriodical] > periodical in [300s], polling every [21600s]. > > 2016-01-08T07:45:20.135Z INFO [transport] [graylog2-server] bound_address > {inet[/0:0:0:0:0:0:0:0:9350]}, publish_address {inet[/10.0.2.15:9350]} > > 2016-01-08T07:45:20.188Z INFO [discovery] [graylog2-server] > graylog-production/7iQ5shwgTqWg1wAxehPLSA > > 2016-01-08T07:45:20.473Z INFO [Reflections] Reflections took 654 ms to > scan 1 urls, producing 2 keys and 2 values > > 2016-01-08T07:45:23.190Z WARN [discovery] [graylog2-server] waited for 3s > and no initial state was set by the discovery > > 2016-01-08T07:45:23.191Z INFO [node] [graylog2-server] started > > 2016-01-08T07:45:23.338Z INFO [zen] [graylog2-server] failed to send join > request to master > [[Bes][NPuV7eQxRNqeAPwhTcaTZw][vagrant-ubuntu-trusty-64][inet[/192.168.33.11:9300]]], > > reason > [RemoteTransportException[[Bes][inet[/192.168.33.11:9300]][internal:discovery/zen/join]]; > > nested: ConnectTransportException[[graylog2-server][inet[/10.0.2.15:9350]] > connect_timeout[30s]]; nested: ConnectException[Connection refused: / > 10.0.2.15:9350]; ] > > 2016-01-08T07:45:26.378Z INFO [zen] [graylog2-server] failed to send join > request to master > [[Bes][NPuV7eQxRNqeAPwhTcaTZw][vagrant-ubuntu-trusty-64][inet[/192.168.33.11:9300]]], > > reason > [RemoteTransportException[[Bes][inet[/192.168.33.11:9300]][internal:discovery/zen/join]]; > > nested: ConnectTransportException[[graylog2-server][inet[/10.0.2.15:9350]] > connect_timeout[30s]]; nested: ConnectException[Connection refused: / > 10.0.2.15:9350]; ] > > 2016-01-08T07:45:27.600Z INFO [RestApiService] Adding security context > factory: <org.graylog2.security.ShiroSecurityContextFactory@10bd3bef> > > 2016-01-08T07:45:27.642Z INFO [RestApiService] Started REST API at < > http://127.0.0.1:12900/> > > *2016-01-08T07:45:28.193Z INFO [IndexerSetupService] Checking > Elasticsearch HTTP API at http://192.168.33.10:9200/ > <http://192.168.33.10:9200/>* > > *2016-01-08T07:45:28.692Z INFO [IndexerSetupService] Checking > Elasticsearch HTTP API at http://192.168.33.11:9200/ > <http://192.168.33.11:9200/>* > > *2016-01-08T07:45:28.704Z WARN [IndexerSetupService] Could not connect to > Elasticsearch* > > 2016-01-08T07:45:28.705Z INFO [IndexerSetupService] If you're using > multicast, check that it is working in your network and that Elasticsearch > is accessible. Also check that the cluster name setting is correct. > > 2016-01-08T07:45:28.706Z INFO [IndexerSetupService] See > http://docs.graylog.org/en/1.2/pages/configuring_es.html for details. > > 2016-01-08T07:45:28.708Z INFO [ServerBootstrap] Services started, startup > times in ms: {OutputSetupService [RUNNING]=27, DashboardRegistryService > [RUNNING]=29, MetricsReporterService [RUNNING]=29, JournalReader > [RUNNING]=34, KafkaJournal [RUNNING]=38, BufferSynchronizerService > [RUNNING]=39, InputSetupService [RUNNING]=41, PeriodicalsService > [RUNNING]=355, RestApiService [RUNNING]=7943, IndexerSetupService > [RUNNING]=9000} > > 2016-01-08T07:45:28.712Z INFO [ServiceManagerListener] Services are > healthy > > 2016-01-08T07:45:28.714Z INFO [InputSetupService] Triggering launching > persisted inputs, node transitioned from Uninitialized?[LB:DEAD] to > Running?[LB:ALIVE] > > 2016-01-08T07:45:28.716Z INFO [ServerBootstrap] Graylog server up and > running. > > 2016-01-08T07:45:29.399Z INFO [zen] [graylog2-server] failed to send join > request to master > [[Bes][NPuV7eQxRNqeAPwhTcaTZw][vagrant-ubuntu-trusty-64][inet[/192.168.33.11:9300]]], > > reason > [RemoteTransportException[[Bes][inet[/192.168.33.11:9300]][internal:discovery/zen/join]]; > > nested: ConnectTransportException[[graylog2-server][inet[/10.0.2.15:9350]] > connect_timeout[30s]]; nested: ConnectException[Connection refused: / > 10.0.2.15:9350]; ] > > 2016-01-08T07:45:32.414Z INFO [zen] [graylog2-server] failed to send join > request to master > [[Bes][NPuV7eQxRNqeAPwhTcaTZw][vagrant-ubuntu-trusty-64][inet[/192.168.33.11:9300]]], > > reason > [RemoteTransportException[[Bes][inet[/192.168.33.11:9300]][internal:discovery/zen/join]]; > > nested: ConnectTransportException[[graylog2-server][inet[/10.0.2.15:9350]] > connect_timeout[30s]]; nested: ConnectException[Connection refused: / > 10.0.2.15:9350]; ] > > 2016-01-08T07:45:35.438Z INFO [zen] [graylog2-server] failed to send join > request to master > [[Bes][NPuV7eQxRNqeAPwhTcaTZw][vagrant-ubuntu-trusty-64][inet[/192.168.33.11:9300]]], > > reason > [RemoteTransportException[[Bes][inet[/192.168.33.11:9300]][internal:discovery/zen/join]]; > > nested: ConnectTransportException[[graylog2-server][inet[/10.0.2.15:9350]] > connect_timeout[30s]]; nested: ConnectException[Connection refused: / > 10.0.2.15:9350]; ] > > > Please help me to connect graylog to elastic search > > > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/06fbbeda-60b0-49a9-b5c5-7967b783e4eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
