Hi Shrawan,
as I said, make sure that all Elasticsearch nodes (including Graylog) in
your cluster can communicate with each other. The IP addresses also look
vastly different, so maybe you want to explicitly set those for each
Elasticsearch node.
On a side note, you might want to use the same Elasticsearch version
everywhere (i. e. ES 1.7.5).
Cheers,
Jochen
On Thursday, 21 April 2016 09:31:04 UTC+2, Shrawan Bhagwat wrote:
>
> Hi Jochen,
>
> I am not getting any error message in Elasticsearch logs on both the
> servers.
> Server1:
> [2016-04-20 18:34:36,386][INFO ][bootstrap ] max_open_files
> [65536]
> [2016-04-20 18:34:36,695][INFO ][node ] [Master 228]
> version[1.7.2], pid[2149], build[e43676b/2015-09-14T09:49:53Z]
> [2016-04-20 18:34:36,695][INFO ][node ] [Master 228]
> initializing ...
> [2016-04-20 18:34:37,100][INFO ][plugins ] [Master 228]
> loaded [], sites [head, bigdesk]
> [2016-04-20 18:34:37,213][INFO ][env ] [Master 228]
> using [1] data paths, mounts [[/smapp (/dev/mapper/vg02-lvol01)]], net
> usable_space [23.5gb], net total_space [39.2gb], types [ext4]
> [2016-04-20 18:34:46,644][INFO ][node ] [Master 228]
> initialized
> [2016-04-20 18:34:46,645][INFO ][node ] [Master 228]
> starting ...
> [2016-04-20 18:34:46,763][INFO ][transport ] [Master 228]
> bound_address {inet[/192.168.178.228:9300]}, publish_address {inet[/
> 192.168.178.228:9300]}
> [2016-04-20 18:34:46,779][INFO ][discovery ] [Master 228]
> UltimatixDev/OFXuALtwQOGN7GU4IdL95Q
>
> server2:
> [2016-04-20 18:15:18,642][INFO ][bootstrap ] max_open_files
> [65536]
> [2016-04-20 18:15:18,894][INFO ][node ] [Master 149]
> version[1.7.5], pid[12297], build[00f95f4/2016-02-02T09:55:30Z]
> [2016-04-20 18:15:18,894][INFO ][node ] [Master 149]
> initializing ...
> [2016-04-20 18:15:19,081][INFO ][plugins ] [Master 149]
> loaded [], sites [bigdesk, head]
> [2016-04-20 18:15:19,143][INFO ][env ] [Master 149]
> using [1] data paths, mounts [[/smapp (/dev/mapper/vg02-lvol01)]], net
> usable_space [7gb], net total_space [39.2gb], types [ext4]
> [2016-04-20 18:15:23,577][INFO ][node ] [Master 149]
> initialized
> [2016-04-20 18:15:23,577][INFO ][node ] [Master 149]
> starting ...
> [2016-04-20 18:15:23,658][INFO ][transport ] [Master 149]
> bound_address {inet[/10.40.4.149:9300]}, publish_address {inet[/
> 10.40.4.149:9300]}
> [2016-04-20 18:15:23,672][INFO ][discovery ] [Master 149]
> UltimatixDev/PziIysSaTy-lC57MwaJi5g
> [2016-04-20 18:15:53,672][WARN ][discovery ] [Master 149]
> waited for 30s and no initial state was set by the discovery
> [2016-04-20 18:15:53,683][INFO ][http ] [Master 149]
> bound_address {inet[/10.40.4.149:9200]}, publish_address {inet[/
> 10.40.4.149:9200]}
> [2016-04-20 18:15:53,684][INFO ][node ] [Master 149]
> started
>
>
> Please Guide.
>
> Regards,
> Shrawan
>
> On Wednesday, 20 April 2016 19:59:41 UTC+5:30, Jochen Schalanda wrote:
>>
>> Hi Shrawan,
>>
>> looks like your Elasticsearch cluster or at least the communication
>> within the cluster is broken. Please check the logs of your Elasticsearch
>> nodes for error messages and make sure, that each node of the Elasticsearch
>> cluster is able to communicate with the rest of the cluster.
>>
>> Cheers,
>> Jochen
>>
>> On Wednesday, 20 April 2016 15:17:24 UTC+2, Shrawan Bhagwat wrote:
>>>
>>> Hi All,
>>>
>>> I am using graylog-1.3.3 ,elasticsearch-1.7.5 and Logstash-2.2.2.
>>>
>>> I am getting Reason: There was a problem with your search. We expected
>>> HTTP 200, but got a HTTP 500. on the Graylog UI.
>>>
>>> I have found following errors in graylog log file:
>>>
>>> 2016-04-20 18:39:18,019 ERROR:
>>> org.graylog2.periodical.AlertScannerThread - Skipping alert check that
>>> threw an exception.
>>> org.elasticsearch.discovery.MasterNotDiscoveredException: waited for
>>> [30s]
>>> at
>>> org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$4.onTimeout(TransportMasterNodeOperationAction.java:164)
>>> at
>>> org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:231)
>>> at
>>> org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:560)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>> 2016-04-20 18:39:23,467 WARN :
>>> org.elasticsearch.discovery.zen.ping.unicast - [Graylog2 Node 228] failed
>>> to send ping to [[#zen_unicast_2#][CDCUSMDECAPP01][inet[/10.40.4.149:9300]]]
>>> org.elasticsearch.transport.SendRequestTransportException:
>>> [][inet[/10.40.4.149:9300]][internal:discovery/zen/unicast_gte_1_4]
>>> at
>>> org.elasticsearch.transport.TransportService.sendRequest(TransportService.java:286)
>>> at
>>> org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing.sendPingRequestTo14NodeWithFallback(UnicastZenPing.java:431)
>>> at
>>> org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing.sendPings(UnicastZenPing.java:413)
>>> at
>>> org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing.ping(UnicastZenPing.java:219)
>>> at
>>> org.elasticsearch.discovery.zen.ping.ZenPingService.ping(ZenPingService.java:146)
>>> at
>>> org.elasticsearch.discovery.zen.ping.ZenPingService.pingAndWait(ZenPingService.java:124)
>>> at
>>> org.elasticsearch.discovery.zen.ZenDiscovery.findMaster(ZenDiscovery.java:1007)
>>> at
>>> org.elasticsearch.discovery.zen.ZenDiscovery.innerJoinCluster(ZenDiscovery.java:361)
>>> at
>>> org.elasticsearch.discovery.zen.ZenDiscovery.access$6100(ZenDiscovery.java:86)
>>> at
>>> org.elasticsearch.discovery.zen.ZenDiscovery$JoinThreadControl$1.run(ZenDiscovery.java:1384)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>> Caused by: org.elasticsearch.transport.NodeNotConnectedException:
>>> [][inet[/10.40.4.149:9300]] Node not connected
>>> at
>>> org.elasticsearch.transport.netty.NettyTransport.nodeChannel(NettyTransport.java:964)
>>> at
>>> org.elasticsearch.transport.netty.NettyTransport.sendRequest(NettyTransport.java:656)
>>> at
>>> org.elasticsearch.transport.TransportService.sendRequest(TransportService.java:276)
>>> ... 12 more
>>>
>>> Earlier it was working fine.
>>>
>>> Please Guide.
>>>
>>> Regards,
>>> Shrawan
>>>
>>>
--
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/dba63bed-3ecc-4bc3-8d3a-2d48f0d9032c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
