Hi,
while you can certainly increase the maximum heap size for Graylog, it
shouldn't be necessary for most workloads. As a matter of fact, increasing
the heap size is counter-productive most of the time, as it increases the
garbage collection time. What are you trying to achieve with this?
Che
Hello,
No one can help me ?
Thanks
Regards
Yves Louis
Le mercredi 8 avril 2015 11:24:54 UTC+2, yvesloui...@gmail.com a écrit :
>
> Hi everyone,
>
> Running
> graylog-1.1.0-SNAPSHOT-20150401153823/graylog-web-interface-1.1.0-SNAPSHOT-20150401152745
>
>
> When trying to access "Manage alerts" o
Hi!
Really, if you are running 1.1.0 snapshots, _many_ things will break without a
warning.
Please do not rely on these now, unless you are trying to do development on
Graylog :)
Best,
Kay
> On 16 Apr 2015, at 12:23, yveslouis.rof...@gmail.com wrote:
>
> Hello,
>
> No one can help me ?
>
>
Hi,
Thanks Kay for your answer,
I just thought it could be helpful to know there is something wrong.
But you're right, I'm not a developer and snapshots are for development.
Regards,
Yves Louis
Le jeudi 16 avril 2015 12:25:18 UTC+2, Kay Röpke a écrit :
>
> Hi!
>
> Really, if you are running 1.
> On 16 Apr 2015, at 14:45, yveslouis.rof...@gmail.com wrote:
>
> Thanks Kay for your answer,
> I just thought it could be helpful to know there is something wrong.
>
> But you're right, I'm not a developer and snapshots are for development.
>
No worries.
It’s just that with 1.1.0 snapshots
Hi Jochen,
That worked great, i archived the data using the copy and no downtime,
Thanks Much for your help.
I tried to copy back the data and changed the ownership to elasticsearch,
but the indice was not shown in elasticsearch yet. I tried to refresh the
whole indice, but no luck. I closed
it's vm image, so gparted wouldn't work
You can of course just read OVA
Readme https://github.com/Graylog2/graylog2-images/tree/master/ova :-)
especially *"Extend disk space"* section, in short you have to generate
new, larger hd image and make vm use it as second one, create partition on
it,
Dear, I've installed Graylog 1.0.1. Elasticsearch and graylog-web start
automatically but graylog-server doesn't.
I edit /etc/rc.local with:
/etc/init.d/graylog-server start &
but after reboot the graylog-server is stopped.
The only way to start the service is executing manually from terminal:
In the /etc/init.d/graylog-server file I add the line:
/bin/sleep 20
and the graylog-server service starts perfectly.
Maybe graylog-server has to wait more time for any condition I don't know???
Regards,
Roberto
El jueves, 16 de abril de 2015, 10:46:06 (UTC-3), roberto...@gmail.com
escribió:
I have install graylog2 docker successfully,
and I can access the web interface http://localhost:9000/
docker run -t -p 9000:9000 -p 12201:12201 -p 12301:12301 -p 12302:12302
graylog2/allinone
for nginx:
I followed this guide,
https://www.graylog.org/resource/content-pack/547b5021e4b0a06d87e
Yesterday I installed the latest graylog.ova and enabled ssl using
graylog-ctl enforce-ssl.
I need to remove ssl so I can redirect using a load balancer.
I’ve modified /etc/graylog/graylog-settings.json to show false for
enforce_ssl and used graylog-ctl reconfigure.
I am still getting r
So most of the performance tuning should take place in the
/etc/elasticsearch settings then (local or not)? The graylog elastic index
doesn't appear to store anything anyway.
Looks like we peak at about 2.5k messages per minute (very rare) from a
dozen sources. More commonly we see 500 message
Going to try your solution here, it occurs to me to on a cents installation.
Reboot, graylag-web up, and no grayling-server running.
Op donderdag 16 april 2015 16:49:28 UTC+2 schreef roberto...@gmail.com:
>
> In the /etc/init.d/graylog-server file I add the line:
>
> /bin/sleep 20
>
> and the g
13 matches
Mail list logo
