Dgraph Please Retry Again Server Is Not Ready to Accept Requests
Troubleshooting Tentacles
Last updated
All of the 'classic' bug of TCP networking: firewalls, proxies, timeouts, DNS bug, and then-on can affect Octopus Tentacles. This guide will assistance to rails downward these problems when either a machine cannot be "Discovered" (Listening Tentacles) or "Registered" (Polling Tentacles) with the Octopus Server, or a previously working car fails a health-check with errors from the networking stack.
Restart the Octopus and Tentacle services
Earlier 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. Neither actionshould fix a communication problem, but sometimes they can help flush a problem out.
Restart the Octopus service
Open the Octopus Manager app, and select Restart.
Alternatively, open the Services app, find OctopusDeploy, and click restart.
Restart the Tentacle service
Open the Tentacle Director app, and select Restart.
Alternatively, open up the Services app, find OctopusDeploy Tentacle, and click restart.
Uninstall Tentacles
If you become 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. This can be washed without any impact to the applications you have deployed. Larn virtually manually uninstalling Tentacle. Working from a clean slate can sometimes betrayal the underlying problem.
Communication mode
Before continuing, it'south worth briefly revisiting the concept of Listening Tentacles and Polling Tentacles. As yous troubleshoot issues with your Tentacles, delight pay attention to which advice mode they are configured for.
Review Tentacle communication modes.
Identify the trouble
If you are having problems with a previously-working machine, or you've successfully "Discovered" or "Registered" a car merely can't become advice to piece of work subsequently, you tin can observe data in three places:
- If the machine has been included in a Health Check or Deployment, examine the Raw Task Log. At that place's a link to this on the page containing the details of the Health Check or Deployment, which can ordinarily be located using theTasks page in the Octopus Web Portal.
- On theInfrastructure page of the Octopus Web Portal, click on the trouble machine and select theConnectivity tab. There'due south ofttimes specific information about the advice status of the machine here.
- In the Octopus Web Portal, open Configuration ➜ Diagnostics . Information on this page can exist helpful to work out what's going on in the Octopus installation. Look at the information underServer logs and searching for the machine'due south proper name or IP address can plough up useful information.
Check the Octopus and Tentacle services are running
If you're successfully connecting to the Octopus Web Portal with your web browser, you can be confident the Octopus Server service is running.
The Tentacle Manager usually shows correct service status, but information technology pays to double-check. On the Tentacle motorcar, open the Windows Services Control Panel applet (services.msc) and look for "OctopusDeploy Tentacle". Verify that the service is in the "Running" state.
If the services is not running...
If the Tentacle service is not running, yous tin can try to showtime information technology from the Services applet. Allow 30 seconds for the service to start work, then refresh the Services screen. If the Tentacle service keeps running, become dorsum to the Octopus Web Portal and try Health Checking the afflicted car again. If the service stops, it is likely that the service is crashing during startup; this can be caused by a number of things, nearly of which tin can exist diagnosed from the Tentacle log files. Audit these yourself, and either send the log files or extracts from them showing the issue to the Octopus Deploy Support email address for assistance.
If the service is running, go along to the next stride.
Advice settings
To verify the communication settings, On the Tentacle machine, open the Tentacle Manager application from the Commencement screen or Start menu.
At that place are iii pieces of data to verify and they are slightly different, depending on whether you configured you Tentacle to communicate in Listening mode or Polling mode:
Listening Tentacle
- Ensure that the Tentacle is inlistening mode. Below the thumbprint, you should run across the text This Tentacles listens for connections on port 10933.
- Check the port that the Tentacle listens on.
- Check that theOctopus Server thumbprint shown in light gray in the Tentacle manager matches the one shown in the Configuration ➜ Thumbprints screen in the Octopus Spider web Portal.
Note, that in that location are two thumbprints displayed - that of the Tentacle itself (shown first in bold) and the thumbprints of trusted servers (shown inline in the greyness text).
If any of the communications settings are incorrect, choose Delete this Tentacle instance.... After doing so, you lot'll be presented with the Tentacle installation wizard, where the correct settings tin be chosen. If the settings are correct, keep to adjacent pace.
Polling Tentacles
- Ensure that the Tentacle is inpolling mode. Below the thumbprint, you should run into the text This Tentacle polls the Octopus Server....
- Bank check the port that the Tentacle polls the Octopus Server on.
- Cheque that theOctopus Server thumbprint shown in calorie-free gray in the Tentacle manager matches the one shown in the Configuration ➜ Thumbprints screen in the Octopus Web Portal.
Note, that there are ii thumbprints displayed - that of the Tentacle itself (shown first in bold) and the thumbprints of trusted servers (shown inline in the gray text).
If whatsoever of the communications settings are incorrect, choose Delete this Tentacle case.... After doing then, you'll be presented with the Tentacle installation magician, where the correct settings can be called. If the settings are correct, go on to next footstep.
Check the Tentacle thumbprint
Verify that the Tentacle'due south thumbprint, shown in bold in the big box, matches any that have been presented in error messages, and in the Automobile Settings page on the Octopus Web Portal.
Check the connections
To assistance with diagnostics, we've include a welcome page y'all can connect to from your spider web browser. The process of connecting is slightly different depending on if y'all are using a listening Tentacle or a polling Tentacle.
When you carry these checks:
- If you lot're presented with a prompt to "confirm a certificate" or "select a certificate" choose "Cancel" - don't provide 1.
- If yous're presented with a warning about the invalidity of the site's document, "continue to the site" or "add together an exception" (Octopus Server uses a cocky-signed document by default).
Checking a Listening Tentacle
On the Tentacle motorcar, open a web browser and navigate to https://localhost:10933 (or your chosen Tentacle communications port if it isn't the default). Make sure you lot use an HTTPS URL is used.
The page shown should expect similar the one below.
If you can't browse to the page...
If this is where your journey ends, there'due south a problem on the Tentacle automobile. It is very probable that the Tentacle is unable to open the communications port, either considering of permissions, or considering some other process is listening on that port. Using the Windows netstat -o -n -a -b command can aid to get to the lesser of this quickly. If you're still in trouble, check the Tentacle log files and contact Octopus Deploy back up.
Next, repeat the procedure of connecting to the Tentacle with a web browser, but do thisfrom the Octopus Server auto.
When forming the URL to bank check:
- Get-go try using the Tentacle'south DNS hostname, e.g. https://my-tentacle:10933.
- If this fails, effort using the Tentacle's IP accost instead, e.g. https://ane.2.three.4:10933 - success using the IP accost just not the DNS hostname will point a DNS upshot.
If you lot can't connect... Declining to connect at this step means that you accept a network consequence preventing traffic between the Octopus Server and Tentacles. Bank check that the Tentacle port is open in any firewalls, and that other services on the network are working. There's non usually much that Octopus Deploy Back up tin can propose for these bug as networks are complex and highly varied. Having the network administrator from your system help diagnose the event is the best first step. If that draws a blank, please arrive bear on.
Recall to cheque both the built-in Windows Firewall, and any other firewalls (in Amazon EC2, bank check your security grouping settings for instance).
Checking a Polling Tentacle
On the Octopus Server machine, open a web browser and navigate to https://localhost:10943 (or your chosen Tentacle communications port if information technology isn't the default). Make certain an HTTPS URL is used.
The page shown should look like the one beneath.
If you've made it this far, skilful news! Your Octopus Server is running and ready to accept entering connections from Polling Tentacles.
If you tin can't browse to the page...
If this is where your journey ends, there's a problem on the Octopus Server machine itself. It is very likely that the Octopus Server is unable to open the communications port, either because of permissions, or because another process is listening on that port. Using the Windows netstat -o -north -a -b control can help to get to the lesser of this quickly. If you can see connections being opened and immediately airtight (CLOSE_WAIT state in netstat output) from the same Foreign Address, it might indicate that this server is blocking traffic from the communications port and therefore resetting the connectedness immediately. Bank check both the built-in Windows Firewall, and whatsoever other firewalls (in Amazon EC2, check your security group settings for example) on the server identified past the Foreign Address in netstat and make certain that the communications port isn't being blocked. You can too employ Wireshark to inspect traffic that is coming in on the Octopus Server communications port to notice whatever connections that are being immediately reset by starting a network capture and filtering the traffic by tcp.port == 10943 (or your chosen Tentacle communications port if it isn't the default), this should identify any incoming requests that gets reset immediately.
If you're nonetheless in problem, check the Octopus Server log files and contact Octopus Deploy support.
Next, repeat the procedure of connecting to the Octopus Server with a spider web browser, but practise thisfrom the Tentacle machine.
When forming the URL to check:
- First try using the Octopus Server's DNS hostname, e.m. https://my-octopus:10943.
- If this fails, try using the Octopus Server's IP address instead, e.k. https://1.2.three.four:10943 - success using the IP accost but not the DNS hostname volition indicate a DNS effect.
If y'all tin't connect... Failing to connect at this step ways that you lot have a network issue preventing traffic between the Tentacles and Octopus Server. Check that the Octopus Server polling port is open in any firewalls, and that other services on the network are working. There's not usually much that Octopus Deploy Back up can suggest for these bug equally networks are complex and highly varied. Having the network administrator from your organization aid diagnose the issue is the best offset step. If that draws a blank, please go far touch.
Remember to check both the built-in Windows Firewall, and any other firewalls (in Amazon EC2, cheque your security group settings for example).
If the Tentacle welcome folio is shown, good news - your network is fine.
Picket out for proxy servers or SSL offloading...
Octopus and Tentacle use TCP to communicate, with special treatment to enable web browsers to connect for diagnostic purposes. Full HTTP is not supported, and so network services like SSL offloading are not supported, and proxies are not supported in before versions of Octopus Deploy. Make sure there'south a direct connexion between the Octopus Server and Tentacle, without an HTTP proxy or a network appliance performing SSL offloading in between.
Also see, advanced back up for HTTP proxies.
Tentacle ping
Nosotros have built a small utility for testing the communications protocol betwixt two servers called Tentacle Ping. This tool helps isolate the source of communication bug without needing a full Octopus configuration. Information technology is built as a simple client and server component that emulates the communications protocol used past Octopus Server and Tentacle.
In Octopus 3.0 you volition need TentaclePing and TentaclePong, you lot cannot exam directly to Octopus Server nor Tentacle:
Listening Tentacles
- RunTentaclePing on your Octopus Server auto (which is the client in this relationship).
- RunTentaclePong on your Tentacle auto (which is the server in this relationship).
Use the output to help diagnose what is going wrong.
Polling Tentacles
- RunTentaclePing on your Tentacle machine (which is the client in this human relationship).
- RunTentaclePong on your Octopus Server machine (which is the server in this relationship).
Use the output to aid diagnose what is going wrong.
Check the IP address
Your Octopus Server or Tentacle Server may have multiple IP addresses that they listen on. For case, in Amazon EC2 machines in a VPN might accept both an internal IP address and an external addresses using NAT. Octopus Server and Tentacle Server may non listen on all addresses; y'all can bank check which addresses are configured on the server past running ipconfig /all from the command line and looking for the IPv4 addresses.
Bank check for zombie kid processes locking TCP ports (Listening Tentacles)
If Tentacle fails to start with an error message similar this:A required communications port is already in use.
The about common scenario is when you lot already have an example of Tentacle (or something else) listening on the same TCP port. However, we have seen cases where there is no running Tentacle in the list of processes. In this very specific case information technology could be due to a zombie PowerShell.exe or Calamari.exe procedure that was launched by Tentacle that is still property the TCP port. This can happen when attempting to cancel a task that has hung inside of Calamari/PowerShell. Merely rebooting the machine, or killing the zombie process will fix this outcome, and you should exist able to start Tentacle successfully.
Bank check the server service business relationship permissions
Listening Tentacle
If the Tentacle is running as theLocal System account yous can skip this section.
If the Tentacle is running every bit a specific user, make certain that the user has "total control" permission to theOctopus Habitation folder on the Tentacle machine. This is usually C:\Octopus - employ permissions recursively.
Polling Tentacle
For polling Tentacles we need to check the Octopus Server is running as theLocal Arrangement account. If it is, y'all can skip this section.
If the Octopus Server is running as a specific user, brand certain that the user has "total control" permission to theOctopus Habitation folder on the machine. This is usually C:\Octopus - apply permissions recursively.
Check the load time
In some DMZ-style environments without Internet access, failing to disable Windows code signing certificate revocation list checking will cause Windows to pause during loading of the Octopus applications and installers. This tin have a significant negative functioning impact, which may prevent Octopus and Tentacles connecting.
Check Tentacle.exe load time (Listening Tentacle)
To test this on a listening Tentacle, run:
Tentacle.exe assist If the control aid is not displayed immediately (< 1s) you lot may need to consider disabling the CRL check while the Tentacle is configured.
To do this open up Control Panel ➜ Net Options ➜ Advanced , and uncheck theCheck for publisher's document revocation choice every bit shown beneath.
Check Octopus.Server.exe load fourth dimension (Polling Tentacle)
To test this for a polling Tentacle, on the Octopus Server, run:
Octopus.Server.exe aid If the command help is not displayed immediately (< 1s) yous may need to consider disabling the CRL bank check while the Octopus Server is configured.
To practice this open Command Console ➜ Net Options ➜ Advanced , and uncheck theCheck for publisher'due south certificate revocation option as shown beneath.
Schannel and TLS configuration mismatches
Octopus uses Schannel for secure communications and volition attempt to employ the best available protocol available to both servers. If you lot are seeing mistake messages like below, try Troubleshooting Schannel and TLS:
Client-side:System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> Arrangement.ComponentModel.Win32Exception: One or more of the parameters passed to the function was invalid
Server-side:System.IO.IOException: Unable to read data from the transport connection: An existing connectedness was forcibly closed by the remote host.
Other error messages
Halibut.Transport.Protocol.ConnectionInitializationFailedException: Unable to process remote identity; unknown identity 'HTTP/1.0'
If a Tentacle health-check fails with an fault message containing this error bulletin, and so in that location is network infrastructure inserting a web folio into the communication. The most common components to do this are firewalls and proxy servers and then it'southward recommend to check your network setup to verify connectivity between the two servers using the information higher up and then update your infrastructure appropriately.
Demand support? We're hither to help.
richmondthametiones.blogspot.com
Source: https://octopus.com/docs/infrastructure/deployment-targets/windows-targets/troubleshooting-tentacles
0 Response to "Dgraph Please Retry Again Server Is Not Ready to Accept Requests"
Post a Comment