Hey Jochen,
Apologies for missing this. As i recall, it wasn't until i shutdown
Graylog and restarted my server instance that the old input finally cleared
out.
Regards,
J
On Friday, April 22, 2016 at 5:59:37 PM UTC-4, Jochen Schalanda wrote:
>
> Hi Jayica,
>
> would you mind tel
Thanks Jochen. This was all very helpful. Problem solved.
On Sunday, April 17, 2016 at 7:04:36 PM UTC-4, Jayica wrote:
>
> I just installed Graylog 2.0.0-beta.3 and created an input (which was
> working fine until I added an elastic IP to my Graylog AWS instance - while
&g
to just wipe this out.
On Sunday, April 17, 2016 at 7:04:36 PM UTC-4, Jayica wrote:
>
> I just installed Graylog 2.0.0-beta.3 and created an input (which was
> working fine until I added an elastic IP to my Graylog AWS instance - while
> it was up and running). Now I can't st
I just installed Graylog 2.0.0-beta.3 and created an input (which was
working fine until I added an elastic IP to my Graylog AWS instance - while
it was up and running). Now I can't stop or delete the input.
Error upon attempting to stop the input:
Input 'Graylog Lab Server - Linux' could not
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 res
h should be applied on
# the first start of Graylog.
content_packs_auto_load = grok-patterns.json
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 wit
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
I am able to log onto my Graylog web ui and see the admin/password page
without issue (log shows "Graylog server up and running"). However, the
minute i log in through the web ui, i get the following exceptions in the
logs and cannot configure any inputs. I am running graylog on a single AWS
After displaying the login page, it than fails with this:
We are experiencing problems connecting to the Graylog server running on
*http://127.0.0.1:12900//*. Please verify that the server is healthy and
working correctly.
Graylog service is up and running though (on AWS instance - Ubuntu
