we often see an issue that is identical to the one described here: Tentacle service fails to start on occasion
we see the same error messages:
“A timeout was reached (30000 milliseconds) while waiting for the Octopus Tentacle service to connect.”
“The Octopus Tentacle service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.”
when this occurs, we don’t also see service startup failures for other windows services, whether they’re first-party microsoft or third-party services. the affected devices are all vm’s running windows server 2016 core, fully patched as of this writing.
it does not occur on every boot, and i have not been able to discern a pattern.
i see the registry modification in the aforementioned topic from 2012, but i would hate to have to push a registry hack to all my vm’s just to fix an issue with one service.
are there any options in octopus/tentacle that i can modify, or has there been any further progress on the tentacle code solution that was mentioned?