[graylog2] Re: How to solve this alert? Notification condition [NO_MASTER] has been fixed.

Hello Jochen, But the problem of disk space is from yesterday because a vmware datastore problem that is already solved. But I want to solve the alert "NO MASTER fixed" that appears till the first day... Thanks El jueves, 2 de febrero de 2017, 15:22:58 (UTC+1), Jochen Schalanda escribió: > >

[graylog2] Monitoring Windows DHCP Server Activity

I set up a Graylog 2.1.2 server by deploying the downloadable OVA from graylog.org. I'm trying to monitor a Windows 2008 R2 server with the DHCP role installed. The DHCP server deposits activity data into log files at C:\Windows\System32\dhcp\DhcpSrvLog-*.log. I have collector-sidecar and

[graylog2] Re: Indices and edit Extractor page timing out

Hi This is still a big issue for me. Is there anything I can do? Is there any more information I can provide to get help? On Wednesday, December 14, 2016 at 10:46:36 AM UTC-5, Steve Kuntz wrote: > > Hi, > > Has anyone else seen this behavior? Everything works well until I hit the > Indices

[graylog2] Re: [ANN] Graylog 2.2.0-rc.1 has been released

Graylog is perfect, it only needs more customization and it will beat any classic Elasticsearch with kibana... when do you plan working on more customizable dashboards like Kibana? -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To

[graylog2] Unable to connect elastic search

Hi, I am configuring graylog in my pc, I am unable to connect elasticserach server from graylog Exception: com.google.common.util.concurrent.UncheckedExecutionException: ClusterBlockException[blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];] at

[graylog2] Re: Source Name is not displayed.

Hi Sridhar, Which GELF appender are you using? Did you configure a GELF UDP or a GELF TCP input in Graylog? How did you configure these inputs? Did you check your firewall rules to allow access on port 12201/tcp or 12201/udp? Cheers, Jochen On Thursday, 2 February 2017 16:21:08 UTC+1, Sridhar

[graylog2] Re: Nodes with too long GC pauses

Hi Nitzan, please post the configuration and logs of all Graylog nodes and a description of your hardware. Cheers, Jochen On Thursday, 2 February 2017 17:18:12 UTC+1, Nitzan Haimovich wrote: > > Hi all, > > I'm getting this message (*Nodes with too long GC pauses*) on my Graylog > cluster. I

[graylog2] Re: javax.net.ssl.SSLPeerUnverifiedException: Hostname 10.22.5.24 not verified - https

