Hello,
We have a pair of GL nodes with a cluster of three ES servers at the
backend. The occasional capacity problem aside this has been working fine
for the most part.
Today one of the GL nodes decided to act up though, it's behavior is pretty
strange:
The process is up, I can connect to it v
Oh and I noticed I left out the versions of the software, doh.
Graylog 0.20.6(web and server)
ES 0.90.10
Regards
Johan
On Tuesday, August 19, 2014 2:29:48 PM UTC+2, sun...@sunner.com wrote:
>
> Hello,
>
> We have a pair of GL nodes with a cluster of three ES servers at the
> backend. The occasi
Hello,
We've lost the ability to add widgets to dashboards, it took me a while to
figure out but this is because of a deleted user that once created a
dashboard.
Basically, when you go to the dashboards list this will cause an error when
the "Created by" user isn't found, and this in turn seems
Hello,
Is it possible to rewrite the timestamp on incoming logs to the local
system time of the Graylog server? I'm asking because we have some machines
all across the world where the timezones don't match up so the timestamps
get fairly large offsets.
I've looked into using a Drools rule for t
Hello,
With the release of 1.0 we've started moving towards a new cluster of GL
hosts. These are working very well, with one exception.
For some reason any reasonably significant UDP traffic will choke the
message processor, fill up and process buffers on all four hosts, and
effectively choke u
Well that could be a suspect if it wasn't for the fact that the old nodes
running on old hardware handle it just fine, along with the fact that the
traffic seems to reach the nodes just fine(i.e it actually fills the
journal up just fine, and the input buffer never breaks a sweat). And it's
rea
This is strange, I went through all of the settings for my reply, and we
are indeed using rdns, and it seems to be the culprit. The strangeness is
that it works fine on the old servers even though they're on the same
networks, and using the same DNS's and resolver settings.
Did something regardi
I installed unbound locally and used this, and it seems to have resolved
the issue. It's odd that the old server didn't show this behavior, but I'm
happy enough that it's resolved anyway. :)
Regards
Johan
On Friday, February 27, 2015 at 2:02:08 PM UTC+1, Bernd Ahlers wrote:
>
> Johan, Henrik,
