Re: [graylog2] Re: not able to join Graylog with ES Clusters

I tried with that config. but still the same. I debugged with the Firefox Dev tools and in back this is trying to https://172.16.16.102:12900/system/cluster/node . and since this is HTTPS enabled and certificate error is thrown and blocking in that stage then if I manually open the above URL and

[graylog2] Enable https issues on v. 2.0 ...

I am unable to get ssl working properly and receive the following error message: We are experiencing problems connecting to the Graylog server running on *https://fqdn:12900//*. Please verify that the server is healthy and working correctly. This is the last response we received from the

[graylog2] Graylog nodes unable to communicate with each other

I've got a graylog cluster set up with two graylog server nodes on AWS. Both of the nodes function fine on their own, but don't see each other. The rest API endpoints are bound to their internal 10.x endpoint and both hosts can communicate with each other. When I look at the elasticsearch

[graylog2] Re: Switching to whitespace analyzer

Hi Jochen, I assume that the search functionality in the web interface uses one of the search endpoints (i.e. /search/universal/relative). Perhaps, the problem in my case is that the *search query itself is tokenized using the standard analyzer*. In theory, I assume that it should use the

[graylog2] Re: How to configure Graylog clusters in V-2.0 alpha

thank u jochen. -- 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

[graylog2] Re: Switching to whitespace analyzer

Thanks, Jochen. Any idea of when you willl release the build? Sincerely, Dilip M. On Tuesday, May 10, 2016 at 12:24:19 PM UTC-4, Jochen Schalanda wrote: > > Hi Dilip, > > the "field terms" are using the analyze endpoint internally, so they > currently are showing the wrong terms (will be fixed

[graylog2] Re: Graylog V2 web interface stuck on loading after login

Hi Jochen, Thanks very much for replying. I've managed to figure this one out. While I was getting the graylog logs, I noticed that there was a line about the cluster name - it can't have upper case characters in it. Once I changed this and restarted my services, everything is coming up

[graylog2] Re: How to setup tls security?

Hi Earest, please take a look at the documentation chapter about configuring the Graylog 2.0.0 web interface: http://docs.graylog.org/en/2.0/pages/configuring_webif.html In case you're using self-signed certificates, the following FAQ entry might also be interesting for you:

[graylog2] Re: Graylog stream

Hi Seba, I'm not sure what you're trying to accomplish. Please elaborate on your use case. Cheers, Jochen On Friday, 6 May 2016 11:47:14 UTC+2, Seba wrote: > > *Dear all,* > > > > > *How can I set a streaming rule, in order to not send a notification, when > access to the switch is not

[graylog2] Re: Switching to whitespace analyzer

Hi Dilip, the "field terms" are using the analyze endpoint internally, so they currently are showing the wrong terms (will be fixed in Graylog 2.0.1). Cheers, Jochen On Tuesday, 10 May 2016 17:52:35 UTC+2, Dilip Muthukrishnan wrote: > > Thanks, Jochen. However, does this bug affect the search

[graylog2] Re: Graylog V2 web interface stuck on loading after login

Hi Nathan, please tell us some details about your setup (e. g. if you're using HTTPS, if you're using some reverse proxy etc.). Cheers, Jochen On Monday, 9 May 2016 18:03:05 UTC+2, Nathan Hicks wrote: > > Hi, > > I'll have the Graylog logs in a minute, but for now, I've got this out of > the

[graylog2] "Empty" messages received from Graylog Collector

We are using Graylog2 v1.3.4 with Graylog Collector 0.4.1 to grab logs from our Windows machines. I have noticed an issue where some log entries are being replaced with the word "Empty" in the message field (all the other fields are correct). These are valid log entries which are not empty;

[graylog2] "Empty" log entries from Windows Event Logs

We are using Graylog2 v1.3.4 with GrayLog collector v0.4.1 on our Windows boxes to collect Windows Event Logs. I notice that on all of these Windows machines we are often (1 in 20) receiving log entries where the message field contains the text "Empty" instead of the proper entry. Valuable

Re: [graylog2] Re: Unable to send heartbeat to Graylog server: ConnectException: Connection refused

Hi Jochen, I copy the file line copying missing. I found the problem. I realized that I have two server-url. :( . Sorry for my fault. Thank you for your kindly attention 2016-05-10 15:24 GMT+03:00 Jochen Schalanda : > Hi Hasan, > > I think you're missing the server-url

[graylog2] Re: Unable to Upgrade Graylog from 1.3 to 2.0 Lauched from Readymade AMI

Hi Sharma, please read this chapter in the Graylog documentation about upgrading the virtual machine images (including the AMIs) to Graylog 2.0.0: http://docs.graylog.org/en/2.0/pages/installation/graylog_ctl.html#migrate-manually-from-1-x-to-2-0-x Cheers, Jochen On Tuesday, 10 May 2016

Re: [graylog2] Re: Unable to send heartbeat to Graylog server: ConnectException: Connection refused

Hi Hasan, I think you're missing the server-url setting ( https://github.com/Graylog2/collector/blob/0.4.2/config/collector.conf.example#L3-L4) in your Graylog Collector configuration file. Cheers, Jochen On Tuesday, 10 May 2016 13:30:18 UTC+2, hasan akgöz wrote: > > Hi Jochen > > My

Re: [graylog2] Re: Unable to send heartbeat to Graylog server: ConnectException: Connection refused

Hi Jochen My graylog-server version is 1.3.4-1 and collector version is 0.4.2-1. my collector config. It is as follows. collector-id = "file:/etc/graylog/collector/collector-id" inputs { local-syslog { type = "file" path = "/var/log/syslog" charset = "utf-8" content-splitter

[graylog2] Unable to Upgrade Graylog from 1.3 to 2.0 Lauched from Readymade AMI

Hi Team, We have setup Graylog 1.3 using readymade AWS EC2-AMI, Now we are planning to upgrade that to 2.0. but unfortunately we are unable to upgrade that Please help us getting it resolved. I have used below commands to upgrade graylog. *wget

[graylog2] Re: Unable to send heartbeat to Graylog server: ConnectException: Connection refused

Hi Hasan, please post the configuration of your Graylog Collector and tell us, which exact versions of Graylog and of the Graylog Collector you're using. Cheers, Jochen On Tuesday, 10 May 2016 12:32:29 UTC+2, hasan akgöz wrote: > > Hi Guys, > > Before running the graylog collector today gives

[graylog2] Re: Issue with source code of graylog2-rest-client

Hi Trisha, the classes in the org.graylog2.restroutes.generated.routes package are being automatically generated when running Maven (using the Maven Exec plugin). Please take a look at the .travis.yml file on the 1.3 branch ( https://github.com/Graylog2/graylog2-server/blob/1.3/.travis.yml) to

[graylog2] Re: Raw Log Dashboard Widget

Hi Ben, there is currently no simple message list widget for dashboards in Graylog. You can either file a feature request for this at https://github.com/Graylog2/graylog2-server/issues or try to create a custom plugin providing such a widget (see

[graylog2] Re: Can't see the new features in my graylog install after upgrade

In fact, I was using the omnibus package until the first beta, when the repository was created, after that I've been using the repository until now. So I just went from rc5 to 2.0.0-2, the only issue was that the -G flag considered the versions 2.0.0-2 and 2.0.0-1 older than the existant ones,

[graylog2] Raw Log Dashboard Widget

Hi, I'm pretty new to greylog2 I have a system all setup but I want to create a custom search and just output the raw logs into a dashboard widget. I guess a widget that shows me the last 10 lines from the live search would work. Is this possible? Am I just missing it in the GUI or do I need a