Hi Rin, please post the actual message payload. For example the timestamp in your previous example was a string, which as I wrote before is not a valid GELF message.
[KafkaJournal] Read offset 1640 before start of log at 1683, starting to > read from the beginning of the journal. > and > [NettyTransport] ...GELF Listener... recieveBufferSize should be 1048576 > but is 212992. > Is the journal corrupt? Both are informational messages (the latter being caused by the limit the operating system imposes on the size of TCP or UDP receive buffers). Cheers, Jochen On Tuesday, 17 November 2015 18:11:54 UTC+1, Rin Saunders wrote: > > The example I sent earlier is actual input, if you insert a decimal point > into the timestamp. > > When graylog starts, all the services are reported as running. The > anomalies I see are: > > [KafkaJournal] Read offset 1640 before start of log at 1683, starting to > read from the beginning of the journal. > and > [NettyTransport] ...GELF Listener... recieveBufferSize should be 1048576 > but is 212992. > > Is the journal corrupt? > > > On Tuesday, November 17, 2015 at 11:17:30 AM UTC-5, Jochen Schalanda wrote: >> >> Hi Rin, >> >> On Tuesday, 17 November 2015 17:02:20 UTC+1, Rin Saunders wrote: >>> >>> Wait a minute. I looked at the node page. It says " *6,060 unprocessed >>> messages* are currently in the journal, " Is something down? >>> >> >> The logs of your Graylog server node should tell you what's wrong. >> >> >> Cheers, >> Jochen >> > -- 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/2ee7d42d-af79-4c09-b241-5e625de8660b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
