Error : [UpdateRegistration] Failed to report collector status to server: Put http://<host>:9000/api/plugins/org.graylog.plugins.collector/collectors/ EOF

So im trying to install the collector on a centos7 vm.
I have done this on other machines, but i this one i keep this error:

“[UpdateRegistration] Failed to report collector status to server: Put http://:9000/api/plugins/org.graylog.plugins.collector/collectors/bee37efb-a8c1-4554-a163-273c6d17372d: EOF”

I keept on looking around but cannot find any reason for this error.

I have this configuration:

nano /etc/graylog/collector-sidecar/collector_sidecar.yml

server_url: http://host:9000/api/
update_interval: 10
tls_skip_verify: false
send_status: true
node_id: vm-root-dc1
collector_id: file:/etc/graylog/collector-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
- linux
- name: nxlog
enabled: true
binary_path: /usr/bin/nxlog
configuration_path: /etc/graylog/collector-sidecar/generated/nxlog.conf

When i start the service for the first time it get its configuration from graylog based on the tag “linux”, and it created the file needed.

I can also see the collector in the graylog server.
If i click “Show Messages” on this collector i can see all the error mesages from the vm collector.

Im using graylog server Graylog 2.2.3+7adc951 and collector-sidecar 0.1.8

What can i look at ?

I guess that your Graylog is not compatible with the Collector Sidecar version …

So ive just installed collector-sidecar 0.1.8 and nxlog ce 2.10 on three other machines, and everything freekin works …
I also tried to delete everything from this machine, that is having these errors, reinstalled collector-sidecar and nxlog ce, and it has the same behaviour.
It communicates with graylog, and sends eveything from /var/log/messages, including the error i mentioned.

AFAIK Graylog 2.2 does not have the API for the status updates. You should disable that int he sidecar configuration.

You should really update your Graylog to a more recent Version that also gets security updates and new features …

Well thats weird.
I have the same config for collector-sidecar on all of the machines.

By the way, if i access the link i get in the error, i get a json .

So the link is:

And the result is:

{“id”:“8b2bcc43-d3a8-427c-84cd-86db726a775c”,“active”:true,“node_id”:“cag3-root-dc1”,“node_details”:{“operating_system”:“Linux”,“tags”:[“linux”],“ip”:“”,“metrics”:{“disks_75”:,“cpu_idle”:99.95,“load_1”:0.0},“log_file_list”:null,“status”:{“status”:0,“message”:“1 collectors running”,“backends”:{“nxlog”:{“status”:0,“message”:“Running”}}}},“last_seen”:“2019-06-06T12:47:41.324Z”,“collector_version”:“0.1.8”}

Wouldnt this mean that the api exists and it works ?

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