Re: [graylog2] Exception in thread "elasticsearch[graylog2-server][generic][T#1]"

2016-06-23 Thread Jan Doberstein
Hej Anant,


On 23. Juni 2016 at 16:34:21, Anant Sawant (sawantanan...@gmail.com) wrote:
> This is the first time this issue has occurred. Could you please tell me
> how can I check and increase heap size for graylog server, I searched but
> got nothing for graylog server about how to increase the heap size.

it depend how you had installed graylog. in your startup script you
can place additional java opts and you need to raise the heap at this
location.

/jd

-- 
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/CAGm-bLbSM8R7WTAAin_3EUw3dHoXVDoPpJ3XweDgsvPqLT45xg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [graylog2] Exception in thread "elasticsearch[graylog2-server][generic][T#1]"

2016-06-23 Thread Anant Sawant
Hi Jan!

Thanks for the reply.
This is the first time this issue has occurred. Could you please tell me 
how can I check and increase heap size for graylog server, I searched but 
got nothing for graylog server about how to increase the heap size. 

On Thursday, 23 June 2016 15:10:41 UTC+5:30, Jan Doberstein wrote:
>
> Hej Anant, 
>
>
> On 23. Juni 2016 at 09:40:05, Anant Sawant (sawant...@gmail.com 
> ) wrote: 
> > Graylog server is throwing following error. Exception in thread 
>
>
> > Exception: java.lang.OutOfMemoryError thrown from the 
> > UncaughtExceptionHandler in thread 
> > "elasticsearch[graylog2-server][generic][T#10]" 
> > Exception in thread "eventbus-handler-8" Exception in thread 
> > "restapi-boss-0" Exception in thread "eventbus-handler-9" 
> > Exception: java.lang.OutOfMemoryError thrown from the 
> > UncaughtExceptionHandler in thread "eventbus-handler-8" 
> > 
> > Exception: java.lang.OutOfMemoryError thrown from the 
> > UncaughtExceptionHandler in thread "restapi-boss-0” 
>
>
> Does this happen from one day to the other? Did you check you Memory 
> usage and the Heap of the Graylog server? 
>
> Would it be possible for you to Update to the latest 1.3.5 release or 
> Update to the most current 2.0.3 Version? 
>
>
> > Is the issue related to the Graylog server or elasticsearch?? 
> > 
> > Using Graylog 1.1.6 and elasticsearch 1.7.2 on CentOS release 6.7. 
>
> This is related to Graylog - as you can see it gives and 
> out-of-memory-error 
>
> with kind regards 
> Jan 
>

-- 
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/d6891248-26c5-4057-b195-cb44cbc4fac7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [graylog2] Exception in thread "elasticsearch[graylog2-server][generic][T#1]"

2016-06-23 Thread Jan Doberstein
Hej Anant,


On 23. Juni 2016 at 09:40:05, Anant Sawant (sawantanan...@gmail.com) wrote:
> Graylog server is throwing following error. Exception in thread


> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread
> "elasticsearch[graylog2-server][generic][T#10]"
> Exception in thread "eventbus-handler-8" Exception in thread
> "restapi-boss-0" Exception in thread "eventbus-handler-9"
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "eventbus-handler-8"
>
> Exception: java.lang.OutOfMemoryError thrown from the
> UncaughtExceptionHandler in thread "restapi-boss-0”


Does this happen from one day to the other? Did you check you Memory
usage and the Heap of the Graylog server?

Would it be possible for you to Update to the latest 1.3.5 release or
Update to the most current 2.0.3 Version?


> Is the issue related to the Graylog server or elasticsearch??
>
> Using Graylog 1.1.6 and elasticsearch 1.7.2 on CentOS release 6.7.

This is related to Graylog - as you can see it gives and out-of-memory-error

with kind regards
Jan

-- 
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/CAGm-bLZL%2B0TojRDi-9vpRKUZvCKbY8d%3DUJM70dQg6GUKLp7xTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Exception in thread "elasticsearch[graylog2-server][generic][T#1]"

2016-06-23 Thread Anant Sawant
Hi All !!

Graylog server is throwing following error. Exception in thread 
"elasticsearch[graylog2-server][generic][T#1]"
Exception: java.lang.OutOfMemoryError thrown from the 
UncaughtExceptionHandler in thread 
"elasticsearch[graylog2-server][generic][T#1]".
complete logs trace is as follows


