How to disable ACLK?

[nikobearrr]

Question summary

I would like to disable ACLK. I am trying to follow this guide: https://learn.netdata.cloud/docs/agent/aclk but I do not think I succeed.

OS / Environment

Netdata v1.23.2 in docker

Component Name

aclk

Expected results

I have copied cloud.conf to /etc/netdata/cloud.d/cloud.conf and /var/lib/netdata/cloud.d/cloud.conf (just to be sure). So I don't expect to see anything ACLK related in my logs.

cloud.conf:

[global]
enabled = no

Also in my netdata.conf I have put:

[cloud]
statistics = no

But when I start netdata I see:

2020-07-19 12:49:36: netdata INFO  : ACLK_Main : thread created with task id 282
2020-07-19 12:49:36: netdata INFO  : ACLK_Main : set name of thread 282 to ACLK_Main
2020-07-19 12:49:36: netdata INFO  : ACLK_Main : Waiting for netdata to be ready
2020-07-19 12:49:36: netdata INFO  : ACLK_Main : Waiting for Cloud to be enabled
2020-07-19 12:49:36: netdata INFO  : ACLK_Main : Waiting for netdata to be claimed

Which leads me to think ACLK is running. How should I disable it?

[underhood]

@nikobearrr
There are multiple ways to achieve that. The safest is disabling cloud functionality at compile time.
For example using netdata-installer.sh --disable-cloud.

Important is ACLK doesn't initiate any network communication unless cloud is enabled and the node is claimed.
From your log file it seems node is not claimed so do not worry there is/will be no network connections made.

However if you set in file /var/lib/netdata/cloud.d/cloud.conf (location could be diferent depending on your install prefix) [global] key enabled = no it should stop at previous step:
2020-07-19 12:49:36: netdata INFO : ACLK_Main : Waiting for Cloud to be enabled

@Ferroin do you know inside the docker environment if the path is correct?

[underhood]

Just to be sure I tested on my local machine

2020-07-20 21:51:40: netdata INFO  : MAIN : EXIT: Stopping main thread: ACLK_Main
2020-07-20 21:51:40: netdata INFO  : ACLK_Main : thread with task id 62541 finished
2020-07-20 21:51:41: netdata INFO  : ACLK_Main : thread created with task id 63047
2020-07-20 21:51:41: netdata INFO  : ACLK_Main : set name of thread 63047 to ACLK_Main
2020-07-20 21:51:41: netdata INFO  : ACLK_Main : Waiting for netdata to be ready
2020-07-20 21:51:42: netdata INFO  : ACLK_Main : Waiting for Cloud to be enabled

and it seems to work, therefore it seems that your netdata in Docker doesn't see the cloud.conf

[nikobearrr]

Hi @underhood. Perhaps I am not using the correct path. As I said in my OP I have put it on 2 places "just to be sure" - doesn't mean they are correct though.

I can see more or less the same logs in my docker container, except the EXIT: Stopping main thread: ACLK_Main. However, after it says that for you, 1 second later it creates a new thread with the same name and waits to be ready/enabled. This is also what I see:

2020-07-19 12:49:36: netdata INFO  : ACLK_Main : Waiting for Cloud to be enabled
2020-07-19 12:49:36: netdata INFO  : ACLK_Main : Waiting for netdata to be claimed

Should I that that it works in that case? Perhaps I am just a little bit confused about this.

[underhood]

@nikobearrr the EXIT is from the restart of netdata. I restarted the agent after changing the configuration so starting from 2020-07-20 21:51:41 is the relevant logs

[Ferroin]

The path for the cloud.d directory should be the same for the Docker containers, though that path may not already exist. AFAICT we shouldn't be doing anything in the Docker container build that would prevent this from working correctly.

[stale]

This issue has been inactive for 30 days. It will be closed in one week, unless it is updated.

[stale]

This issue has been automatically closed due to extended period of inactivity. Please reopen if it is still valid. Thank you for your contributions.