Hi Steve,
errors like this can also be caused by long GC pauses in your Graylog
server nodes. Do you see any of those in your Graylog server logs? And in
general, are there any error messages in your Graylog server logs?
Cheers,
Jochen
On Tuesday, 26 January 2016 16:20:36 UTC+1, st...@cherryf
Hi Steve,
I've only briefly skipped through the logs files you've attached.
2016-01-28 15:40:07,822 ERROR:
> org.graylog2.inputs.codecs.GelfChunkAggregator - Received duplicate chunk 0
> for message 3737393936323835 from null
This could be a broken GELF client.
2016-01-29 13:00:51,334 ERROR
Hi Jochen
Thanks for the reply. I've actually tried turning off the journal,
message_journal_enabled = false
this didn't seem to make any difference.
The VMWare host I'm running the two nodes on are quite heavily loaded with
high CPU wait times. I decided to move the nodes to a dedicated VMWar
Hi Steve,
I'd not recommend disabling the message journal at all as it's being used
to buffer messages if the processing steps or the output to the backend
(Elasticsearch) takes too long.
Cheers,
Jochen
On Monday, 1 February 2016 11:34:02 UTC+1, st...@cherryfamily.co.uk wrote:
>
> Hi Jochen
