Issues installing Netdata on servers

Help
, , ,
1

I am new to Netdata and trying to install the agent on some servers to test. When I paste the install code from my cloud account it begins fine and installs but at the end I am getting the following issue

Extracting public key from private key.
writing RSA key
Failed to connect to https://app.netdata.cloud, return code 60
Connection attempt 1 failed. Retry in 1s.
Failed to connect to https://app.netdata.cloud, return code 60
Connection attempt 2 failed. Retry in 2s.
Failed to connect to https://app.netdata.cloud, return code 60
Connection attempt 3 failed. Retry in 3s.
grep: /opt/netdata/var/lib/netdata/cloud.d/tmpout.txt: No such file or directory
grep: /opt/netdata/var/lib/netdata/cloud.d/tmpout.txt: No such file or directory
Failed to claim node with the following error message:“Unknown HTTP error message”
WARNING Unable to claim node, you must do so manually.

I have tried this on multiple servers and get the same results. Any help would be appreciated.

2

Hello @John_Aucoin sorry for the late response, welcome in our community. Let me help you.

Have you installed the Agent in the the particular node? What steps have you made so far?

3

I have copied the code from my account and tried to install it on multiple servers. It installs the net data client fine but never claims

Thanks
John

4

Ok, let’s be more specific and focus on one node. Could you please answer to the followings:

  • Node’s OS, version of kernel
  • Share your Netdata version and build (run netdata -W buildinfo )
  • Could you access the Agent’s dashboard in this host? (It listens on port :19999)
5

Did you solve this issue? I think it is a kernel or SO related issue, not sure. In a Debian 8 relase the issue is present, but not in a Debian 10. I solved the problem using:
export PATH=“/opt/netdata/bin:${PATH}”

I used this solution from [Feat]: netdata-claim.sh is too cryptic, documentation missing · Issue #12186 · netdata/netdata · GitHub

6

Hello @g4br13l24 and welcome into our community

You mean that you faced the same error

. . .I am getting the following issue

Extracting public key from private key.
writing RSA key
Failed to connect to https://app.netdata.cloud, return code 60
Connection attempt 1 failed. Retry in 1s.
Failed to connect to https://app.netdata.cloud, return code 60
Connection attempt 2 failed. Retry in 2s.
Failed to connect to https://app.netdata.cloud, return code 60
Connection attempt 3 failed. Retry in 3s.
grep: /opt/netdata/var/lib/netdata/cloud.d/tmpout.txt: No such file or directory
grep: /opt/netdata/var/lib/netdata/cloud.d/tmpout.txt: No such file or directory
Failed to claim node with the following error message:“Unknown HTTP error message”
WARNING Unable to claim node, you must do so manually.

And it resolved just by adding/including the Netdata’s bin (you have static builds that’s why Agent is under /opt) folder into your path?

I am just curious not arguing, I am just aware that error code 60 is related to ca-certificates issues.

I think that just an update of the ca-certificates fixes the issue.

7

I will try to reproduce it in Debian 8 and let you know :slight_smile: :slight_smile:

8

Hello @Tasos_Katsoulas

Thank you! Yes, I faced same issue.

Failed to connect to https://app.netdata.cloud, return code 60
Connection attempt 1 failed. Retry in 1s.
Failed to connect to https://app.netdata.cloud, return code 60
Connection attempt 2 failed. Retry in 2s.
Failed to connect to https://app.netdata.cloud, return code 60
Connection attempt 3 failed. Retry in 3s.
grep: /opt/netdata/var/lib/netdata/cloud.d/tmpout.txt: No such file or directory
grep: /opt/netdata/var/lib/netdata/cloud.d/tmpout.txt: No such file or directory
Failed to claim node with the following error message:“Unknown HTTP error message”

I’m pretty sure the above message it was the same, with 60 error code.