naxprima.blogg.se - Critical ops check connection

There's often specific information about the communication status of the machine here.

On the Infrastructure page of the Octopus Web Portal, click on the problem machine and select the Connectivity tab.

There's a link to this on the page containing the details of the Health Check or Deployment, which can usually be located using the Tasks page in the Octopus Web Portal.

If the machine has been included in a Health Check or Deployment, examine the Raw Task Log.

If you are having problems with a previously-working machine, or you've successfully "Discovered" or "Registered" a machine but can't get communication to work afterwards, you can find information in three places:

As you troubleshoot problems with your Tentacles, please pay attention to which communication mode they are configured for. Communication modeīefore continuing, it's worth briefly revisiting the concept of Listening Tentacles and Polling Tentacles. Working from a clean slate can sometimes expose the underlying problem. Learn about manually uninstalling Tentacle. This can be done without any impact to the applications you have deployed. If you get to the end of this guide without success, it can be worthwhile to completely remove the Tentacle configuration, data, and working folders, and then reconfigure it from scratch. Open the Tentacle Manager app, and select Restart.Īlternatively, open the Services app, find OctopusDeploy Tentacle, and click restart. Open the Octopus Manager app, and select Restart.Īlternatively, open the Services app, find OctopusDeploy, and click restart.

Neither action should fix a communication problem, but sometimes they can help flush a problem out. Restart the Octopus and Tentacle servicesīefore following the steps below, it can be worthwhile to restart the Octopus and Tentacle services, and refresh the browser you're using to connect to the Octopus Web Portal. This guide will help to track down these issues when either a machine cannot be "Discovered" (Listening Tentacles) or "Registered" (Polling Tentacles) with the Octopus Server, or a previously working machine fails a health-check with errors from the networking stack. All of the 'classic' problems of TCP networking: firewalls, proxies, timeouts, DNS issues, and so-on can affect Octopus Tentacles.