Same machine on multiple instances fails health check


We are using the same machine in multiple environments. It fails the health check, and on checking the machine the OctopusDeploy Tentacle service had stopped. This is an automatic service and the health check passes once the service is started up again.

This has happened twice, where the service stops on it’s own. My understanding is that only one tentacle service needs to be running for the machine to be available in different environments. Is there anything I can do to fix this?

Thanks in advance,

The Event logs return this:

2014-07-09 14:39:08.3020 FATAL System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.Net.Sockets.TcpListener.Start(Int32 backlog)
at Pipefish.Transport.SecureTcp.Server.SecureTcpServer.Start() in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\Server\SecureTcpServer.cs:line 46
at Octopus.Tentacle.Communications.TcpServer.TcpServerDistributionConfig.StartApp() in y:\work\db516cd4dfb6f424\source\Octopus.Tentacle\Communications\TcpServer\TcpServerDistributionConfig.cs:line 87
at Octopus.Tentacle.Communications.TcpServer.TcpServerDistributionConfig.Start() in y:\work\db516cd4dfb6f424\source\Octopus.Tentacle\Communications\TcpServer\TcpServerDistributionConfig.cs:line 52
at Octopus.Tentacle.Communications.DistributionStarter.Start() in y:\work\db516cd4dfb6f424\source\Octopus.Tentacle\Communications\DistributionStarter.cs:line 17
at Octopus.Tentacle.Commands.RunAgentCommand.Start() in y:\work\db516cd4dfb6f424\source\Octopus.Tentacle\Commands\RunAgentCommand.cs:line 50
at Octopus.Shared.Startup.ConsoleHost.Run(Action`1 start, Action shutdown) in y:\work\db516cd4dfb6f424\source\Octopus.Shared\Startup\ConsoleHost.cs:line 36

2014-07-09 14:39:08.3320 FATAL The Tentacle was restarted during execution of the worker process.

Hi Ann,

Thanks for getting in touch!
There is no problem using the same machine in multiple environments, there is also no issue with having multiple tentacle installs on the one machine.
The problem comes when it shares a port. It needs to have a unique port per tentacle installation. This doesn’t just mean no sharing between tentacles, but also means no sharing on the machine for anything else using that port. This error tells us that its getting a conflict on bindings and thus stopping.

What version of Octopus/Tentacle are you running?
A bit more information about this specific setup might also help us nail this down. Thanks!



We have only one tentacle installed on this machine. All environments use the same port to access the tentacle.

Do I need to start different tentacle services for each environment this machine is used on?

We’re using Octopus version 2.0.


Hi Ann,

Yeah, it looks like you are doing everything correctly, and the way you have Octopus and your Tentacle is fine.
So we can only make the assumption that the port is being used by something outside of Octopus and Tentacle.
Could you try to re-install the Tentacle on another port and see if the issues persists?