I have a working installation of Octopus Deploy 1.6.1.1718 running on my server. However whenever the machine is restarted I have to go onto the box and start the service manually.
It is set to Automatic start yet never starts. When I start the service manually it works fine with no errors.
No events relating to the service are written to the EventLog.
Any logs would be written to the Windows application event log; we don’t currently write any messages to disk but we will in Octopus 2.0.
You could try using sc.exe from the command line to give the service a dependency on the built-in Workstation (LanmanWorkstation) service. This should make our service start once the rest of the machine has started.
We have a similar problem. I have the tentacle installed on about 30 machines - a mix of 2008 and 2003 servers. When we patch and reboot our servers, the agent will randomly not start on some of them. Sometimes it starts, sometimes it doesn’t.
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.
We’re hoping for a v2 release in August/September. Delayed start seems to work for some people. Adding a dependency on LanmanWorkstation seems to work for other people.