Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tentacle `poll-server` command fails to successfully register with second and subsequent nodes #5545

matt-richardson opened this issue May 7, 2019 · 4 comments


Copy link

commented May 7, 2019


  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • I have linked the original source of this report
  • I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

When using the poll-server command, the Tentacle successfully configures itself to talk to the target node, but the target node does not refresh its list of known thumbprints, so refuses to communicate with it.

This previously happened during a call to /api/machines/all?thumbprint=123, but this call was removed during the work to make Tentacle spaces aware - this "side effect" behavior wasn't apparent from the Tentacle side so it went unnoticed.

What I expected to happen

After executing the command, I expect the new node to immediately trust the new thumbprint and start communicating.

Steps to reproduce

  1. Setup a HA cluster
  2. Setup a new tentacle
  3. Register as a worker / deployment target with NodeA
  4. Run the poll-server command against NodeB
  5. Check server logs -> see errors where unknown thumbprint is presented

Log exerpt

to be supplied

Affected versions

Octopus Tentacle: 4.x till fixed



  • Restart NodeB
  • call from a webbrowser.


source: #5206 (comment)
source: internally found


This comment has been minimized.

Copy link

commented May 7, 2019

If I remember correctly, restarting the nodes didn't seem to have any effect on this.

The other work around, at least in my case, was to use the 3.24.x version of the tentacle installer, and then letting Octopus Server update the tentacle during the first deployment to the machine.

I'm happy nonetheless that you identified this as an issue, hopefully this is something resolved at some point in the near future. We'll just keep using the older tentacle installer in the mean time.


This comment has been minimized.

Copy link

commented May 15, 2019

@DerekCampbellOctopus @matt-richardson We started running into this issue after the polling-server cmd was fixed for worker nodes in v4.0.1 of the tentacle (#5206). But I just now ran into this issue again after installing the latest version of the tentacle as a deployment tentacle (not a worker).

If the tentacle communicated with the secondary node it failed. But if it communicated with the primary node it worked. You can test this by draining nodes and running healthchecks on the tentacle. I ran the wrokaround mentioned above and that seemed to have solve the communication problem. Not really sure why or how though....

@octoreleasebot octoreleasebot added this to the 2019.5.4 milestone May 16, 2019

This comment has been minimized.

Copy link

commented May 16, 2019

Release Note: Fixed an issue where the Tentacle poll-server command was unable to successfully configure polling on second and subsequent HA nodes


This comment has been minimized.

Copy link

commented Aug 14, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
4 participants
You can’t perform that action at this time.