Not getting data on Collector-Sidecar

Graylog Central (peer support)
,
1

Hello,

I had installed collector-sidecar version 0.1.0 on CentOS 7, all collectors on running state, but I didn’t get any log messages on Graylog

INFO[0000] Using collector-id: 6219a2a2-a1d7-4416-a964-a71ccffa2d86
INFO[0000] Fetching configurations tagged by: [linux apache]
DEBU[0000] Creating rotated log writer for: /var/log/graylog/collector-sidecar/collector_sidecar.log.%Y%m%d%H%M
DEBU[0000] Add collector backend: filebeat
INFO[0000] Starting signal distributor
DEBU[0000] [signal-processor] (seq=1) handling cmd: restart
INFO[0000] [filebeat] Starting (exec driver)
DEBU[0000] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M
DEBU[0000] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M
DEBU[0000] [signal-processor] (seq=1) cmd done: restart
INFO[0010] [filebeat] Configuration change detected, rewriting configuration file.
DEBU[0010] [signal-processor] (seq=2) handling cmd: restart
INFO[0010] [filebeat] Stopping
DEBU[0012] [filebeat] SIGHUP ignored, killing process
DEBU[0012] [filebeat] Failed to kill process os: process already finished
INFO[0012] [filebeat] Starting (exec driver)
DEBU[0012] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M
DEBU[0012] Creating rotated log writer for: /var/log/graylog/collector-sidecar/filebeat_stderr.log.%Y%m%d%H%M
DEBU[0012] [signal-processor] (seq=2) cmd done: restart
DEBU[0020] [RequestConfiguration] No configuration update available, skipping update.
2

I am seeing the same exact issue you are. Did you ever find a solution for this? Logs had been working perfectly fine and then suddenly almost all of our logs stopped flowing in. Have the same debug information as you provided above. Would love to hear if/how you solved this issues.

3

yeah, I had resolved this issue. You need to check your filebeat configurations and Tags on collectors

1 Like