Error in Connectivity After Tentacle Install :: Server 2008 R2

Legacy Uncategorised
1

I am attempting to install tentacle version 3.0.17.2462 on a Server 2008 R2 VM. I am able to get through the setup process just fine, however when I go into the Octopus UI > Add the new Environment > Then attempt to do a Health Check, it is failing.

  • I was able to successfully connect to the tentacle from the Octopus host server using the browser as well as connect to the Octopus host server from the tentacle machine using the browser (as suggested in the troubleshooting steps).

  • We are currently running Octopus server version 3.0.17.2462. I have even tried to install tentacle version 3.0.23.0 as a way to remedy the issue.

  • We are running Powershell version 2.0 on the tentacle VM

  • This is the error I see when I go to the Connectivity tab of the Environment I am trying to set up:
    “Identifying as a client
    2016-02-17 13:29:35 Info
    Sent: IScriptService::StartScript[1] / baebd5a0-7239-48e0-b2e1-2524d4ed30a9
    2016-02-17 13:29:35 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 13:29:36 Info
    Sent: IScriptService::GetStatus[2] / fe26320c-ebc8-4939-8479-b1a8ea893136
    2016-02-17 13:29:36 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 13:29:36 Info
    Sent: IScriptService::CompleteScript[3] / 0b7fe788-6f47-4f6d-8654-36cb5da6c350
    2016-02-17 13:29:36 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 14:29:36 Info
    Opening a new connection
    2016-02-17 14:29:36 Info
    Connection established
    2016-02-17 14:29:36 Info
    Performing SSL (TLS 1.0) handshake
    2016-02-17 14:29:36 Info
    Secure connection established. Server at 192.XXX.XXX.XXX:10933 identified by thumbprint: 6924BC0XXXXXXXXXXXXXXXXXXXXXXXXXX
    2016-02-17 14:29:36 Info
    Identifying as a client
    2016-02-17 14:29:36 Info
    Sent: IScriptService::StartScript[1] / e3bad9cf-12a0-43dd-b983-b14c890f1a36
    2016-02-17 14:29:36 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 14:29:36 Info
    Sent: IScriptService::GetStatus[2] / 8d6755ef-18f2-4d12-a1a0-0b6241b00997
    2016-02-17 14:29:36 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 14:29:37 Info
    Sent: IScriptService::GetStatus[3] / 72fe1341-39dc-4c98-97b5-443e618e3463
    2016-02-17 14:29:37 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 14:29:37 Info
    Sent: IScriptService::GetStatus[4] / eba33f3d-a98d-4b56-83d7-0aeff9241b5f
    2016-02-17 14:29:37 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 14:29:38 Info
    Sent: IScriptService::GetStatus[5] / 559cedad-90cc-42c6-b3c8-1dcbc9541bfc
    2016-02-17 14:29:38 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 14:29:38 Info
    Sent: IScriptService::GetStatus[6] / b83bbc46-c43b-45a0-9f51-211d8ec0a6c9
    2016-02-17 14:29:38 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 14:29:38 Info
    Sent: IScriptService::CompleteScript[7] / 3c77d6ed-7be4-4284-958b-643af6e39a1a
    2016-02-17 14:29:38 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 15:29:35 Info
    Opening a new connection
    2016-02-17 15:29:35 Info
    Connection established
    2016-02-17 15:29:35 Info
    Performing SSL (TLS 1.0) handshake
    2016-02-17 15:29:35 Info
    Secure connection established. Server at 192.XXX.XXX,XXX:10933 identified by thumbprint: 6924BC0XXXXXXXXXXXXXXXXXXXXXXXXXXX
    2016-02-17 15:29:35 Info
    Identifying as a client
    2016-02-17 15:29:36 Info
    Sent: IScriptService::StartScript[1] / dbca670a-b9b3-48e9-af3b-ba07bd9a0c64
    2016-02-17 15:29:36 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 15:29:36 Info
    Sent: IScriptService::GetStatus[2] / 20bcf58c-5f11-47fd-800f-9224abc609a2
    2016-02-17 15:29:36 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 15:29:37 Info
    Sent: IScriptService::GetStatus[3] / 8877e31e-1e58-426b-89ac-db7f9f95906f
    2016-02-17 15:29:37 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 15:29:37 Info
    Sent: IScriptService::GetStatus[4] / e4b30544-86f0-4f78-ac9f-66e8695fe2ac
    2016-02-17 15:29:37 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 15:29:38 Info
    Sent: IScriptService::GetStatus[5] / e5f416b4-5380-4f0d-8418-c4f61ef85733
    2016-02-17 15:29:38 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 15:29:38 Info
    Sent: IScriptService::GetStatus[6] / 1c1e9580-ebe2-4f9b-9d44-506bbcd0e91a
    2016-02-17 15:29:38 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-17 15:29:38 Info
    Sent: IScriptService::CompleteScript[7] / 00a932a8-290c-403b-80ed-3163a72ba13e
    2016-02-17 15:29:38 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:14 Info
    Opening a new connection
    2016-02-22 09:08:14 Info
    Connection established
    2016-02-22 09:08:14 Info
    Performing SSL (TLS 1.0) handshake
    2016-02-22 09:08:15 Info
    Secure connection established. Server at 192.XXX.XXX.XXX:10933 identified by thumbprint: 6924BC0XXXXXXXXXXXXXXXXXXXXXXXXXX
    2016-02-22 09:08:15 Info
    Identifying as a client
    2016-02-22 09:08:15 Info
    Sent: IScriptService::StartScript[1] / 23f4416f-26c2-4d19-a24a-f7c526cc72f5
    2016-02-22 09:08:15 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:16 Info
    Sent: IScriptService::GetStatus[2] / 4348094c-aec4-4c9b-8ec6-ed807210b0ae
    2016-02-22 09:08:16 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:16 Info
    Sent: IScriptService::CompleteScript[3] / 6138146e-d3e3-4c9b-94cb-8ee56f7601ff
    2016-02-22 09:08:16 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:16 Info
    Sent: IScriptService::StartScript[4] / 097cec34-9819-4c99-93b6-4839b3371ded
    2016-02-22 09:08:16 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:17 Info
    Sent: IScriptService::GetStatus[5] / 6593cfe7-7ae2-494b-b94e-dd8761c8a2e9
    2016-02-22 09:08:17 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:17 Info
    Sent: IScriptService::GetStatus[6] / 43e18080-02f6-4ad5-8be4-d2e36f965813
    2016-02-22 09:08:17 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:18 Info
    Sent: IScriptService::GetStatus[7] / 34eb07f3-c8b5-4311-a130-f92ed2532e8e
    2016-02-22 09:08:18 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:18 Info
    Sent: IScriptService::GetStatus[8] / e46fb723-d16a-47a5-9430-269b8f98d482
    2016-02-22 09:08:18 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:19 Info
    Sent: IScriptService::GetStatus[9] / 4ba747b2-52d2-4967-8ce1-1ba2c6425a63
    2016-02-22 09:08:19 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:19 Info
    Sent: IScriptService::GetStatus[10] / 888be06e-d8da-46fd-b21a-a2ab6b1f3b04
    2016-02-22 09:08:19 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:20 Info
    Sent: IScriptService::GetStatus[11] / 87ec2cf7-f799-4b48-b20b-2811157374fc
    2016-02-22 09:08:20 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:20 Info
    Sent: IScriptService::GetStatus[12] / cbedff70-e93f-47ee-bfa0-1e8c41b8462c
    2016-02-22 09:08:20 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:20 Info
    Sent: IScriptService::CompleteScript[13] / a8714ac8-eccd-49f8-9190-205361550ae5
    2016-02-22 09:08:20 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:20 Info
    Sent: IScriptService::StartScript[14] / ae8657bc-b27f-45f8-b03b-f278105a2277
    2016-02-22 09:08:20 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:21 Info
    Sent: IScriptService::GetStatus[15] / ff730136-65d3-44d6-b4aa-72dbd9d50867
    2016-02-22 09:08:21 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:21 Info
    Sent: IScriptService::GetStatus[16] / 1b8ff9cf-dcf6-460a-9740-f996e528e294
    2016-02-22 09:08:21 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:22 Info
    Sent: IScriptService::GetStatus[17] / 2e561c08-181c-4fa6-8eee-5f33bed72ecf
    2016-02-22 09:08:22 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:22 Info
    Sent: IScriptService::GetStatus[18] / 9253d303-6deb-46ec-9916-a687ce7b03a7
    2016-02-22 09:08:22 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:23 Info
    Sent: IScriptService::GetStatus[19] / 5ff150a1-7757-4120-9afa-9230b05fe08d
    2016-02-22 09:08:23 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:23 Info
    Sent: IScriptService::GetStatus[20] / c6375ba4-fd8d-43b5-89d2-e884b22a348a
    2016-02-22 09:08:23 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:24 Info
    Sent: IScriptService::GetStatus[21] / 6330b9d4-964f-43f7-b506-18a257dba8ed
    2016-02-22 09:08:24 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:24 Info
    Sent: IScriptService::GetStatus[22] / 7d95ec58-8b16-4ff2-ad87-08ea96dca692
    2016-02-22 09:08:24 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:25 Info
    Sent: IScriptService::GetStatus[23] / 4e2d8356-67ed-4299-acbf-3c7c671c37c5
    2016-02-22 09:08:25 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:25 Info
    Sent: IScriptService::GetStatus[24] / 71b084a8-7b65-49c4-88f6-bae288a765c9
    2016-02-22 09:08:25 Info
    Received: Halibut.Transport.Protocol.ResponseMessage
    2016-02-22 09:08:25 Info
    Sent: IScriptService::CompleteScript[25] / ceb446c1-ef04-4de3-97ed-38fb4daabab3
    2016-02-22 09:08:25 Info
    Received: Halibut.Transport.Protocol.ResponseMessage”

  • This is the error I see when I go to Tasks > Click on the manual Health Check task I initiated for the VM in question
    "Running health check on VMName
    09:08:14Info
    Sending health check request to VMName at https://192.XXX.XXX.XXX:10933/…
    09:08:16Info
    This server does not have version 3.0.17.448 of the Calamari package. It will be pushed automatically.
    09:08:17Info
    C:\Program Files\Octopus Deploy\Calamari\3.0.17.448\Success.txt
    09:08:21Error
    Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
    09:08:21Error
    at Calamari.Integration.Proxies.ProxyInitializer.InitializeDefaultProxy() in y:\work\b1fd300731d5f2fc\source\Calamari\Integration\Proxies\ProxyInitializer.cs:line 13
    09:08:21Error
    at Calamari.Program.Main(String[] args) in y:\work\b1fd300731d5f2fc\source\Calamari\Program.cs:line 13
    09:08:25Fatal
    The remote script failed with exit code 255"

  • The errors in the health check point toward the tentacle having an out of date .msi installed that is not compatible with my Octopus Server version. However, I am using the .msi provided by Octopus with the file name: Octopus.Tentacle.3.0.17.2462-x64.msi. I also tried using this .msi : Octopus.Tentacle.3.0.23.0-x64.msi

  • Note: X’s have been put in place of IP Addresses and Thumbprints and ‘VMName’ has been entered instead of the actual VM name.

  • Any help would be appreciated! Thanks!

