Force a clearing of the tentacle queue

I have a PowerShell script I am working on and due to a license agreement pop-up the process hangs. I have resolved the PowerShell script to work around this, but my problem is with the Octopus Tentacle queue. I have used the Octopus Tentacle Manager to stop > re-install > start the service, but I still get the following when I try running a further deployment : -

2014-03-10 11:51:21.4533 WARN Deployment mutex started up with 'Deploying package App, version 3.9.3748.83' holding it.

Is there a way I can clear the queue on the Octopus Tentacle?

Cheers

Steve

Hi Steve,

Can you:

  1. Stop the running Octopus Deploy: Tentacle windows service
  2. Delete the Actors and Messages folders under: C:\Octopus\Tentacle
  3. Start the Octopus Deploy: Tentacle windows service

This will purge the data that is preventing the deployment from continuing. This bug should be fixed in the latest release so that it doesn’t happen again, but for now you’ll need to perform the steps above.

Please let me know if that works for you,

Paul

Thanks Paul,

That’s done the job!

Cheers

Steve

Hi Paul,

So it appears there are a few issues when trying to reconnect after deleting the Actors and Messages folders : -

@@@
2014-03-11 10:49:42.4181 ERROR Error in Octopus.SquidFinder@SQ-HXC30313-8E568EB3 while receiving 13d2ee84-a0a6-4e6a-a588-ee7052a5da7e
System.InvalidOperationException: The actor Octopus.SquidFinder@SQ-HXC30313-8E568EB3 cannot receive Octopus.Server.Communications.Handshaking.PassiveTentacleHandshakeReply
at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\Actor.cs:line 132
@@@

@@@
2014-03-11 10:49:42.4361 ERROR Undeliverable message detected: Pipefish.Messages.Delivery.DeliveryFailureEvent from: Octopus.SquidFinder@SQ-HXC30313-8E568EB3 to: PassiveTentacleHandshaker-AQ-tRbC3a3w@SQ-HXC30313-8E568EB3

  • Body is: {“FailedMessage”:{“Id”:“13d2ee84-a0a6-4e6a-a588-ee7052a5da7e”,“From”:{“SerializedValue”:“PassiveTentacleHandshaker-AQ-tRbC3a3w@SQ-HXC30313-8E568EB3”},“Headers”:{“Expires-At”:“635327237671986730”,“In-Reply-To”:“3e281f1e-2a48-4aad-86de-3994f22b48a7”,“MessageStore-Envelope-NoFwd”:“08D10B2EB52D262A00000055”},“To”:{“SerializedValue”:“Octopus.SquidFinder@SQ-HXC30313-8E568EB3”},“MessageType”:“Octopus.Server.Communications.Handshaking.PassiveTentacleHandshakeReply”,“Body”:{"$type":“Octopus.Server.Communications.Handshaking.PassiveTentacleHandshakeReply, Octopus.Server”,“Squid”:“SQ-HXC30316-657A6BD6”,“Thumbprint”:“D0C1729526F2F507D7490CA8D96F14DAAEFE806A”}},“Error”:{“Message”:“The message could not be handled”,“Detail”:“System.InvalidOperationException: The actor Octopus.SquidFinder@SQ-HXC30313-8E568EB3 cannot receive Octopus.Server.Communications.Handshaking.PassiveTentacleHandshakeReply\r\n at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\Actor.cs:line 132”}}
    @@@

@@@
2014-03-11 10:49:43.4813 ERROR Error in PassiveTentacleHandshaker-BQ-tRbeXsns@SQ-HXC30313-8E568EB3 while receiving 63ed26bb-3ec6-4e97-b334-183d9158162f
System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 10.204.22.101:10933
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 Octopus.Server.Communications.Handshaking.PassiveTentacleHandshaker.Receive(PassiveTentacleHandshakeRequest message) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Communications\Handshaking\PassiveTentacleHandshaker.cs:line 56
at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\Actor.cs:line 113
@@@

@@@
2014-03-11 10:49:43.5813 FATAL
System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 10.204.22.101:10933
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 Octopus.Server.Communications.Handshaking.PassiveTentacleHandshaker.Receive(PassiveTentacleHandshakeRequest message) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Communications\Handshaking\PassiveTentacleHandshaker.cs:line 56
at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\Actor.cs:line 113
@@@

@@@
2014-03-11 10:49:43.5873 ERROR Failed to discover SQUID for Magic file server
Pipefish.Errors.PipefishCommunicationException: No connection could be made because the target machine actively refused it 10.204.22.101:10933
at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
at Octopus.Server.Communications.Handshaking.PassiveTentacleSquidFinder.d__f.MoveNext() in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Communications\Handshaking\PassiveTentacleSquidFinder.cs:line 98
System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 10.204.22.101:10933
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 Octopus.Server.Communications.Handshaking.PassiveTentacleHandshaker.Receive(PassiveTentacleHandshakeRequest message) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Communications\Handshaking\PassiveTentacleHandshaker.cs:line 56
at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\Actor.cs:line 113
@@@

Hi Steven,

Would you be available to do a Skype call or another screen sharing session to try and resolve this?

Paul

Hi Paul,

Unfortunately it appears that the error went away with time and I haven’t been able to re-produce it since.

I will let you know if this starts up again

Cheers

Steve