We are preparing to upgrade to version 2.5.8 and have begun efforts to deploy multiple tentacle instances on different ports on our deployment servers. When I run the installation to deploy a new tentacle instance from the 2.4.8.107 msi it alerts me that I have an existing 2.0 installation that must be uninstalled first. The existing tentacle instance started as a 2.0 tentacle and has been upgraded incrementally as new versions have been released. Our objective was to deploy multiple tentacles ahead of the update to ensure we have unique SQUID’s within our deployments.
Thanks for getting in touch! I’m slightly confused so please bare with my questions.
Are you trying to install multiple instances of Tentacle on one server? If so this is how you do it:
We have a specific method to install the instances for you.
Also please let me know if you are trying to install multiple instances of a polling tentacle as there is a current bug in the installer, and I have some command line calls to make it work if you need.
If I am on the totally wrong path here, please explain a little more about the server you are trying to install on.
Vanessa
Our issue is I believe with the Tools.exe. When I follow the instructions to deploy an additional tentacle the Tools on this specific server launch as the 2.0.13 version instead of the more recent version which would match the Tentacle. On another machine where we haven’t gone through the upgrade cycle and deployed a Tentacle by installing from the 2.4.8.107 MSI I am able to add and manage multiple instances as per the documentation. Is there a way to upgrade the Tools without an uninstall and re-install of the existing Tentacle?
I have confirmed that it is an issue with Tools.exe exclusively. A simple copy of the Tentacle folder from another machine which hasn’t had any version of Octopus less than 2.4.8.107 to the Tentacle server which still has the tools for version 2.0.n resulted in the ability to load Tools.exe -tentacle and administer the tentacle instance including adding new tentacle instances.
Sorry you had the troubles, but I am glad you were able to sort it out. When you have a Tentacle that has been around for a while, and only upgrade via the Octopus Server, we do not actually run the MSI but update via a NuGet Package. The tools aren’t updated during this process. Running the MSI on the Tentacle will update the tools. A re-install will not delete any files or configurations, just update the software so it is a safe process to run.
We haven’t sorted it out entirely. The workaround was to “copy and paste” the tentacle directory from another machine which was installed clean. We still can not run the MSI installer as it still recognizes the 2.0.n version. I presume this is a registry check and it is finding a key that I have not been able to identify.
Although the work around validated that tools.exe is still at the older version we can’t move forward with an upgrade to 2.5.8.447 or anything newer until we can determine how to update tools without disrupting our existing production tentacle. Adding a new deployment server is a costly option but none the less still an option.
Can the tools be upgraded such that tentacle manager is once again useful? Or do I have to perform a manual uninstall of the default instance in order to deploy additional instances? If manual unistall (the install doesn’t exist in add or remove programs any longer).
Thanks again for the support.
Sent via the Samsung Galaxy S® 5 ACTIVE™, an AT&T 4G LTE smartphone