Good morning Netdata people!
Unfortunately after many days of working without a problem (see this thread for more information and performed actions) this morning my hosts are “Unreachable” again.
EDIT: I didn’t want to hijack that thread hence the new one. Plus it seems to be a totally new issue
Once again the reason (I assume) was that the ACLK-NG flag was ignored on the daily automatic update.
All are affected
Since I have set the
aclk implementation = ng
netdata.conf file I was expecting this to be used in auto updates.
Indeed this was the case for some time now but again today it has reverted and from the API info I can see that:
_aclk_ng_available "false" _aclk_legacy_available "true" _aclk_impl "Legacy"
Why is this happening?
I am sorry to say it but I am really frustrated with Netdata not working as it should and doing things on its own…Please excuse my language here but it doesn’t look very robust
EDIT: What I 'd like to say here is that the purpose of a monitoring system like Netdata should be “set it and forget it”. Instead I need to always have it in my mind and check over it again and again.
Here is the buildinfo:
# netdata -W buildinfo
Version: netdata v1.31.0-105-nightly
Configure options: ‘–prefix=/usr’ ‘–sysconfdir=/etc’ ‘–localstatedir=/var’ ‘–libexecdir=/usr/libexec’ ‘–libdir=/usr/lib’ ‘–with-zlib’ ‘–with-math’ ‘–with-user=netdata’ ‘–with-bundled-lws’ ‘–with-bundled-libJudy’ ‘CFLAGS=-O2’ ‘LDFLAGS=’
Native HTTPS: YES
Netdata Cloud: YES
ACLK Next Generation: NO
ACLK Legacy: YES
TLS Host Verification: YES
LWS: YES static v3.2.2
cgroup Network Tracking: YES
Xen VBD Error Tracking: NO
AWS Kinesis: NO
GCP PubSub: NO
Prometheus Remote Write: NO