Hey @itsystemshq,
Thank you for that response, a collegue has just sent me an article from our forums to show you which may help. I don’t know if you have seen this but it looks to be pretty close to what you are trying to achieve.
We also have this page (which I should have linked in my inital response) which details how you go about making sure your tentacles are polling to all of your nodes not just one.
Are you able to have a look and make sure you have not missed anything from a configuration point of view that could cause the issues you are experiencing? If you have seen the articles already let me know and I will look out for the logs.
As for the polling tentacles we have some documentation on how they communicate with Octopus here, that explains it a lot better than I can over a forum post.
Basically the health check is run by the Octopus server to the tentacle via a script (similar to this one - that checks disk space which is also done on the full health check but you get the gist). Octopus will run automated health checks to workers via scheduled tasks and it also does it on deployments to that target and manually when a user requests it (also on initial tentacle registration).
I think the top article will get you to a resolution and might explain why your health checks are failing when running a new Octopus node.
Let me know if that answers your health check query for polling tentacles and also how you get on with that article.
Kind Regards,
Clare