Thanks all, that was it. I thought I had my firewall open properly, but apparently not.
On Monday, April 4, 2016 at 9:16:59 AM UTC-4, Jochen Schalanda wrote: > > Hi Jayica, > > Graylog is internally trying to connect the cluster nodes (including > itself) via HTTP on the rest_transport_uri. Please ensure that > http://52.78.189.238:12900/ is reachable from the Graylog node itself (as > Vincent already suggested). > > Cheers, > Jochen > > On Friday, 1 April 2016 20:27:06 UTC+2, Jayica wrote: >> >> Here is my Graylog conf file. Thanks for taking a look. >> >> # REST API listen URI. Must be reachable by other Graylog server nodes if >> you run a cluster. >> # When using Graylog Collectors, this URI will be used to receive >> heartbeat messages and must be accessible for all collectors. >> #rest_listen_uri = http://127.0.0.1:12900/ >> rest_listen_uri = http://0.0.0.0:12900/ >> >> # REST API transport address. Defaults to the value of rest_listen_uri. >> Exception: If rest_listen_uri >> # is set to a wildcard IP address (0.0.0.0) the first non-loopback IPv4 >> system address is used. >> # If set, this will be promoted in the cluster discovery APIs, so other >> nodes may try to connect on >> # this address and it is used to generate URLs addressing entities in the >> REST API. (see rest_listen_uri) >> # You will need to define this, if your Graylog server is running behind >> a HTTP proxy that is rewriting >> # the scheme, host name or URI. >> rest_transport_uri = http://52.78.189.238:12900/ >> > [...] >> >> >> >> On Tuesday, March 29, 2016 at 6:47:53 AM UTC-4, Jochen Schalanda wrote: >>> >>> Hi Jayica, >>> >>> the error message (and the stack trace in your first post) looks like >>> some problem with the internal communication of Graylog. >>> >>> Please post your Graylog configuration file. >>> >>> Cheers, >>> Jochen >>> >>> On Friday, 25 March 2016 19:20:45 UTC+1, Jayica wrote: >>>> >>>> The public ip is from my Graylog machine. I'm trying to test this on a >>>> single AWS instance. The only way i can successfully log into the Web UI >>>> is by defining the public ip there (rest_transport_uri = ) . This allows >>>> me to log on, but than i get the below exception in the logs which >>>> disallows an input connection. >>>> >>>> 2016-03-25T18:08:15.116Z ERROR [AnyExceptionClassMapper] Unhandled >>>> exception in REST resource >>>> java.net.SocketTimeoutException: connect timed out >>>> >>>> Is there any updated documentation anywhere on how exactly one is >>>> supposed to setup this beta version on a single AWS instance (yes, I'm >>>> trying the new v2.0-beta.1 version now and getting the same issue, which >>>> is >>>> quite frustrating). >>>> >>>> On Thursday, March 17, 2016 at 6:14:57 AM UTC-4, Vincent Amadou wrote: >>>>> >>>>> Did you find the problem ? >>>>> Very stupid question but is http://<my_public_ip>:12900/ reachable >>>>> from the Graylog machine ? >>>>> >>>> -- 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/d59e2522-0a22-45aa-8807-19168baae063%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
