Sounds weird, but I'm glad that it's working now. Please write if it happens
again, so we can look more into it.
Regards,
Edmundo
> On 28 Apr 2016, at 16:17, David Gerdeman wrote:
>
> I guess it was just some lag in the update process...When I went back to the
> webpage to check for JS errors
I guess it was just some lag in the update process...When I went back to
the webpage to check for JS errors and the like, every input I created was
in the list, with most of them in the failed state because the port was
taken by the first instance to start. Looks like it fixed itself.
Thanks
Hi David,
The issue sounds quite odd. Were there errors in your Graylog server logs or
browser's JS console when creating the input? Also, did you try restarting your
Graylog server to see if the input appears in the list?
Regards,
Edmundo
> On 28 Apr 2016, at 15:42, David Gerdeman wrote:
>
I'm having an issue on a fresh virtual appliance of graylog v2. When
launching a new input (gelf udp on port 7), I get a message saying that
adding the new input was successful, but the input never shows up on the
inputs page of the web portal, or in the list of inputs returned in the API
