I was excited to finally look at this feature that has been around for awhile now. I wanted to use it for some of the logs that we have in our build process. However when I was prototyping the feature it did not work as intended. I have attached the build log below. I had to cancel the task because it was stuck in the requesting upload for several minutes. Can you provide some feedback for this? Is there anything that needs to be setup to make this work? Any information would be helpful Thanks!
Thanks for getting in touch!
What we are seeing here is that the tentacle crashed.
If you could please provide the tentacle log to help us trace why.
If you look into C:\Octopus\Logs (or the folder where tentacle was installed on the server) and grab the correct Octopus.Tenacle.txt with the correct date and supply that why might be able to see why this crash occurred.
When I look at the correct log file all I see is the Powershell output and no more information about the tentacle. In addition, I checked the event viewer and got no error from the OD tentacle. To give some more information we are running PS 3.0 on this machine with Windows Server 2008 R2.
G’day Brent! Still trying to find an angle to approach this from (tricky without much output as you observed) - a couple of preliminary thoughts:
Which Octopus/Tentacle versions are you working with?
Is the file still in the same location, with the same name, after the PowerShell script completes? (We don’t copy it anywhere, so it needs to stay put.)
Can you please post the PS line with the New-OctopusArtifact call in it?
I have tested this in our beta region running 2.5.4.280 and it does work correctly. The version I was testing before was 2.4.10.235 for both the server and tentacle.
Thanks Brent - it’s possible there’s a but in the earlier version that we haven’t previously encountered; glad to hear the new version has it covered. Let me know if you have any more trouble with it.
Thanks for the extra info Brent - I’ve spotted a bug causing this issue to surface; it will have been triggered by the server/tentacle experiencing load at an earlier point in time - restarting both of them should reset the disc buffer that is erroneously rejecting messages.
That was a typo. Sorry about the confusion. It is also worth noting that there were left over tasks in the diagnostic window that do not go away when an upload fails. These tasks appear to never go away either.
We had the same issue today – trying to get a small 1KB file failed multiple times with the same error. After restarting the Tentacle, it attached fine.
A request for the next file chunk could not be delivered.
The receiver is offline or experiencing high load and cannot accept the message.
Tentacle version 2.5.5.318
It began hanging after I updated tentacle from 2.5.4.280 to 2.5.5.318 (both on 2.5.5.318 server).
Posting for just get notified when it’ll be fixed
