I end up with tentacle nicely registered on octopus server, but after first health check tentacle is unreachable, going onto the machine, and checking services, there is no tentacle service
Thanks for getting in touch. Tentacle connection issues can be quite tricky to troubleshoot, as it’s a complicated area where there’s a lot of moving parts that will impact the communication.
The fastest way to hopefully resolve your issue will be to go through our tentacle troubleshooting guide, it has lots of detailed sections for all the possible scenarios and will help us pinpoint your issue https://octopus.com/docs/how-to/troubleshoot-polling-tentacles
Let us know if any part of it is unclear or you get stuck.
Ignore roles and environment parameter… This function assumes you have a bat file on local machine that has environment and roles
(i.e go through tentacle setup wizard, copy cmd line at the end, and have your GetBatFile function make necessary changes to roles, environment and machine name)
We do something similar in that we run a script from the octopus server which cycles through a csv to create a new thumbprint and connect each server to Octopus with their appropriate roles. This does mean the tentacle has to already be installed
on the server however this is done as part of the initial build process for us.
This script has been embedded into our environment creation scripts to ensure we always have the tentacles connected throughout the life cycle.
If your interested I can upload a copy of it to here