We built and installed Netdata on AWS Linux 2. It installed without issue and is currently running; yet, the portal has “UNREACHABLE NEEDS UPDATE”. The needs update link says, “The agent on this node has an older version and an update is required. Please upgrade to agent version 1.26 or above.”; however, this was a new build done yesterday and is running 1.26.
$ netdata -V
netdata v1.26.0-375-nightly
We tried another EC2 instance and got the same error with nothing working on the portal.
@Stelios_Fragkakis I think version number was used for composite instead of an ACLK version. Who is the right person to check what is the logic that recognizes agent version on cloud side? Perhaps it has an issue with nightly build versions?
Have upgraded to netdata v1.26.0-400-nightly and still have the same error in netdata.cloud. Have the agent installed and running on 2 servers, but both present the same error:
If the agent is unreachable it means Netdata Cloud cannot connect to it so it doesn’t know its version yet. Currently Netdata Cloud has a known issue that it also shows “needs update” when it doesn’t know the agent version yet.
So this “needs update” is not true if you are using v1.26. The issue here is that you have an unreachable agent
We can help with that if you tell us a little bit more about your setup
Sure, these are AWS EC2 Micro and Small instances. We didn’t enable any ports in the AWS firewall because the assumption was that the agent would be connecting out, with nothing trying to connect inbound.
2020-12-17 04:25:40: netdata ERROR : ACLK_Main : Libwebsockets: SSL error: unable to get local issuer certificate (preverify_ok=0;err=20;depth=1)
(errno 2, No such file or directory)
I’ve checked the openssl.cnf file for correct paths and updated the ca trust and still no joy.
I am glad that you found the answer. So you couldn’t connect from Netdata Cloud to Netdata Agent because of the OpenSSL library. Can you please give me some more info in regards to your Netdata Agent? I think that the Agent should have signaled somehow that this is the error, instead if manually troubleshooting it.
During Agent installation, if you use the kickstart script, did it showed any error?