Hey guys,
We are having an issue where a deployment will occasionally hang on one machine in the environment (not specific to the machine) during the package download. In looking through the logs, I cannot determine when a specific tentacle completed the package download. Is this possible?
Would it be possible to enhance the deployment log such that a verbose entry is added when the tentacle completes the download? That is first place I looked, and would probably be the ideal location for it.
Hi Derrick,
Thx for reaching us! Could you please send us the raw log of the deployment for us the help you see what is going on? Here is a link that shows you how to do it: http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task
Also, are your tentacles configured in “Listening” or “Polling” mode?
Hope to hear from you soon,
Dalmiro
Here is the redacted section from the log detailing the package download.
I can tell that all packages finished download at 07:55:34, but I cannot tell what happened between 07:36:36 and 07:55:34.
I would like to know when each individual server finished the download. These deployments usually take less than 2 minutes, so that 20 minute delay is extreme.
| Success: Acquire packages
07:36:02 Info | Downloading packages
07:36:02 Info | Making a list of packages to download
07:36:02 Verbose | The following packages will be downloaded by the Octopus Server:
07:36:02 Verbose | The following packages will be downloaded directly by Tentacles:
07:36:02 Verbose | - MyPackage 2014.11.12.8 (feed: MyFeed)
07:55:34 Info | All packages have been downloaded
|
| Success: Download package MyPackage 2014.11.12.8 from NuGet feed MyFeed on applicable machines
07:36:02 Verbose | Starting Acquire package MyPackage.2014.11.12.8
07:55:34 Verbose | Verifying that the same package was downloaded on all machines
07:55:34 Verbose | The package hash on all machines matched
|
| Success: Download MyPackage on https://WebServer-01:10933/
07:36:02 Verbose | Starting Download MyPackage on https://WebServer-01:10933/
07:36:09 Verbose | Checking package cache for package MyPackage 2014.11.12.8
07:36:09 Info | Downloading NuGet package MyPackage 2014.11.12.8 from feed: 'https://MyNugetServer.MyDomain.com/nuget'
07:36:09 Verbose | Downloaded packages will be stored in: D:\Octopus\Applications\.Tentacle\Packages\feeds-MyFeed
07:36:09 Verbose | Finding package (attempt 1 of 5)
07:36:10 Verbose | Found package MyPackage version 2014.11.12.8
07:36:31 Verbose | Downloading to: D:\Octopus\Applications\.Tentacle\Packages\feeds-MyFeed\MyPackage.2014.11.12.8_26235190020D0A439F13A88E4C80436B.nupkg
07:36:31 Verbose | A direct download is possible; bypassing the NuGet machine cache
07:36:36 Verbose | SHA1 hash of package is: d34c91ceb97813f27a9fa70a19b91a3d20134606
|
| Success: Download MyPackage on https://WebServer-02:10933/
07:36:02 Verbose | Starting Download MyPackage on https://WebServer-02:10933/
07:36:03 Verbose | Checking package cache for package MyPackage 2014.11.12.8
07:36:03 Info | Downloading NuGet package MyPackage 2014.11.12.8 from feed: 'https://MyNugetServer.MyDomain.com/nuget'
07:36:03 Verbose | Downloaded packages will be stored in: D:\Octopus\Applications\.Tentacle\Packages\feeds-MyFeed
07:36:03 Verbose | Finding package (attempt 1 of 5)
07:36:10 Verbose | Found package MyPackage version 2014.11.12.8
07:36:10 Verbose | Downloading to: D:\Octopus\Applications\.Tentacle\Packages\feeds-MyFeed\MyPackage.2014.11.12.8_E712FBF23C057A45A7BA05734812B3CA.nupkg
07:36:10 Verbose | A direct download is possible; bypassing the NuGet machine cache
07:36:16 Verbose | SHA1 hash of package is: d34c91ceb97813f27a9fa70a19b91a3d20134606
|
| Success: Download MyPackage on https://WebServer-03:10933/
07:36:02 Verbose | Starting Download MyPackage on https://WebServer-03:10933/
07:36:03 Verbose | Checking package cache for package MyPackage 2014.11.12.8
07:36:03 Info | Downloading NuGet package MyPackage 2014.11.12.8 from feed: 'https://MyNugetServer.MyDomain.com/nuget'
07:36:03 Verbose | Downloaded packages will be stored in: D:\Octopus\Applications\.Tentacle\Packages\feeds-MyFeed
07:36:03 Verbose | Finding package (attempt 1 of 5)
07:36:11 Verbose | Found package MyPackage version 2014.11.12.8
07:36:11 Verbose | Downloading to: D:\Octopus\Applications\.Tentacle\Packages\feeds-MyFeed\MyPackage.2014.11.12.8_7D8DF7CFDBCA9B4C8DDEF760664C1A30.nupkg
07:36:11 Verbose | A direct download is possible; bypassing the NuGet machine cache
07:36:16 Verbose | SHA1 hash of package is: d34c91ceb97813f27a9fa70a19b91a3d20134606
|
| Success: Download MyPackage on https://WebServer-04:10933/
07:36:02 Verbose | Starting Download MyPackage on https://WebServer-04:10933/
07:36:03 Verbose | Checking package cache for package MyPackage 2014.11.12.8
07:36:03 Info | Downloading NuGet package MyPackage 2014.11.12.8 from feed: 'https://MyNugetServer.MyDomain.com/nuget'
07:36:03 Verbose | Downloaded packages will be stored in: D:\Octopus\Applications\.Tentacle\Packages\feeds-MyFeed
07:36:03 Verbose | Finding package (attempt 1 of 5)
07:36:10 Verbose | Found package MyPackage version 2014.11.12.8
07:36:10 Verbose | Downloading to: D:\Octopus\Applications\.Tentacle\Packages\feeds-MyFeed\MyPackage.2014.11.12.8_93EC0B5A9FA695469C1374580060AD42.nupkg
07:36:10 Verbose | A direct download is possible; bypassing the NuGet machine cache
07:36:16 Verbose | SHA1 hash of package is: d34c91ceb97813f27a9fa70a19b91a3d20134606
Hi Derrick,
Thanks for getting in touch! Sorry about the delay in a response.
We don’t really have any settings that can be turned on here to find out what is going wrong.
I am also going to have to assume that you have copied all the relevant parts of the log - based on that assumption, there does appear to be a 20 min gap there.
What might point me in the right direction here would be a copy of the Tentacle logs c:\Octopus\logs\OctopusTentacle.txt etc
If we can find why it might be hanging on receiving the package this might determine the gap.
Thanks!
Vanessa