Tentacle 2.3.6.1385 connectivity error

Legacy Uncategorised
1

we have had v2.3.6 of octopus and tentacles installed for a while. over the last week or so, we started getting the error shown below under Environments and cannot deploy anything to this server anymore. any ideas on what might be the cause?

I have tried recycling the octopus tentacle service.
I cannot browse to the url that normally says whether its running or not
Windows firewall seems to still have the correct setting for octopus.

Connectivity
×
More information…
Secure TCP connection to https://pre-esbx6401:10933/mx/v1 0 2
Connected. The last attempt to exchange messages failed. The connection is idle and won’t poll until an outgoing message is sent.
Last connected 18 hours ago
Expiring. The last attempt to exchange messages failed. The connection is idle and won’t poll until an outgoing message is sent.
Last connected 18 hours ago
Not connected. The last attempt to exchange messages failed. The connection is idle and won’t poll until an outgoing message is sent.
Last connected 18 hours ago
Not started. The last attempt to exchange messages failed. The connection is idle and won’t poll until an outgoing message is sent.
Show last failure »
The last recorded failure on the connection was:
Error 08:21:27
System.Net.Sockets.SocketException (0x80004005): A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port) at Pipefish.Transport.SecureTcp.Client.SecureTcpClient.Send(SecureTcpRequest request) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 39 at Pipefish.Transport.SecureTcp.MessageExchange.Client.ClientWorker.PerformExchange() in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\MessageExchange\Client\ClientWorker.cs:line 298 at Pipefish.Transport.SecureTcp.MessageExchange.Client.ClientWorker.Run() in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish.Transport.SecureTcp\MessageExchange\Client\ClientWorker.cs:line 173

2

Hi Kirk,

Thanks for getting in touch; I haven’t seen this error previously. Does a Reset button appear on the machine’s Connectivity tab? If so, pressing it should resolve any Octopus configuration issues related to the machine.

If that option isn’t available, can you please check the steps listed in: http://docs.octopusdeploy.com/display/OD/Troubleshoot+Listening+Tentacles

Though some may not apply, it would be useful to work out whether the issue is likely to be at the Tentacle end or the Octopus.

I assume also that you’ve tried restarting Octopus and the affected Tentacle.

Let me know what you find, I’ll do some further research on the possible causes of this error. Knowing the .NET and OS versions would also be handy.

Regards,
Nick

3

as it turns out we had an internal dns name issue causing our problem, so our IT department fixed the issue internally. it had nothing to do with Octopus, just an issue getting to the box in general. thanks for the suggestions though.

4

Excellent, thanks for following up!