João,
Thank you very much. This did fix the issue.
Cheers,
Daniel
On Saturday, June 7, 2014 6:40:00 AM UTC+12, Joao Marques Alexandre wrote:
>
> Hi Daniel,
>
> I've published an equal post about this issue and after no answer, I've
> find it out by myself:
>
> 1- edit your graylog2.conf and mo
I wanted to leave a note that installing NTP here and syncing time did fix
these errors:
2014-06-11 14:09:15,978 WARN : org.graylog2.periodical.NodePingThread - Did
not find meta info of this node. Re-registering.
2014-06-11 14:09:16,978 WARN : org.graylog2.periodical.NodePingThread - Did
not f
These are usually fields that used to contain a number but now are a
string. Thus incompatible.
Without looking at the index and the messages no one can tell what the
problem is :(
On Jun 11, 2014 6:46 PM, "Florent B" wrote:
> Any idea for these errors ? :-)
>
> On 06/10/2014 06:32 PM, Florent B
João,
Thank you so much for your message! I know I'm not the OP but I was
searching around on how to fix this exact issue and your instructions
worked perfectly.
Thanks again,
Chris
On Friday, June 6, 2014 11:40:00 AM UTC-7, Joao Marques Alexandre wrote:
>
> Hi Daniel,
>
> I've published an eq
I have the exact same issue.
ElasticSearch 0.90.13 and Graylog2 0.20.2
I've got 5 servers all sending their logs to Graylog2, and TCP dump shows
they are indeed sending their logs. I see graylog2 showing that it is
getting messages:
Meter
Total:183 eventsMean:0.15 events/sec1 minute avg:0 ev
Great!
Could you link to it from the issue
https://github.com/Graylog2/graylog2-web-interface/issues/560 ?
Maybe we can either integrate something, or at the very least point
people to it.
Many thanks!
On Wed, Jun 11, 2014 at 2:36 PM, Егор Морозов wrote:
> Hi,
>
> Hooray! I was finally able to
Hi,
Hooray! I was finally able to do this. Thanks a lot :) I think I'll make up
the code and release it later~
On Tuesday, June 10, 2014 4:57:33 PM UTC+3, Kay Röpke wrote:
>
> Hi!
>
> I believe this is the Play framework signing the entire cookie.
> The relevant code looks like:
> /**
>*
Hi!
The exception means that some indices were set to read only, but an
attempt was made to write to them, at least metadata. This could
possibly happen for recalculating index ranges, I'll open a ticket for
investigation.
As to the rise in CPU usage, I'm not aware that there's anything in
0.20.2
https://imgur.com/ex4lGF0
In this graph you can see the rise of the cpu load on our graylog2 server
(server, web ui and elastic search all on the same machine). Especially elastic
search need much more cpu after the update. We have round about 160msg/sec -
and overall our graylog2 contains 80mio
Hi Asad,
Searching around I found a very fine article about Graylog2 with
Elasticsearch, maybe there is some info
in it to help you out. I am trying to build my own Elasticsearch cluster
here.
http://edgeofsanity.net/article/2012/12/26/elasticsearch-for-logging.html
Arie.
On Monday, June 9,
I'll have another look at the amqp consumer implementation, but maybe it
helps if you configure an explicit prefetch count for the amqp radio inputs?
I believe the default is 0 (unlimited) which isn't optimal for multiple
consumers IIRC.
On Jun 11, 2014 9:40 AM, "Michael Glad" wrote:
> Thank you
Thank you for your help, it seems that after the 0.20.2 upgrade + change to
AMQP, log entries are piling up in AMQP which eventually leads
to an storage crisis:
root@loggl2loghost01:~# grep vm_memory_high_watermark
/var/log/rabbitmq/rab...@loggl2loghost01.log
...
vm_memory_high_watermark set. Memo
12 matches
Mail list logo
