Node status is NOT CAPABLE for Ubuntu 20.04

Help
,
1

I tried the * kickstart.sh to add node option from netdata cloud dash, but Node status is NOT CAPABLE for my Ubuntu 20.04.
Refer to ML: NOT CAPABLE for ALMALINUX, I share below information:

  1. I tried the * kickstart.sh to add node option from netdata cloud dash.
  2. $ uname -a; grep -HvE “^#|URL” /etc/*release
    Linux pek-hguo3-d2 5.15.0-69-generic #76~20.04.1-Ubuntu SMP Mon Mar 20 15:54:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
    /etc/lsb-release:DISTRIB_ID=Ubuntu
    /etc/lsb-release:DISTRIB_RELEASE=20.04
    /etc/lsb-release:DISTRIB_CODENAME=focal
    /etc/lsb-release:DISTRIB_DESCRIPTION=“Ubuntu 20.04.6 LTS”
    /etc/os-release:NAME=“Ubuntu”
    /etc/os-release:VERSION=“20.04.6 LTS (Focal Fossa)”
    /etc/os-release:ID=ubuntu
    /etc/os-release:ID_LIKE=debian
    /etc/os-release:PRETTY_NAME=“Ubuntu 20.04.6 LTS”
    /etc/os-release:VERSION_ID=“20.04”
    /etc/os-release:VERSION_CODENAME=focal
    /etc/os-release:UBUNTU_CODENAME=focal
  3. $ /opt/netdata/bin/srv/netdata -W buildinfo
    Version: netdata v1.38.1
    Configure options: ‘–prefix=/opt/netdata/usr’ ‘–sysconfdir=/opt/netdata/etc’ ‘–localstatedir=/opt/netdata/var’ ‘–libexecdir=/opt/netdata/usr/libexec’ ‘–libdir=/opt/netdata/usr/lib’ ‘–with-zlib’ ‘–with-math’ ‘–with-user=netdata’ ‘–enable-cloud’ ‘–without-bundled-protobuf’ ‘–disable-dependency-tracking’ ‘CFLAGS=-static -O2 -I/openssl-static/include -pipe’ ‘LDFLAGS=-static -L/openssl-static/lib’ ‘PKG_CONFIG_PATH=/openssl-static/lib/pkgconfig’
    Install type: kickstart-static
    Binary architecture: x86_64
    Features:
    dbengine: YES
    Native HTTPS: YES
    Netdata Cloud: YES
    ACLK: YES
    TLS Host Verification: YES
    Machine Learning: YES
    Stream Compression: YES
    Libraries:
    protobuf: YES (system)
    jemalloc: NO
    JSON-C: YES
    libcap: NO
    libcrypto: YES
    libm: YES
    tcalloc: NO
    zlib: YES
    Plugins:
    apps: YES
    cgroup Network Tracking: YES
    CUPS: NO
    EBPF: YES
    IPMI: NO
    NFACCT: NO
    perf: YES
    slabinfo: YES
    Xen: NO
    Xen VBD Error Tracking: NO
    Exporters:
    AWS Kinesis: NO
    GCP PubSub: NO
    MongoDB: NO
    Prometheus Remote Write: YES
    Debug/Developer Features:
    Trace Allocations: NO
  4. $ ps aux | grep netdata
    netdata 1760448 2.0 0.3 245052 53292 ? SNsl 09:56 0:03 /opt/netdata/bin/srv/netdata -P /run/netdata/netdata.pid -D
    netdata 1760451 0.0 0.0 19216 3496 ? SNl 09:56 0:00 /opt/netdata/bin/srv/netdata --special-spawn-server
    netdata 1760712 0.1 0.0 1916 1428 ? SN 09:56 0:00 bash /opt/netdata/usr/libexec/netdata/plugins.d/tc-qos-helper.sh 1
    netdata 1760720 0.4 0.1 40156 27176 ? SNl 09:56 0:00 /usr/bin/python3 /opt/netdata/usr/libexec/netdata/plugins.d/python.d.plugin 1
    netdata 1760753 0.6 0.2 774508 48436 ? SNl 09:56 0:01 /opt/netdata/usr/libexec/netdata/plugins.d/go.d.plugin 1
    root 1760755 4.0 0.0 58712 5740 ? SNl 09:56 0:07 /opt/netdata/usr/libexec/netdata/plugins.d/apps.plugin 1
    root 1760756 0.3 0.0 82940 9092 ? SNl 09:56 0:00 /opt/netdata/usr/libexec/netdata/plugins.d/ebpf.plugin 1

Could I get guide to check its reason?

Thanks a lot,
Heng

2

We’ve been trying to find someone with some insight as to how this could happen, but it’s not a clear cut case. It’s not forgotten though.

3

Hi @hguo3, sorry for the long delay.

Could you please share a screenshot on the cloud on where exactly the Not Capable appears?

4

screenshot3
screenshot31841×996 74.7 KB

screenshot2
screenshot21837×997 92.3 KB

screenshot1
screenshot11844×1012 140 KB

Sorry for late reply, because last few days are holiday. Here is the screenshot.

5

Ok, thanks @hguo3

So it appears as if the claim process was okay (the agent contacted the cloud and registered itself) but it doesn’t really connect.

Can you please share your error.log file (should be under /opt/netdata/var/log) to manolis@netdata.cloud ?

Thanks!

6

Email with all logs at /opt/netdata/var/log/netdata was sent.

Br,
Heng

7

Thanks @hguo3.

Indeed, from your logs, the agent does not connect to the cloud. There is a problem with the SSL certificate:

2023-05-05 11:01:35: netdata INFO  : ACLK_MAIN : Attempting connection now
2023-05-05 11:01:36: netdata ERROR : ACLK_MAIN : Cert Chain verify error:num=2:unable to get issuer certificate:depth=2:/DC=com/DC=wrs/DC=ad/DC=corp/CN=corp-ALA-CA01-CA (errno 2, No such file or directory)
2023-05-05 11:01:36: netdata ERROR : ACLK_MAIN : SSL_write Err: SSL_ERROR_SSL
2023-05-05 11:01:36: netdata ERROR : ACLK_MAIN : Couldn't write HTTP request header into SSL connection (errno 22, Invalid argument)
2023-05-05 11:01:36: netdata ERROR : ACLK_MAIN : Couldn't process request
2023-05-05 11:01:36: netdata ERROR : ACLK_MAIN : Error trying to contact env endpoint (errno 22, Invalid argument)
2023-05-05 11:01:36: netdata ERROR : ACLK_MAIN : Failed to Get ACLK environment
2023-05-05 11:01:36: netdata INFO  : ACLK_MAIN : Wait before attempting to reconnect in 0.944 seconds

I’m not sure what the situation is, but I will try to replicate it. Not sure as well, do you have a latest ca-certificates package in your system (Focal (20.04) : ca-certificates package : Ubuntu) ?

8

Thanks, will try latest ca-certificates package 20.04 and reply you later.

Br,

Heng