Same Problem... :-/
Booth Machines have 6GB RAM and the heap settings are increased to:
"custom_attributes": {
"graylog-server": {
"memory": "1800m"
},
"elasticsearch": {
"memory": "2600m"
}
}
Am Montag, 10. Oktober 2016 17:35:54 UTC+2 schrieb Jochen Schalanda:
>
> Hi Timo,
>
> if you're running Graylog and Elasticsearch on those VMs, 4 GB RAM is too
> little.
>
> Try providing at least 6 GB of memory and tweak the JVM heap settings for
> Graylog and Elasticsearch.
>
> Cheers,
> Jochen
>
> On Monday, 10 October 2016 17:19:38 UTC+2, Timo Beuker wrote:
>>
>> LAN-Master: *Graylog **2.1.1+01d50e5* on XXXXXX (Oracle Corporation
>> 1.8.0_101 on Linux 4.2.0-42-generic)
>> VMWare: V7 /* 4 vCPU / 4GB RAM / 20GB IDE & 60 GB SATA* (Data)
>>
>> DMZ-Backend: *Graylog **2.1.1+01d50e5* on XXXXXX (Oracle Corporation
>> 1.8.0_101 on Linux 4.2.0-42-generic)
>> VMWare: V7 / *2 vCPU / 4GB RAM / 20GB IDE & 80 GB SATA* (Data)
>>
>> Am Montag, 10. Oktober 2016 17:05:45 UTC+2 schrieb Jochen Schalanda:
>>>
>>> Hi Timo,
>>>
>>> what are the hardware specs of your VMs and which exact versions of
>>> Graylog are you using?
>>>
>>> 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/e799c39e-1c81-4a34-98c6-5b09c1fb1534%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.