2016-06-23 12:30:47,811 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded 
plugins: [AWS input 0.5.0 [com.graylog2.plugin.AWSInputPlugin], Anonymous 
Usage Statistics 1.1.1 
[org.graylog.plugins.usagestatistics.UsageStatsPlugin], HttpMonitorInput 
1.0.0 [org.graylog2.plugin.httpmonitor.HttpMonitorInputPlugin]]
2016-06-23 12:30:47,950 INFO : org.graylog2.bootstrap.CmdLineTool - Running 
with JVM arguments:
2016-06-23 12:30:48,806 INFO : 
org.graylog2.shared.system.stats.SigarService - Failed to load SIGAR. 
Falling back to JMX implementations.
2016-06-23 12:30:50,809 INFO : org.graylog2.shared.buffers.InputBufferImpl 
- Message journal is enabled.
2016-06-23 12:30:51,279 INFO : kafka.log.LogManager - Loading log 
'messagejournal-0'
2016-06-23 12:30:51,756 INFO : org.graylog2.shared.journal.KafkaJournal - 
Initialized Kafka based journal at data/journal
2016-06-23 12:30:51,765 INFO : org.graylog2.shared.buffers.InputBufferImpl 
- Initialized InputBufferImpl with ring size <65536> and wait strategy 
, running 2 parallel message handlers.
2016-06-23 12:30:51,997 INFO : org.graylog2.plugin.system.NodeId - Node ID: 
c942aae1-e8e7-4d6a-899e-bfc0e3f10703
2016-06-23 12:30:52,329 INFO : org.elasticsearch.node - [graylog2-server] 
version[1.6.2], pid[3547], build[6220391/2015-07-29T09:24:47Z]
2016-06-23 12:30:52,329 INFO : org.elasticsearch.node - [graylog2-server] 
initializing ...
2016-06-23 12:30:52,425 INFO : org.elasticsearch.plugins - 
[graylog2-server] loaded [graylog2-monitor], sites []
2016-06-23 12:30:54,215 INFO : org.elasticsearch.node - [graylog2-server] 
initialized
2016-06-23 12:30:54,224 INFO : org.graylog2.shared.buffers.ProcessBuffer - 
Initialized ProcessBuffer with ring size <65536> and wait strategy 
.
2016-06-23 12:30:55,901 INFO : 
org.graylog2.bindings.providers.RulesEngineProvider - No static rules file 
loaded.
2016-06-23 12:30:55,983 INFO : org.graylog2.buffers.OutputBuffer - 
Initialized OutputBuffer with ring size <65536> and wait strategy 
.
2016-06-23 12:30:56,250 INFO : 
org.hibernate.validator.internal.util.Version - HV01: Hibernate 
Validator 5.1.3.Final
2016-06-23 12:30:56,650 INFO : org.graylog2.bootstrap.ServerBootstrap - 
Graylog server 1.1.6 (${git.commit.id.abbrev}) starting up. (JRE: Oracle 
Corporation 1.7.0_79 on Linux 2.6.32-573.18.1.el6.x86_64)
2016-06-23 12:30:56,742 INFO : 
org.graylog2.shared.initializers.PeriodicalsService - Starting 21 
periodicals ...
2016-06-23 12:30:56,771 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.ThroughputCounterManagerThread] 
periodical in [0s], polling every [1s].
2016-06-23 12:30:56,774 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.ThroughputCalculator] periodical in [0s], 
polling every [1s].
2016-06-23 12:30:56,774 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.AlertScannerThread] periodical in [10s], 
polling every [60s].
2016-06-23 12:30:56,774 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.BatchedElasticSearchOutputFlushThread] 
periodical in [0s], polling every [1s].
2016-06-23 12:30:56,774 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.ClusterHealthCheckThread] periodical in 
[0s], polling every [20s].
2016-06-23 12:30:56,774 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.ContentPackLoaderPeriodical] periodical, 
running forever.
2016-06-23 12:30:56,795 INFO : org.elasticsearch.node - [graylog2-server] 
starting ...
2016-06-23 12:30:56,796 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.DeadLetterThread] periodical, running 
forever.
2016-06-23 12:30:56,796 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.GarbageCollectionWarningThread] 
periodical, running forever.
2016-06-23 12:30:56,797 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.IndexerClusterCheckerThread] periodical 
in [0s], polling every [30s].
2016-06-23 12:30:56,797 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.IndexRetentionThread] periodical in [0s], 
polling every [300s].
2016-06-23 12:30:56,797 INFO : org.graylog2.periodical.IndexRetentionThread 
- Elasticsearch cluster not available, skipping index retention checks.
2016-06-23 12:30:56,798 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.IndexRotationThread] periodical in [0s], 
polling every [10s].
2016-06-23 12:30:56,798 INFO : org.graylog2.periodical.Periodicals - 
Starting [org.graylog2.periodical.NodePingThread] periodical in [0s], 
polling every [1s].
2016-