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 VMWare host 
to see if this will make a difference. I won't be able to do this for at 
least a week though. I'll report my findings afterwards.

Cheers
Steve

On Friday, 29 January 2016 16:37:29 UTC, Jochen Schalanda wrote:
>
> 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: 
>> org.graylog2.shared.buffers.processors.DecodingProcessor - Error processing 
>> message RawMessage{id=52d32793-c688-11e5-9cd7-005056a73602, 
>> journalOffset=22464451, codec=gelf, payloadSize=1247, 
>> timestamp=2016-01-29T13:00:51.209Z}
>> java.util.zip.ZipException: Corrupt GZIP trailer
>
>
> Those error messages look like you either received broken GELF messages or 
> that your journal is broken (e. g. ran out of disk space). Try deleting the 
> journal files (see 
> https://github.com/Graylog2/graylog2-server/blob/1.3.3/misc/graylog2.conf#L263-L265)
>  
> while Graylog is stopped and start the Graylog server nodes again after 
> that.
>
>
> Cheers,
> Jochen
>
> On Friday, 29 January 2016 14:22:14 UTC+1, [email protected] wrote:
>>
>> Hi Jochen,
>>
>> Thanks for the reply, I don't see and messages regarding GC pauses but I 
>> do have other errors. I don't think these errors have any bearing on this 
>> issue, I could be wrong of course. I've attached the logs from both nodes 
>> in the cluster.
>>
>> Cheers
>> Steve
>>
>

-- 
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/da075cf1-4e8e-4406-be98-cf4ca25f04b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to