Tentacle Stalling after Deployment Complete

Legacy Uncategorised
1

Hi there,

My tentacles keep stalling at the point as indicated below:

@@@
2014-05-24 11:03:38.7663 INFO Deployment complete.
2014-05-24 11:03:38.7819 TRACE Stored Octopus.Platform.Deployment.Logging.LogMessageEvent from TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103 to Octopus.Logger@SQ-VOUCHDEV-13D0EC6F (id: b96b42f68a6c475bae28acb946987eb5 env: 08D14556F353F2AB00000031)
2014-05-24 11:03:38.7819 TRACE Received a request from TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103 to release the deployment mutex acquisition 2871a72c-11b9-4df2-b6e8-e59731158af9
2014-05-24 11:03:38.9382 TRACE Supervised actor TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103 succeeding
2014-05-24 11:03:38.9538 TRACE Starting termination of supervised actor TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103
2014-05-24 11:03:38.9694 TRACE Operation is in progress in TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103, saving completion message
2014-05-24 11:03:38.9694 TRACE Post supervisee implicitly completed in supervised actor TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103
2014-05-24 11:03:38.9850 TRACE Operation Run Procedure is complete in supervised actor TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103
2014-05-24 11:03:38.9850 TRACE Completing supervised actor TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103 immediately
2014-05-24 11:03:39.0163 TRACE Stored Octopus.Platform.Deployment.Messages.Deploy.Package.TentaclePackageDeployedEvent from TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103 to DeployPackageActionOrchestrator-aQ-7z7_Oaog@SQ-VOUCHDEV-13D0EC6F (id: 2f845062689940a3a848bf74adaf0ca3 env: 08D14556F377B5F100000032)
2014-05-24 11:03:39.0475 TRACE Detaching TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103
2014-05-24 11:03:39.0475 TRACE Finished ServerTasks-1263/aef71f1d75bd4747bdd8995995522b66/05a67281298343f49c5ae26c6be7fdaa/1e1944194cf248c3b6d33b811ea5e3a0
2014-05-24 11:03:39.0632 TRACE Stored Octopus.Platform.Deployment.Logging.ProgressMessageEvent from TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103 to Octopus.Logger@SQ-VOUCHDEV-13D0EC6F (id: b533606c07eb4b82bd218926941dc24a env: 08D14556F37EDCFF00000033)
2014-05-24 11:03:39.0788 TRACE Stored Pipefish.Messages.Timing.ClearTimeoutsCommand from TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103 to Clock@SQ-ENJOVIA-APP1-F9755103 (id: 238dd64b65a7437f9a568dbf8f0fb804 env: 08D14556F3813F5900000034)
2014-05-24 11:03:39.0944 TRACE TentaclePackageDeployment-Aw-7z8BnWp7@SQ-ENJOVIA-APP1-F9755103 successfully detached
2014-05-24 11:03:46.5788 TRACE Accepted TCP client 162.13.183.212:54098
2014-05-24 11:03:46.8288 TRACE Routing Post request for /mx/v1…
2014-05-24 11:03:46.8288 TRACE Found handler.
2014-05-24 11:04:01.9382 TRACE Accepted TCP client 162.13.183.212:54109
2014-05-24 11:04:02.1569 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:02.1725 TRACE Found handler.
2014-05-24 11:04:07.2350 TRACE Accepted TCP client 162.13.183.212:54113
2014-05-24 11:04:07.5007 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:07.5007 TRACE Found handler.
2014-05-24 11:04:12.5944 TRACE Accepted TCP client 162.13.183.212:54117
2014-05-24 11:04:12.8444 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:12.8600 TRACE Found handler.
2014-05-24 11:04:17.9225 TRACE Accepted TCP client 162.13.183.212:54121
2014-05-24 11:04:18.1725 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:18.1882 TRACE Found handler.
2014-05-24 11:04:23.2350 TRACE Accepted TCP client 162.13.183.212:54124
2014-05-24 11:04:23.4850 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:23.4850 TRACE Found handler.
2014-05-24 11:04:28.5163 TRACE Accepted TCP client 162.13.183.212:54127
2014-05-24 11:04:28.7819 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:28.7819 TRACE Found handler.
2014-05-24 11:04:33.8444 TRACE Accepted TCP client 162.13.183.212:54131
2014-05-24 11:04:34.0944 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:34.0944 TRACE Found handler.
2014-05-24 11:04:39.1569 TRACE Accepted TCP client 162.13.183.212:54139
2014-05-24 11:04:39.3757 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:39.3757 TRACE Found handler.
2014-05-24 11:04:44.4538 TRACE Accepted TCP client 162.13.183.212:54142
2014-05-24 11:04:44.7038 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:44.7038 TRACE Found handler.
2014-05-24 11:04:49.7350 TRACE Accepted TCP client 162.13.183.212:54145
2014-05-24 11:04:50.0007 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:50.0007 TRACE Found handler.
2014-05-24 11:04:55.0788 TRACE Accepted TCP client 162.13.183.212:54148
2014-05-24 11:04:55.3288 TRACE Routing Post request for /mx/v1…
2014-05-24 11:04:55.3288 TRACE Found handler.
2014-05-24 11:05:00.4069 TRACE Accepted TCP client 162.13.183.212:54153
2014-05-24 11:05:00.6413 TRACE Routing Post request for /mx/v1…
2014-05-24 11:05:00.6413 TRACE Found handler.
2014-05-24 11:05:05.6882 TRACE Accepted TCP client 162.13.183.212:54157
2014-05-24 11:05:05.9382 TRACE Routing Post request for /mx/v1…
2014-05-24 11:05:05.9538 TRACE Found handler.
2014-05-24 11:05:11.0163 TRACE Accepted TCP client 162.13.183.212:54160
2014-05-24 11:05:11.2663 TRACE Routing Post request for /mx/v1…
2014-05-24 11:05:11.2663 TRACE Found handler.
2014-05-24 11:05:16.3444 TRACE Accepted TCP client 162.13.183.212:54163
2014-05-24 11:05:16.5944 TRACE Routing Post request for /mx/v1…
2014-05-24 11:05:16.5944 TRACE Found handler.
2014-05-24 11:05:21.6882 TRACE Accepted TCP client 162.13.183.212:54166
2014-05-24 11:05:21.9382 TRACE Routing Post request for /mx/v1…
2014-05-24 11:05:21.9382 TRACE Found handler.
2014-05-24 11:05:26.9851 TRACE Accepted TCP client 162.13.183.212:54173
2014-05-24 11:05:27.2508 TRACE Routing Post request for /mx/v1…
2014-05-24 11:05:27.2508 TRACE Found handler.
@@@

