from time to time cloud is complaining that my agents need to be updated to a version newer than v.1.26 when I have already installed v.1.31.
The solution to the problem is to restart the “netdata” daemon but should this be happening in the first place?
I have to say here that I am on stable release and not on nightly.
I am also using the NextGeneration (NG) ACLK.
Here is the output from Netdata-Updater
Checking if a newer version of the updater script is available.
Downloading newest version of updater script.
Thu Sep 16 09:14:35 EEST 2021 : INFO: Running on a terminal - (this script also supports running headless from crontab)
Thu Sep 16 09:14:35 EEST 2021 : INFO: Current Version: 00103100000000
Thu Sep 16 09:14:35 EEST 2021 : INFO: Latest Version: 00103100000000
Thu Sep 16 09:14:35 EEST 2021 : INFO: Newest version (current=00103100000000 >= latest=00103100000000) is already installed
and here is the buildinfo:
# netdata -W buildinfo
Version: netdata v1.31.0
Configure options: ‘–prefix=/usr’ ‘–sysconfdir=/etc’ ‘–localstatedir=/var’ ‘–libexecdir=/usr/libexec’ ‘–libdir=/usr/lib’ ‘–with-zlib’ ‘–with-math’ ‘–with-user=netdata’ ‘–with-aclk-ng’ ‘CFLAGS=-O2’ ‘LDFLAGS=’
Native HTTPS: YES
Netdata Cloud: YES
Cloud Implementation: Next Generation
TLS Host Verification: YES
cgroup Network Tracking: YES
Xen VBD Error Tracking: NO
AWS Kinesis: NO
GCP PubSub: NO
Prometheus Remote Write: NO
I was not expecting to see an error/warning like this and that “netadata” daemon would not need to be restarted every now and then.