I see that I did post twice. Please ignore this one, response to the first
one.
On Friday, March 21, 2014 4:56:08 PM UTC-7, Robert Blumen wrote:
>
> Graylog2 is classifying 100% of incoming GELF messages as "incomplete".
>
> I tried to post this earlier but I believe that I failed. I apologize in
> advance if this gets posted twice.
>
> Using:
>
> - mongod 2.4.9
> - elasticsearch 0.90.10
> - graylog server 0.20.1
> - graylog web 0.20.1
> - from java, me.moocar:logback-gelf:jar:0.10p2
>
> Running a jetty web server on one node, sending GELF messages to GL at
> 12202 on a different node.
>
> On GL I have a GELF UDP global input listening on 12202
>
> - Under "show metrics" the counts of total messages and incomplete
> messages in the input were showing all messages being classified as
> incomplete.
> - I upgraded the logging on the server node's Graylog2 subsystem to
> "trace". The log showed a huge number of "Incomplete message" errors.
>
> The log messages were coming from GELFProcessor.java:
>
>
>
>
> * 72 if (lm == null || !lm.isComplete()) { 73
> server.metrics().meter(name(metricName, "incompleteMessages")).mark();
> 74 LOG.debug("Skipping incomplete message.");
> 75 return; 76 }*
>
> I need some help in determing why the messages are being classified as
> incomplete. If the system provided a bit more information along those
> lines that would be helpful.
>
> Robert
>
> --
>
>
> Robert Blumen
>
> [email protected]
>
> symphonycommerce.com
>
>
>
> 363 Clementina St.
>
> San Francisco, CA 94103
>
> (415) 806-8389
>
--
You received this message because you are subscribed to the Google Groups
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
