"Failed to report collector status to server" on sidecar side

Graylog Central (peer support)
1

Hello,

we’re using graylog-sidecar to collect some logs, it works fine and logs are delivered to Graylog and I can see sidecar in overview with status “running”.

sht_Selection_217
sht_Selection_217850×498 27.4 KB

But we still get " level=error msg="[UpdateRegistration] Failed to report collector status to server: Put https://log.berlin.ni.team/api/sidecars/sdbs-test11.example.com: EOF" in sidecard logs every minutes.
i’ve tried to disable “send_status” option and change node_id to some generated from “uuidgen”, but still the same error which confuse us and developers.

sidecar.yaml

---
server_url: https://log.example.com/api/
server_api_token: cao3jihhcvrt8ec5ffhes2d0hr7c144vg4q9g1g0qcc3bjauc1r
node_name: sdbs-test11.example.com
update_interval: 10
tls_skip_verify: false
send_status: true
node_id: sdbs-test11.example.com
#collector_id: file:/etc/graylog/sidecar/collector-id
cache_path: "/var/cache/graylog/collector-sidecar"
log_path: "/var/log/graylog/collector-sidecar"
log_rotation_time: 86400
log_max_age: 604800
backends:
- name: nxlog
  enabled: false
  binary_path: "/usr/bin/nxlog"
  configuration_path: "/var/lib/graylog-sidecar/generated/nxlog.conf"
- name: filebeat
  enabled: true
  binary_path: "/usr/bin/filebeat"
  configuration_path: "/var/lib/graylog-sidecar/generated/filebeat.conf"

Graylog version 3.2.3
Sidecar version 1.0.2

2

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