Graylog collector (v0.5.0) hangs when log file size increased to GB


(Amit Shah) #1

Hello,

Issue: Graylog collector process shows as running when checked with below commands

  1. /etc/init.d/graylog-collector status
  2. ps -ef | grep graylog-collector
    But actually it is not sending logs when data increase inside log files.

OS: Amazon Linux
OS VERSION_ID=“2017.03"
Graylog Collector Version: 0.5.0.
File: Graylog collector
COLLECTOR_JAVA_DEFAULT_OPTS=”-Xms1024m -Xmx1024m -Djava.library.path=$COLLECTOR_ROOT/lib/sigar"

Thanks,
Amit.

Thread dump of graylog-collector process: -

2017-09-19 05:38:37
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.141-b15 mixed mode):

"Attach Listener" #157 daemon prio=9 os_prio=0 tid=0x00007fe028001000 nid=0x3b82 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
	- None

"Keep-Alive-Timer" #156 daemon prio=8 os_prio=0 tid=0x00007fdffc049800 nid=0x3b0a waiting on condition [0x00007fe0078f9000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
	at java.lang.Thread.sleep(Native Method)
	at sun.net.www.http.KeepAliveCache.run(KeepAliveCache.java:172)
	at java.lang.Thread.run(Thread.java:748)

   Locked ownable synchronizers:
	- None
...
.....
.......
"GC task thread#6 (ParallelGC)" os_prio=0 tid=0x00007fe074028800 nid=0x565b runnable 
"GC task thread#7 (ParallelGC)" os_prio=0 tid=0x00007fe07402a800 nid=0x565c runnable 
"VM Periodic Task Thread" os_prio=0 tid=0x00007fe07421c000 nid=0x5666 waiting on condition 
JNI global references: 359

Graylog collector (v0.5.0) gets hang
(Jochen) #2

The Graylog Collector is unmaintained and won’t be developed any further. It’s basically abandonware.

I’d recommend switching to another log shipper, such as Logstash, Filebeat, or NXLOG, possibly in combination with the Graylog Collector Sidecar.


(Amit Shah) #3

Thanks @jochen. Appreciate your quick response. We are planing to shift to sidecar. But currently production release is near by. Any help to handle above is very helpful to us in current situation.

Thanks and Regards,
Amit.


(Jochen) #4

It might be a bug in Graylog Collector but there won’t be a bug fix, so I’d recommend switching to another log shipper as soon as possible.


(Amit Shah) #5

Thanks @jochen.

Regards,
Amit.


(Amit Sharma) #6

nohup /bin/java -Xms256m -Xmx512m -Djava.library.path=/usr/share/graylog-collector/lib/sigar -Dlog4j.configurationFile=/etc/graylog/collector/log4j2.xml -jar /usr/share/graylog-collector/graylog-collector.jar run -f /etc/graylog/collector/collector.conf &

solved the issue for me


(system) #7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.