Re: [graylog2] Re: Increase JVM heap space
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? Cheers, Jochen On Thursday, 16 April 2015 00:06:03 UTC+2, Mark Moorcroft wrote: From my kickstart: sed -i -e 's/-Xms1g -Xmx1g -XX:NewRatio=1 -XX:PermSize=128m -XX:MaxPermSize=256m -server/-Xms4g -Xmx4g -XX:NewRatio=1 -server/' /etc/sysconfig/graylog-server I increased from 1G to 4G here. On Wednesday, April 15, 2015 at 6:42:40 AM UTC-7, Alejandro Cabrera Obed wrote: OK, but how can I increase the heap space in the Node tab of the graylog web intrerface??? Because I see this message: The JVM is using *764 of 972 MB* heap space and will not attempt to use more than *972 MB* *Is it possible to grow up from 972 MB to 4 GB ??? How ???* *Thanks* 2015-04-15 4:54 GMT-03:00 Jochen Schalanda joc...@graylog.com: Hi Alejandro, starting with Graylog 1.0.0, incoming messages are always written to the disk journal (which is generally a good thing). You can disable the disk journal entirely (see https://github.com/Graylog2/graylog2-server/blob/1.0.1/misc/graylog2.conf#L245-246), but I would not recommend doing this. Do you see any problems with your current Graylog setup? Cheers, Jochen On Tuesday, 14 April 2015 21:29:24 UTC+2, Alejandro Cabrera Obed wrote: People, in my graylog server I have a lot of incoming logs and in the Node tab of Graylog web (version 1.0.1) I can see too many processing messages and the processing status bar is always near the maximum. How can I increase the JVM heap space in order to avoid journaling??? At the moment the JVM heap space is 972 MB. Thanks a lot, Alejandro -- You received this message because you are subscribed to a topic in the Google Groups graylog2 group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/graylog2/Srt7uXJDdpY/unsubscribe. To unsubscribe from this group and all its topics, send an email to graylog2+u...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Alejandro Cabrera Obed aco...@gmail.com -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: problem with stream alert
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 of a stream, I have the alert Oh
no, something went wrong!
Reason: Could not fetch stream. We expected HTTP 200, but got a HTTP 200.
I tried with
graylog-1.1.0-SNAPSHOT-20150401153823/graylog-web-interface-1.1.0-SNAPSHOT-20150401152745.tgz
and
graylog-1.1.0-SNAPSHOT-20150407151523.tar.gz/graylog-web-interface-1.1.0-SNAPSHOT-20150407120720.tgz
with same result.
With graylog-1.0.0.tgz/graylog-web-interface-1.0.0.tgz there wasn't any
problem.
Error looks like #801 (
https://github.com/Graylog2/graylog2-server/issues/801) or #1023 (
https://github.com/Graylog2/graylog2-web-interface/issues/1023)
Have you already seen this error ?
Have you any idea ?
Thanks in advance.
Regards
Yves Louis ROFORT
(You caused a org.graylog2.restclient.lib.APIException. API call failed
GET
http://@:12900/streams/5524cec799325c408c932955/alarmcallbacks/available
returned 200 OK body:
{types:{org.graylog2.alarmcallbacks.HTTPAlarmCallback:{name:HTTP
Alarm
Callback,requested_configuration:[{title:url,human_name:URL,default_value:
https://example.org/alerts,description:The URL to POST to when an
alert is
triggered,attributes:[],type:text,optional:false,attributes_as_jsvalidation_spec:}]},org.graylog2.alarmcallbacks.EmailAlarmCallback:{name:Email
Alert
Callback,requested_configuration:[{title:sender,human_name:Sender,default_value:
gray...@example.org,description:The sender of sent out mail
alerts,attributes:[],type:text,optional:false,attributes_as_jsvalidation_spec:},{title:body,human_name:E-Mail
Body,default_value:##\nDate:
${check_result.triggeredAt}\nStream ID: ${stream.id}\nStream title:
${stream.title}\n${if stream_url}Stream URL:
${stream_url}${end}\n\nTriggered condition:
${check_result.triggeredCondition}\n##\n\nLast messages accounting
for this alert:\n${if backlog_size 0}${foreach backlog
message}\n${message}\n${end}\n${else}No
backlog.${end}\n\n,description:The template to generate the body
from,attributes:[textarea],type:text,optional:true}]}}})
Stacktrace
org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder#execute
(ApiClientImpl.java:477)
org.graylog2.restclient.models.AlarmCallbackService#available
(AlarmCallbackService.java:77)
controllers.AlertsController#index (AlertsController.java:79)
Routes$$anonfun$routes$1$$anonfun$applyOrElse$31$$anonfun$apply$461#apply
(routes_routing.scala:1605)
Routes$$anonfun$routes$1$$anonfun$applyOrElse$31$$anonfun$apply$461#apply
(routes_routing.scala:1605)
play.core.Router$HandlerInvokerFactory$$anon$4#resultCall
(Router.scala:264)
play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#invocation
(Router.scala:255)
play.core.j.JavaAction$$anon$1#call (JavaAction.scala:55)
play.GlobalSettings$1#call (GlobalSettings.java:67)
play.mvc.Security$AuthenticatedAction#call (Security.java:44)
play.core.j.JavaAction$$anonfun$11#apply (JavaAction.scala:82)
play.core.j.JavaAction$$anonfun$11#apply (JavaAction.scala:82)
scala.concurrent.impl.Future$PromiseCompletingRunnable#liftedTree1$1
(Future.scala:24)
scala.concurrent.impl.Future$PromiseCompletingRunnable#run
(Future.scala:24)
play.core.j.HttpExecutionContext$$anon$2#run
(HttpExecutionContext.scala:40)
play.api.libs.iteratee.Execution$trampoline$#execute (Execution.scala:46)
play.core.j.HttpExecutionContext#execute (HttpExecutionContext.scala:32)
scala.concurrent.impl.Future$#apply (Future.scala:31)
scala.concurrent.Future$#apply (Future.scala:485)
play.core.j.JavaAction$class#apply (JavaAction.scala:82)
play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#apply
(Router.scala:252)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply
(Action.scala:130)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply
(Action.scala:130)
play.utils.Threads$#withContextClassLoader (Threads.scala:21)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply
(Action.scala:129)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply
(Action.scala:128)
scala.Option#map (Option.scala:145)
play.api.mvc.Action$$anonfun$apply$1#apply (Action.scala:128)
play.api.mvc.Action$$anonfun$apply$1#apply (Action.scala:121)
play.api.libs.iteratee.Iteratee$$anonfun$mapM$1#apply (Iteratee.scala:483)
play.api.libs.iteratee.Iteratee$$anonfun$mapM$1#apply (Iteratee.scala:483)
play.api.libs.iteratee.Iteratee$$anonfun$flatMapM$1#apply
(Iteratee.scala:519)
play.api.libs.iteratee.Iteratee$$anonfun$flatMapM$1#apply
(Iteratee.scala:519)
play.api.libs.iteratee.Iteratee$$anonfun$flatMap$1$$anonfun$apply$14#apply
Re: [graylog2] problem with stream alert
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 we are changing lots of smaller things that can lead to surprising breakage if you happen to use the wrong two versions with each other. :) We’ll be posting betas as soon as we feel they are stable enough for testing and would very much appreciate user feedback on those when the time comes. Before that usually too many things change day to day and you’d end up installing this multiple times a day (ask our QA guy ;)) cheers, Kay -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Log Rotation
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 one of the open indice, which was closed successfully and the backed up indice that i copied was also shown. I then recalculated the index in graylog to show the index. Is there any other function/operation that can help me to show the indice in elasticsearch after it is copied back. Am i missing something. Regards, Hema. On Wednesday, April 8, 2015 at 2:37:53 PM UTC+5:30, Jochen Schalanda wrote: Hi Hema, if you're modifying the Elasticsearch indices Graylog externally, you'll have to recalculate the index ranges (System - Indices - Maintenance - Recalculate index ranges). Cheers, Jochen On Tuesday, 7 April 2015 13:51:28 UTC+2, Hema Kumar wrote: Hi Jochen, If i build a shell script using the API and move the closed indice files to different location, would a elasticsearch restart is required in order to refresh itself and the graylog? Based on your suggestion, my plan is to grep for closed indices using API and zip/move all the indices to a different location. Would this help or should i just copy the file to a different location and delete the source with the help of curator. Any ideas to include log rotation policy roles into elastic search in the future release. Thanks, Hema On Friday, April 3, 2015 at 3:23:35 PM UTC+5:30, Jochen Schalanda wrote: Hi Hema, multi-tiered data retention is currently not supported by Graylog. You could probably build something yourself quite quickly using the Elasticsearch API directly (e. g. check which indices are already closed and then create a snapshot of them). Maybe you could even use Curator ( http://www.elastic.co/guide/en/elasticsearch/client/curator/current/about.html) for that. Cheers, Jochen On Friday, 3 April 2015 01:35:00 UTC+2, Hema Kumar wrote: Hi, Is there a way to do a log Rotation - My policy is to hold 60 days of indices which was done in the configs, the logs more than 60 days are closed. - The second thing is after 60 days the closed indices should be moved to different drive and should hold it for 120 days but should still be available in graylog for easier access to open and search for it. - The third is after 120 days the logs can be archived using a zip utility and stored in different drive or deleted. * Numbers are just reference. What i am trying to ask is, would graylog be setting such log rotation policy instead of external tools. Really like the tool that is being developed. Thanks Much. Regards, Hema. -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] problem with stream alert
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.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, yvesloui...@gmail.com javascript: wrote:
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 of a stream, I have the alert Oh
no, something went wrong!
Reason: Could not fetch stream. We expected HTTP 200, but got a HTTP 200.
I tried with
graylog-1.1.0-SNAPSHOT-20150401153823/graylog-web-interface-1.1.0-SNAPSHOT-20150401152745.tgz
and
graylog-1.1.0-SNAPSHOT-20150407151523.tar.gz/graylog-web-interface-1.1.0-SNAPSHOT-20150407120720.tgz
with same result.
With graylog-1.0.0.tgz/graylog-web-interface-1.0.0.tgz there wasn't any
problem.
Error looks like #801 (
https://github.com/Graylog2/graylog2-server/issues/801) or #1023 (
https://github.com/Graylog2/graylog2-web-interface/issues/1023)
Have you already seen this error ?
Have you any idea ?
Thanks in advance.
Regards
Yves Louis ROFORT
(You caused a org.graylog2.restclient.lib.APIException. API call failed
GET
http://@:12900/streams/5524cec799325c408c932955/alarmcallbacks/available
returned 200 OK body:
{types:{org.graylog2.alarmcallbacks.HTTPAlarmCallback:{name:HTTP
Alarm
Callback,requested_configuration:[{title:url,human_name:URL,default_value:
https://example.org/alerts,description:The URL to POST to when an
alert is
triggered,attributes:[],type:text,optional:false,attributes_as_jsvalidation_spec:}]},org.graylog2.alarmcallbacks.EmailAlarmCallback:{name:Email
Alert
Callback,requested_configuration:[{title:sender,human_name:Sender,default_value:
gra...@example.org javascript:,description:The sender of sent out
mail
alerts,attributes:[],type:text,optional:false,attributes_as_jsvalidation_spec:},{title:body,human_name:E-Mail
Body,default_value:##\nDate:
${check_result.triggeredAt}\nStream ID: ${stream.id}\nStream title:
${stream.title}\n${if stream_url}Stream URL:
${stream_url}${end}\n\nTriggered condition:
${check_result.triggeredCondition}\n##\n\nLast messages accounting
for this alert:\n${if backlog_size 0}${foreach backlog
message}\n${message}\n${end}\n${else}No
backlog.${end}\n\n,description:The template to generate the body
from,attributes:[textarea],type:text,optional:true}]}}})
Stacktrace
org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder#execute
(ApiClientImpl.java:477)
org.graylog2.restclient.models.AlarmCallbackService#available
(AlarmCallbackService.java:77)
controllers.AlertsController#index (AlertsController.java:79)
Routes$$anonfun$routes$1$$anonfun$applyOrElse$31$$anonfun$apply$461#apply
(routes_routing.scala:1605)
Routes$$anonfun$routes$1$$anonfun$applyOrElse$31$$anonfun$apply$461#apply
(routes_routing.scala:1605)
play.core.Router$HandlerInvokerFactory$$anon$4#resultCall
(Router.scala:264)
play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#invocation
(Router.scala:255)
play.core.j.JavaAction$$anon$1#call (JavaAction.scala:55)
play.GlobalSettings$1#call (GlobalSettings.java:67)
play.mvc.Security$AuthenticatedAction#call (Security.java:44)
play.core.j.JavaAction$$anonfun$11#apply (JavaAction.scala:82)
play.core.j.JavaAction$$anonfun$11#apply (JavaAction.scala:82)
scala.concurrent.impl.Future$PromiseCompletingRunnable#liftedTree1$1
(Future.scala:24)
scala.concurrent.impl.Future$PromiseCompletingRunnable#run
(Future.scala:24)
play.core.j.HttpExecutionContext$$anon$2#run
(HttpExecutionContext.scala:40)
play.api.libs.iteratee.Execution$trampoline$#execute (Execution.scala:46)
play.core.j.HttpExecutionContext#execute (HttpExecutionContext.scala:32)
scala.concurrent.impl.Future$#apply (Future.scala:31)
scala.concurrent.Future$#apply (Future.scala:485)
play.core.j.JavaAction$class#apply (JavaAction.scala:82)
play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#apply
(Router.scala:252)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply
(Action.scala:130)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply
(Action.scala:130)
play.utils.Threads$#withContextClassLoader (Threads.scala:21)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply
(Action.scala:129)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply
(Action.scala:128)
Re: [graylog2] problem with stream alert
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 ?
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 of a stream, I have the alert Oh no,
something went wrong!
Reason: Could not fetch stream. We expected HTTP 200, but got a HTTP 200.
I tried with
graylog-1.1.0-SNAPSHOT-20150401153823/graylog-web-interface-1.1.0-SNAPSHOT-20150401152745.tgz
and
graylog-1.1.0-SNAPSHOT-20150407151523.tar.gz/graylog-web-interface-1.1.0-SNAPSHOT-20150407120720.tgz
with same result.
With graylog-1.0.0.tgz/graylog-web-interface-1.0.0.tgz there wasn't any
problem.
Error looks like #801 (https://github.com/Graylog2/graylog2-server/issues/801
https://github.com/Graylog2/graylog2-server/issues/801) or #1023
(https://github.com/Graylog2/graylog2-web-interface/issues/1023
https://github.com/Graylog2/graylog2-web-interface/issues/1023)
Have you already seen this error ?
Have you any idea ?
Thanks in advance.
Regards
Yves Louis ROFORT
(You caused a org.graylog2.restclient.lib.APIException. API call failed GET
http://@:12900/streams/5524cec799325c408c932955/alarmcallbacks/available
returned 200 OK body:
{types:{org.graylog2.alarmcallbacks.HTTPAlarmCallback:{name:HTTP Alarm
Callback,requested_configuration:[{title:url,human_name:URL,default_value:https://example.org/alerts
https://example.org/alerts,description:The URL to POST to when an
alert is
triggered,attributes:[],type:text,optional:false,attributes_as_jsvalidation_spec:}]},org.graylog2.alarmcallbacks.EmailAlarmCallback:{name:Email
Alert
Callback,requested_configuration:[{title:sender,human_name:Sender,default_value:gray...@example.org
mailto:gray...@example.org,description:The sender of sent out mail
alerts,attributes:[],type:text,optional:false,attributes_as_jsvalidation_spec:},{title:body,human_name:E-Mail
Body,default_value:##\nDate: ${check_result.triggeredAt}\nStream
ID: ${stream.id http://stream.id/}\nStream title: ${stream.title}\n${if
stream_url}Stream URL: ${stream_url}${end}\n\nTriggered condition:
${check_result.triggeredCondition}\n##\n\nLast messages accounting
for this alert:\n${if backlog_size 0}${foreach backlog
message}\n${message}\n${end}\n${else}No
backlog.${end}\n\n,description:The template to generate the body
from,attributes:[textarea],type:text,optional:true}]}}})
Stacktrace
org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder#execute
(ApiClientImpl.java:477)
org.graylog2.restclient.models.AlarmCallbackService#available
(AlarmCallbackService.java:77)
controllers.AlertsController#index (AlertsController.java:79)
Routes$$anonfun$routes$1$$anonfun$applyOrElse$31$$anonfun$apply$461#apply
(routes_routing.scala:1605)
Routes$$anonfun$routes$1$$anonfun$applyOrElse$31$$anonfun$apply$461#apply
(routes_routing.scala:1605)
play.core.Router$HandlerInvokerFactory$$anon$4#resultCall (Router.scala:264)
play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#invocation
(Router.scala:255)
play.core.j.JavaAction$$anon$1#call (JavaAction.scala:55)
play.GlobalSettings$1#call (GlobalSettings.java:67)
play.mvc.Security$AuthenticatedAction#call (Security.java:44)
play.core.j.JavaAction$$anonfun$11#apply (JavaAction.scala:82)
play.core.j.JavaAction$$anonfun$11#apply (JavaAction.scala:82)
scala.concurrent.impl.Future$PromiseCompletingRunnable#liftedTree1$1
(Future.scala:24)
scala.concurrent.impl.Future$PromiseCompletingRunnable#run (Future.scala:24)
play.core.j.HttpExecutionContext$$anon$2#run (HttpExecutionContext.scala:40)
play.api.libs.iteratee.Execution$trampoline$#execute (Execution.scala:46)
play.core.j.HttpExecutionContext#execute (HttpExecutionContext.scala:32)
scala.concurrent.impl.Future$#apply (Future.scala:31)
scala.concurrent.Future$#apply (Future.scala:485)
play.core.j.JavaAction$class#apply (JavaAction.scala:82)
play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1#apply
(Router.scala:252)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply
(Action.scala:130)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5#apply
(Action.scala:130)
play.utils.Threads$#withContextClassLoader (Threads.scala:21)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply (Action.scala:129)
play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4#apply (Action.scala:128)
scala.Option#map (Option.scala:145)
play.api.mvc.Action$$anonfun$apply$1#apply (Action.scala:128)
[graylog2] Re: graylog-server doesn't start automatically
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ó: 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: # service graylog-server start How can I do in order to start graylog-server automatically on boot??? Thanks a lot, Roberto -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] graylog2 docker nginx problem
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/547b5021e4b0a06d87eea01e/ log_format graylog2_format '$remote_addr - $remote_user [$time_local] $request $status $body_bytes_sent $http_referer $http_user_agent $http_x_forwarded_for msec=$msec|connection=$connection |connection_requests=$connection_requests|millis=$request_time'; # replace the hostnames with the IP or hostname of your Graylog2 server access_log syslog:server=localhost:12301 graylog2_format; error_log syslog:server= localhost:12302; But I still not get any message from web interface, how to check this problem? -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Storage size
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, move contents of /var/opt/graylog/ and mount it in this directory (which is now empty) Since official OVA images are configured to use LVM you can just add create a new disk image in virtualbox (if you use it) add it to VM, boot it, and add new hd to LVM volume, then increase root partition size. Alternatively you can increase existing HD image size, you can easily do that with tools included with virtualbox, (the image needs to be converted to VDI format first since it's the only format virtualbox tools can resize), then after vm bootup you need to increase LVM volume and root partition sizes respectively, this is what i've done I've done it about a month ago, dind't documented it, so i can't provide any more help. It took me about 2 hours with all the researching, but i already had some linux experience. The first solution is the easiest, you need basic linux knowlege to do it, the second and third need more knowlege, i had to do additional research concerning LVM and vm images resizing, it's easy to google. W dniu czwartek, 26 marca 2015 23:39:33 UTC+1 użytkownik Sai Mupparapu napisał: Hi, I deployed the OVA and i see that it defaults to 20GB disk space. I have 2 questions 1) Does graylog operate like a circular buffer when it runs out of disk space? 2) If i want to increase the storage can i just increase the hard disk size? or do i have to configure anything for graylog to use the additional space? thank you Sai -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] graylog-server doesn't start automatically
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: # service graylog-server start How can I do in order to start graylog-server automatically on boot??? Thanks a lot, Roberto -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Re: Increase JVM heap space
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 per minute spikes. On Thursday, April 16, 2015 at 1:23:39 AM UTC-7, Jochen Schalanda wrote: 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? Cheers, Jochen On Thursday, 16 April 2015 00:06:03 UTC+2, Mark Moorcroft wrote: From my kickstart: sed -i -e 's/-Xms1g -Xmx1g -XX:NewRatio=1 -XX:PermSize=128m -XX:MaxPermSize=256m -server/-Xms4g -Xmx4g -XX:NewRatio=1 -server/' /etc/sysconfig/graylog-server I increased from 1G to 4G here. On Wednesday, April 15, 2015 at 6:42:40 AM UTC-7, Alejandro Cabrera Obed wrote: OK, but how can I increase the heap space in the Node tab of the graylog web intrerface??? Because I see this message: The JVM is using *764 of 972 MB* heap space and will not attempt to use more than *972 MB* *Is it possible to grow up from 972 MB to 4 GB ??? How ???* *Thanks* 2015-04-15 4:54 GMT-03:00 Jochen Schalanda joc...@graylog.com: Hi Alejandro, starting with Graylog 1.0.0, incoming messages are always written to the disk journal (which is generally a good thing). You can disable the disk journal entirely (see https://github.com/Graylog2/graylog2-server/blob/1.0.1/misc/graylog2.conf#L245-246), but I would not recommend doing this. Do you see any problems with your current Graylog setup? Cheers, Jochen On Tuesday, 14 April 2015 21:29:24 UTC+2, Alejandro Cabrera Obed wrote: People, in my graylog server I have a lot of incoming logs and in the Node tab of Graylog web (version 1.0.1) I can see too many processing messages and the processing status bar is always near the maximum. How can I increase the JVM heap space in order to avoid journaling??? At the moment the JVM heap space is 972 MB. Thanks a lot, Alejandro -- You received this message because you are subscribed to a topic in the Google Groups graylog2 group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/graylog2/Srt7uXJDdpY/unsubscribe. To unsubscribe from this group and all its topics, send an email to graylog2+u...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Alejandro Cabrera Obed aco...@gmail.com -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: graylog-server doesn't start automatically
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 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ó: 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: # service graylog-server start How can I do in order to start graylog-server automatically on boot??? Thanks a lot, Roberto -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
