Hi, is there any reason --disable-cloud is passed unconditionally? Would you accept a patch that turns this into disabled-by-default useflag? and before I dive into in, are there any gotchas I might miss?
(In reply to Georgy Yakovlev from comment #0) > Hi, > is there any reason --disable-cloud is passed unconditionally? > Would you accept a patch that turns this into disabled-by-default useflag? > and before I dive into in, are there any gotchas I might miss? Currently, netdata builds bundled copies of libwebsockets and mosquitto. That's unacceptable in Gentoo, and since those are requirements for netdata's cloud functionality, it means we can't enable netdata cloud. The issue is being worked upstream at https://github.com/netdata/netdata/issues/8961 - if you can contribute improvements to that effort, we can get netdata cloud into Gentoo more quickly :) Thanks!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5553a5324a97a386f873234a8a24c9bcff2414e0 commit 5553a5324a97a386f873234a8a24c9bcff2414e0 Author: Craig Andrews <candrews@gentoo.org> AuthorDate: 2021-04-13 00:05:05 +0000 Commit: Craig Andrews <candrews@gentoo.org> CommitDate: 2021-04-13 00:05:36 +0000 net-analyzer/netdata: 1.30.1 version bump Add cloud USE flag Closes: https://bugs.gentoo.org/751487 Package-Manager: Portage-3.0.18, Repoman-3.0.3 Signed-off-by: Craig Andrews <candrews@gentoo.org> net-analyzer/netdata/Manifest | 1 + net-analyzer/netdata/metadata.xml | 1 + net-analyzer/netdata/netdata-1.30.1.ebuild | 139 +++++++++++++++++++++++++++++ net-analyzer/netdata/netdata-9999.ebuild | 11 +-- 4 files changed, 147 insertions(+), 5 deletions(-)
Yeah but doesn't work. Any claimed nodes like that show up as unreachable on Netdata Cloud. Non-Gentoo nodes work fine. log: 2021-04-14 17:05:58: netdata INFO : ACLK_Main : Attempting connection now 2021-04-14 17:05:58: netdata INFO : ACLK_Main : Setting ACLK target host=app.netdata.cloud port=443 from https://app.netdata.cloud 2021-04-14 17:05:58: netdata INFO : ACLK_Main : Retrieving challenge from cloud: app.netdata.cloud 443 /api/v1/auth/node/6f46af6a-ff1d-11e9-8762-3440b59ea5a8/challenge 2021-04-14 17:06:58: netdata ERROR : ACLK_Main : No response available - SSL_read()=0 2021-04-14 17:06:58: netdata ERROR : ACLK_Main : Challenge failed: 2021-04-14 17:06:58: netdata ERROR : ACLK_Main : [mqtt_wss] E: Error with MQTT connect "MQTT_ERROR_CONNECTION_REFUSED" (errno 11, Resource temporarily unavailable) 2021-04-14 17:06:58: netdata ERROR : ACLK_Main : Connect failed 2021-04-14 17:06:58: netdata INFO : ACLK_Main : Wait before attempting to reconnect in 1024.000 seconds while the socket has data available but apparently is never read: State Recv-Q Send-Q Local Address:Port Peer Address:Port Process CLOSE-WAIT 3015 0 10.11.1.18:60690 35.196.244.138:443
(In reply to Ortwin Glueck from comment #3) > Yeah but doesn't work. Any claimed nodes like that show up as unreachable on > Netdata Cloud. Non-Gentoo nodes work fine. > > log: > 2021-04-14 17:05:58: netdata INFO : ACLK_Main : Attempting connection now > 2021-04-14 17:05:58: netdata INFO : ACLK_Main : Setting ACLK target > host=app.netdata.cloud port=443 from https://app.netdata.cloud > 2021-04-14 17:05:58: netdata INFO : ACLK_Main : Retrieving challenge from > cloud: app.netdata.cloud 443 > /api/v1/auth/node/6f46af6a-ff1d-11e9-8762-3440b59ea5a8/challenge > 2021-04-14 17:06:58: netdata ERROR : ACLK_Main : No response available - > SSL_read()=0 > 2021-04-14 17:06:58: netdata ERROR : ACLK_Main : Challenge failed: > 2021-04-14 17:06:58: netdata ERROR : ACLK_Main : [mqtt_wss] E: Error with > MQTT connect "MQTT_ERROR_CONNECTION_REFUSED" (errno 11, Resource temporarily > unavailable) > 2021-04-14 17:06:58: netdata ERROR : ACLK_Main : Connect failed > > 2021-04-14 17:06:58: netdata INFO : ACLK_Main : Wait before attempting to > reconnect in 1024.000 seconds > > while the socket has data available but apparently is never read: > State Recv-Q Send-Q Local > Address:Port Peer Address:Port Process > > CLOSE-WAIT 3015 0 > 10.11.1.18:60690 35.196.244.138:443 Do you think you're experiencing this issue? https://github.com/netdata/netdata/pull/10805
thanks for adding btw, works for me with net-analyzer/netdata-1.31.0
(In reply to Georgy Yakovlev from comment #5) > thanks for adding btw, works for me with net-analyzer/netdata-1.31.0 Fantastic! And thank you for following up and letting me know
