Hey,

please make sure your clocks on the server and message sender are
synced. Maybe the message timestamps are in the future.

Regards,
        Bernd

Alfonso Graña [Tue, Jul 08, 2014 at 12:59:58PM -0700] wrote:
>
>I have the same issue with 0.20.5 on debian 7. 
>Do you manage to get around this issue?
>
>Best Regards. 
>
>El sábado, 28 de junio de 2014 23:48:59 UTC-3, Nathan escribió:
>>
>> Just finished setting up Graylog2 (0.20.3) using Mitchell Anicas's 
>> fantastic walkthrough on DigitalOcean. 
>>
>> Everything went well and it all seems to test out fine but I cannot for 
>> the life of me see any of the events. I am seeing that the event counters 
>> are increasing but when I simply press on the green search button with no 
>> conditions, it get nothing! Currently I have an input that is taking in 
>> simple UDP syslog messages from routers and firewalls. 
>>
>> If I am seeing the events increment, why can I not see the actual events? 
>> Could I have missed something in the configuration?
>>
>> When I show the metrics of the input that I created I currently see 100 or 
>> so incomingMessages, 0 incompleteMessages, 100 or so proccessedMessages. 
>> That all tells me that the messages are good and are being indexed.
>>
>> Thoughts?
>>
>> Thanks!!!
>>
>
>-- 
>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.

-- 
Developer

Tel.: +49 (0)40 609 452 077
Fax.: +49 (0)40 609 452 078

TORCH GmbH
Steckelhörn 11
20457 Hamburg
Germany

https://www.torch.sh/

Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175
Geschäftsführer: Lennart Koopmann (CEO)

-- 
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.

Reply via email to