2

Hi Jenna,
I’m sorry to hear that you are having troubles getting the Tentacle set up and deploying.
Based on the logs you have sent through it sounds to me like the Tentacle itself might actually be installed correctly. The line that it appears to be failing on is when, during the health check, it tries to execute a command to Calamari. Calamari is the slim console application that the server sends to the Tentacle and which contains the logic for extracting, transforming and deploying applications. By bundling this logic into Calamari and sending it across to the Tentacle when needed we have been able to reduce the need to upgrade the Tentacle whenever new features are available. Given that connections appear to take place and Calamari is getting copied over it looks like the Tentacle install itself is fine.

It sounds like in this case that there seems to be some sort of problem when Calamari starts up and is attempting to configure the web proxy used for any outbound connections.
Could I please get you to send through any of the logs generated by the Tentacle itself. These can be found on the server where the Tentacle is installed, typically in the C:\Octopus\Logs directory. This might give us a little more information about why its failing.
In addition could I get you to check if you have any web proxy settings configured on the machine that the Tentacle is on. This can be found by opening Internet Explorer, going to Tools -> Internet Options. Click the Connections tab then the LAN settings button. If a proxy server is enabled then the address and port will be set and the checkbox in the Proxy Server form area will be checked. Could you please send through a screenshot of this configuration. If it is enabled then just as an experiment could you try disable the proxy and running the health check again.

Thanks for getting this extra information available. I look forward to your reply.
Cheers
Robert

3

Thanks for your quick response, Rob!

After I read your email, I uninstalled the tentacle version 3.0.23.0-x64
and installed the version that we would like on the server in question,
3.0.17.2462-x64. It seems the only logs that were generated in the Logs
directory you requested are those generated when I installed the version
3.0.17.2462-x64 tentacle back on the machine (the time matches and I wasn’t
able to trigger more logs simply by doing another health check).

Below is a screenshot of both the LAN settings you requested and the Log
files referenced above.

Let me know if I can supply more info to help remedy the issue.

Thanks again!

[image: Inline image 1]

image.png
image.png1155×721 38 KB

4

Hello again!

One of my devs remembered a custom proxy setting we had in the
machine.config on the tentacle machine that was ‘breaking Octopus’. We
commented that out and have connectivity now! This is the setting in case
you have another lost soul with this issue in the future:

Again, thank you for all you do!

  • Jenna

image.png
image.png1155×721 38 KB

5

Hi Jenna,
I’m glad to hear that these steps helped you discover the root cause of your problems. Thanks for letting me know the specific details. I’ll see what we can do to make sure this sort of error is more obvious for users in the future.
Thanks again for helping to improve this product!
Cheers,
Robert