Hi Giwenn, what are the attributes of your self-signed certificate, especially the CommonName (CN) and optionally the AltSubjName? In your first message, it looks like it was CN=10.22.5.24:9000, which is wrong (it has to be the host name of the Graylog node, i. e. CN=10.22.5.24 or

[graylog2] Nodes with too long GC pauses

Hi all, I'm getting this message (*Nodes with too long GC pauses*) on my Graylog cluster. I saw many people were posting about it but not a single thread with solutions for how to solve/fix/approach it. I would be glad for any help. My cluster - 3 Graylog instances, each one with 8 cores and

[graylog2] Re: javax.net.ssl.SSLPeerUnverifiedException: Hostname 10.22.5.24 not verified - https

Hi Jochen, Here are the commands that I pass to put my server graylog in HTTPS: 1- openssl req -x509 -days 7300 -nodes -newkey rsa:2048 -keyout graylogkey.pem -out graycert.pem 2- openssl pkcs8 -in graylogkey.pem -topk8 -nocrypt -out graykey.pem 3- configuration this server.conf:

[graylog2] Source Name is not displayed.

Hi, I am very new to graylog. I am using following configuration, Virtualbox version: Version 5.1.14 r112924 (Qt5.6.2) Graylog OVA file: graylog-2.1.3-1 I am able to open Graylog web interface with out any issue and I am using the following logging configuration for sending messages from my

Re: [graylog2] Re: Error on start

That worked!! Thank you for all your help! Seems like we're all good now! On Thursday, February 2, 2017 at 4:18:54 PM UTC+2, Jochen Schalanda wrote: > > Hi Tzvi, > > > On Thursday, 2 February 2017 15:14:46 UTC+1, Tzvi Moshe Arnstein wrote: >> >> However I'm getting an errr in the browser now: >>

[graylog2] Re: How to solve this alert? Notification condition [NO_MASTER] has been fixed.

Hi Aitor, these logs clearly show that your Elasticsearch cluster is not healthy: It ran out of disk space multiple times and it can't keep up with indexing messages sent by Graylog (full task queues etc.). You'll have to provide more hardware (esp. more memory, at least 4 GiB) to your

Re: [graylog2] Re: Error on start

Hi Tzvi, On Thursday, 2 February 2017 15:14:46 UTC+1, Tzvi Moshe Arnstein wrote: > > However I'm getting an errr in the browser now: > https://gyazo.com/2398b5bd57aa1e860192ec445ae04ee6 the IP there is the > internal IP > Try setting web_endpoint_uri to http://104.196.203.4:9000/api/. This is

Re: [graylog2] Re: Error on start

Hi Jochen, Bingo! I changed to 0.0.0.0 and now it worked! Also seems that my firewall was blocking connections on 9000 so I updated that too. However I'm getting an errr in the browser now: https://gyazo.com/2398b5bd57aa1e860192ec445ae04ee6 the IP there is the internal IP Thank you On

Re: [graylog2] Re: Error on start

Hi Tzvi, On Thursday, 2 February 2017 14:40:13 UTC+1, Tzvi Moshe Arnstein wrote: > > Im not sure what you mean? This is the instance running graylog and this > is the assigned IP, unless I have to do additional configuration to make > this IP work? > The IP addresses set up on the machine are

Re: [graylog2] Re: Error on start

Hi, Im not sure what you mean? This is the instance running graylog and this is the assigned IP, unless I have to do additional configuration to make this IP work? Can you explain? Thanks you for your patience! On Thursday, February 2, 2017 at 3:31:15 PM UTC+2, Jochen Schalanda wrote: > > Hi

[graylog2] Re: You are running an outdated Graylog version even after upgrade from 2.1.x to 2.1.3

Hi Sinai, are you running multiple Graylog nodes? Have all been updated? Did you restart all Graylog nodes after upgrading the files via the package management system of your operating system? Cheers, Jochen On Thursday, 2 February 2017 13:03:15 UTC+1, Sinai Rijkov wrote: > > Hi, > Yes I

Re: [graylog2] Re: Error on start

Hi Tzvi, you have to use an IP address or hostname in rest_listen_uri an web_listen_uri, which has been setup *on the machine* running Graylog. Cheers, Jochen On Thursday, 2 February 2017 14:19:05 UTC+1, Tzvi Moshe Arnstein wrote: > > Hi, > Thats the IP assigned to the instance in GCP > When I

[graylog2] Re: How to solve this alert? Notification condition [NO_MASTER] has been fixed.

Hi Aitor, On Thursday, 2 February 2017 14:06:55 UTC+1, Aitor Mendoza wrote: > > *For example: (/var/log/graylog/elasticsearch/graylog.log)* > Please post the *complete* logs of your Graylog and Elasticsearch nodes as text (for example as an attachment to this discussion). Did you run out of

[graylog2] Re: javax.net.ssl.SSLPeerUnverifiedException: Hostname 10.22.5.24 not verified - https

Hi Giwenn, On Thursday, 2 February 2017 14:20:17 UTC+1, Giwenn Launay wrote: > > You have another solution ??? > What didn't work with the one outlined in the Graylog documentation? Cheers, Jochen -- You received this message because you are subscribed to the Google Groups "Graylog Users"

[graylog2] Re: javax.net.ssl.SSLPeerUnverifiedException: Hostname 10.22.5.24 not verified - https

You have another solution ??? For more than 2 weeks I have been trying to solve this error Thank =) -- 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