Any idea how to resolve this? Have tried restarts, reinstalls, nothing works…

Thanks for your help,
All the best
Sami

2

Hi Sam,

Is this happening during deployment, and at any particular stage?

Please let me know which versions of Octopus Server and Tentacle you’re running as well.

Thanks,
Nick

3

Hi Nicholas,

It stalls on completion, never moving to success as it should.

I am running latest version everything 2.4.5 I think?

Thanks
Sami

4

Hi Sami,

Thanks for the follow-up. When the deployment stalls, can you please collect:

  1. The OctopusTentacle.txt log file from the affected machine
  2. On the server under Configuration > Diagnostics select “Download System Report”
  3. From the deployment itself, collect the Raw task log (http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task)

Feel free to mail me directly (nblumhardt@) if necessary.

Regards,
Nick

5

Hi Nick,

Thanks for your help on this matter…I believe it is still continuing on the latest version of server and tentacle.

In the logs, the only thing I see is an "error posting to ". It happens on two different servers running windows 2008 r2. Sometimes it works (deploy nuget package step that is) sometimes it gets stuck, with the above message. Could it be because the server is pci compliant?( Ie only SSL v3 is allowed atm…octopus needs v2 perhaps?)

Also in another case I run Start-Sleep -s 60 via a step template at the end of a script, itself a final step in the deployment, before the script’s final two commands and this also only sometimes completes…

Thanks for any help you can provide,
All the best
Sami

6

Thanks for the additional information, Sami. Are you able to collect the three pieces of data from my previous post in this thread? We’ll need to dig in quite deeply to get to the bottom of this I think.

Best regards,
Nick

7

Thanks for you input Nick, will send you those three bits you asked asap - fyi I managed to get around the issue by using polling.

All the best,
Sami