Initial tentacle install is failing with error '100 Generating Cert for the machine' about octopus-deploy-cookbook HOT 7 CLOSED

@bdevenney

You will need admin access in order to run these commands. Under the hood the tentacle will run the following in powershell to generate the cert:

.\\Tentacle.exe new-certificate -e "C:\Octopus\tentacle_cert.txt" --console

I would try running this from the same account and see what happens. I know the main issue is that non admin users / winrm users do not have certain dll's available to them. These dlls include the certificate libraries needed to add certs into windows. I do know we run 2012 and have used the cookbook to install tentacles but I would like to understand the full problem. How are you running this command ? Is it running as your user or as the system user in a scheduled task?

Hope this helps!

As for the the feature request for an offline installer approach I think that could be useful for others and have created #101 to track it. If you want to incorporate your code into the main repo I could help get it so you don't have to maintain your own fork, we love pull requests.

from octopus-deploy-cookbook.

Thanks @brentm5

When I get a bit of time, I'll look into the user permissions a bit more. We use PowerCLI to provision the server and use a specific user to call the first chef-client run remotely. Subsequent runs will use the local/system account so it will be interesting to see if the run is successful when the chef-client service runs normally.

For the forking, I pretty much just hacked the installer_url value to point to a local repository but, again, if I get the time to code this properly I'll send through a pull request.

Thanks for the pointers, much appreciated,
Barry.

from octopus-deploy-cookbook.

@bdevenney

Yup the remote user is going to be your problem. The issue is that remote sessions are treated differently and I do not know of a way to get around that. One hack is to setup a scheduled task via winrm and then kick that off via schtasks /run /TN <name> or something. We found a bunch of things that are just easier to run locally. This is essentially where this gem (which is used in test-kitchen I believe) originated from: https://github.com/WinRb/winrm-elevated

from octopus-deploy-cookbook.

I was running into a similar issue, but returning Error 1:

Running the command manually spits out the following message from Tentacle.exe:

.\Tentacle.exe new-certificate -e "C:\Octopus\tentacle_cert.txt" --console
The default instance of Tentacle has not been created. Either pass --instance INSTANCENAME when invoking this command, or run the setup wizard.
-------------------------------------------------------------------------------
Full error details are available in the log files at C:\Users\user\AppData\Local\Octopus\Logs
If you need help, please send these log files to https://octopus.com/support
-------------------------------------------------------------------------------

Not sure if the behavior of this command changed in a recent Tentacle.exe version, but this used to work for me. Using Tentacle 3.14.1 with this error.

from octopus-deploy-cookbook.

I updated to tentacle version 3.15.2 and it installed/configured without error.

from octopus-deploy-cookbook.

@jcuzzi I believe there was a bug before that was resolved. Anything before 3.2.X or something would require an instance.

I actually reported it here: OctopusDeploy/Issues#2143

from octopus-deploy-cookbook.

Closing because these seem related to known issues.

from octopus-deploy-cookbook.