Re: [graylog2] Re: Error on start

Hi, Thats the IP assigned to the instance in GCP When I run: host myip.opendns.com resolver1.opendns.com *This is the response* Using domain server: Name: resolver1.opendns.com Address: 208.67.222.222#53 Aliases: myip.opendns.com has address 104.196.203.4 Host myip.opendns.com not found:

[graylog2] Re: How to solve this alert? Notification condition [NO_MASTER] has been fixed.

Sorry, *For example: (/var/log/graylog/elasticsearch/graylog.log)*

[graylog2] Re: javax.net.ssl.SSLPeerUnverifiedException: Hostname 10.22.5.24 not verified - https

Yes, I added GRAYLOG_SERVER_JAVA_OPTS= "-Djavax.net.ssl.trustStore=/etc/graylog/certificate/cacerts.jks" in the /etc/sysconfig/graylog-server And I did not change the password by default Thank you for the speed of your answer -- You received this message because you are subscribed to the

[graylog2] Re: javax.net.ssl.SSLPeerUnverifiedException: Hostname 10.22.5.24 not verified - https

Yes, I added GRAYLOG_SERVER_JAVA_OPTS= "-Djavax.net.ssl.trustStore=/etc/graylog/certificate/cacerts.jks" in the /etc/sysconfig/graylog-server And I did not change the password by default Thank you for the speed of your answer On Thursday, February 2, 2017 at 12:55:42 PM UTC+1, Jochen

[graylog2] Re: You are running an outdated Graylog version even after upgrade from 2.1.x to 2.1.3

Hi, Yes I know it, but its coming back. :) Pretty annoying when all is "green" and OK. On Wednesday, February 1, 2017 at 5:42:54 PM UTC+2, Jochen Schalanda wrote: > > Hi Sinai, > > you can close/delete that notification by clicking on the 'X' in the upper > right corner of the notification

[graylog2] Re: How to solve this alert? Notification condition [NO_MASTER] has been fixed.

Hi Aitor, please post the logs of your Graylog and ES nodes: http://docs.graylog.org/en/2.1/pages/configuration/file_location.html#deb-package Cheers, Jochen -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group

[graylog2] Re: javax.net.ssl.SSLPeerUnverifiedException: Hostname 10.22.5.24 not verified - https

Hi Giwenn, you have to add your self-signed certificate to the JVM's trust store: http://docs.graylog.org/en/2.1/pages/configuration/https.html#adding-a-self-signed-certificate-to-the-jvm-trust-store Cheers, Jochen On Thursday, 2 February 2017 12:43:47 UTC+1, Giwenn Launay wrote: > > Hello, >

[graylog2] javax.net.ssl.SSLPeerUnverifiedException: Hostname 10.22.5.24 not verified - https

Hello, I'll contact you because I have a problem with the https of my Graylog server. I generated the self-signed certificate and added the certificate to the JVM Here is my error message: You can not call https://10.22.5.24:9000/api/system/metrics/multiple on node <88d73a41-f393-43db-80e6-

[graylog2] Re: How to solve this alert? Notification condition [NO_MASTER] has been fixed.

Hi, *graylog.conf on GRAYLOG SERVER:* is_master = true node_id_file = /var/opt/graylog/graylog-server-node-id rest_listen_uri = http://0.0.0.0:9000/api

[graylog2] Re: How to solve this alert? Notification condition [NO_MASTER] has been fixed.

Hi Aitor, please post the logs of your Graylog node, your Graylog configuration (including JVM settings), and some details about the hardware of the machine running Graylog. Cheers, Jochen On Thursday, 2 February 2017 07:57:34 UTC+1, Aitor Mendoza wrote: > > Hello, > > Since I configured my