[graylog2] Re: graylog2 connection to elasticsearch

Hi Ankur, I think the port no 9350 is already in us on your graylog server by some other application. Also check the firewall setting in cent OS ( port should be open from graylog server to elastisearch server ) Regards, Ankit Mittal -- You received this message because you are

Re: [graylog2] graylog2 connection to elasticsearch

Hey Ankit, I was irritated by this too. The server log contains several attempts to get it up and running. If you scroll down to the end you will see that it is able to bind to tcp/9350, but it fails to join the cluster. Kr, D. On 30.07.2014, at 09:58, Ankit Mittal

[graylog2] Re: graylog2 connection to elasticsearch

Hi Ankur, Please change the below setting in graylog2.conf elasticsearch_discovery_zen_ping_unicast_hosts = 172.16.2.254:9200 to elasticsearch_discovery_zen_ping_unicast_hosts = 172.16.2.254:9300 Regards, Ankit Mittal -- You received this message because you are subscribed to

[graylog2] Re: Export log

But that is not really an option i think... because we have 3 Graylog servers in production and a load balancer in front... so every logging part can enter on a different node :( We don't want a single point of failure (the syslog collector). On Tuesday, July 29, 2014 5:14:17 PM UTC+2, Scipio

[graylog2] Re: graylog2 connection to elasticsearch

Hi Ankur, Please follow the below steps : 1) Stop all services ( elasticsearch , graylog and graylog UI ) 2) Login to your elasticsearch server and clean the data folder and use the below elasticsearch.yml file Also change the */smApp/LMS/ElasticSearch/elasticsearch-0.90.10 *to your

[graylog2] Re: Graylog High availability Set Up

Hi Arie, I am using Two master node for handling *failover* condition. If my master node is down . data node will work or not ? Regards, Ankit Mittal -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop

[graylog2] Re: [ANNOUNCE] Graylog2 v0.20.6 has been released

Hi Bernd, is it possible do update my current instance of graylog2 (0.20.1) directly to 0.20.6 without losing any data/configuration? Is there anything I have to be aware of? Thanks, Denny Am Freitag, 18. Juli 2014 16:51:55 UTC+2 schrieb Bernd Ahlers: Hey everybody, a new bug fix

Re: [graylog2] graylog2 connection to elasticsearch

Hey Ankit, thanks for spotting this. This should help, yes. 9200 is the HTTP port of elasticsearch, we are using the binary protocol to connect to the elasticsearch cluster so port 9300 is correct. Kr, D. On 30.07.2014, at 10:23, Ankit Mittal ankit.lnc...@gmail.com wrote: Hi Ankur,

[graylog2] Re: Design question concerning Inputs

Hi Arie, how did you set up your configuration? One input for everything or did you seperate anything? Denny Am Mittwoch, 2. Juli 2014 16:08:25 UTC+2 schrieb Arie: Hi all, I am working on our production cluster. We want to get log-files from different systems with different

[graylog2] Re: UTF-8, syslog input

Please explain in detail what is the solution? I have similiar problem. I pick up logs from win7x64rus. Russian symbols in string looks like that -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving

[graylog2] encoding in Win7 russian logs

All logs from russian win7 is unreadble. :( string looks like that: 2014-07-30 15:06:39.222 igor.local.puls Service_Control_Manager: 7036: �� �� ��- WinHTTP �� �� ��

Re: [graylog2] Searching in previously closed indices

Hello, I think the problem is that Graylog2 can't tell if you opened that old index manually or if it was already open. Could you please try to open the index by using the Graylog2 web interface? To do that, click on System - Indices and open the closed index you want to use for searching.

[graylog2] Re: Configure Graylog service failure mail alert

Hi,, I am monitoring ES with a Nagios/Check_mk combination. Here is a plugin that can be used for monitoring ES: https://github.com/anchor/nagios-plugin-elasticsearch You could let the check_mk agent check on the graylog services. A. On Saturday, July 26, 2014 8:57:30 AM UTC+2, Ankit Mittal

[graylog2] Re: Graylog High availability Set Up

Thanks Ankit,, On Wednesday, July 30, 2014 12:18:37 PM UTC+2, Ankit Mittal wrote: Hi Arie, Thank you very much for sharing your comment on this. I was facing the split brain problem in my above LMS configuration in which i have only two elasticsearch node both are master + data . It is

[graylog2] Re: UTF-8, syslog input

Hi! It's a pretty easy solution, there is a some details. 1. You need a logstash - download it from http://logstash.net, or find a package for your OS 2. Next, create include in logstash's conf.d directory (in my case, /etc/logstash/conf.d/some.conf), you can use something like this: $ cat

Re: [graylog2] Re: Design question concerning Inputs

Hi! Generally speaking: If your log senders need special treatment (i.e. if you need to set up different extractors), then use different inputs. If you send gelf directly, you are generally ok with one input. Syslog-like inputs often need special extractors, so in those cases you have special

Re: [graylog2] Searching in previously closed indices

Hello Edmundo, thanks for the prompt reply. Opening the closed indices in question in the web interface is not possible either, so I will open an issue with the information you requested, albeit that'll take some time. Here's the general outline: If elasticsearch_max_number_of_indices in

Re: [graylog2] Searching in previously closed indices

Here's the issue: https://github.com/Graylog2/graylog2-server/issues/640 https://github.com/Graylog2/graylog2-server/issues/640More elaborate, and I had to correct some observations as I tested it a few more times. Regards, J. On Thursday, July 31, 2014 11:58:20 AM UTC+9, J John wrote: