Troubleshooting Tentacle communication issues

Legacy Uncategorised
1

I was getting this error during a check health:
2011-11-11 18:57:01 ERROR System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. —> System.ServiceModel.FaultException: An error occurred when verifying security for the message.

It turns out that the clock on that machine was off by over 5 hours. After I sync’d the clock the tentacle came online.

This may be a good thing to mention in the tentacle installation instructions.

2

Hi Pete,

Thanks for letting me know, I’ll include it in the documentation.

Just out of interest, how on earth did you figure that out? :slight_smile:

Paul

3


It was just chance that I noticed the
clock was off. Then I remembered another system where the security depends
on the clocks being relatively close. I wish I could explain it better,
look for MaxClockSkew in MSDN, it might
point you in the right direction.



Pete Craig





From: "Paul Stovell" <tender2+d5a4a6b22d2e878c1e8aab8599398cf0e9e66aaa0@tenderapp.com>
To: <peter.craig@jci.com>
Date: 11/11/2011 02:29 PM
Subject: Re: Troubleshooting Tentacle communication issues [Ideas and suggestions]





// Add your reply above here
==================================================
From: Paul Stovell
Subject: Troubleshooting Tentacle communication issues

Hi Pete,

Thanks for letting me know, I'll include it in the documentation.

Just out of interest, how on earth did you figure that out? :)

Paul

View this Discussion online: http://help.octopusdeploy.com/discussions/suggestions/40-troubleshooting-tentacle-communication-issues
--

To unsubscribe and stop receiving emails from http://help.octopusdeploy.com, visit
http://help.octopusdeploy.com/unsubscribe/95d98014a5ecc156aa4d99cd51b129dbd8012855