![]() If you do not see a login prompt, your Compute Instance may have issues with booting. If you see a log in prompt, but you have forgotten the credentials for your Compute Instance, follow the instructions for resetting your root password and then attempt to log in at the Lish console again. If you can log in at the Lish console, move on to the diagnose network connection issues section of this guide. The root user is available in Lish even if root user login is disabled in your SSH configuration. If a login prompt exists, try logging in with your root user credentials (or any other Linux user credentials that you previously created on the server). If the Compute Instance is listed as running in the Cloud Manager, or after you boot it from the Manager, open the Lish console and look for a login prompt. If the instance is powered off, turn it on. Log in to the Cloud Manager and inspect the Compute Instance’s dashboard. Review the installation instructions in Linode’s Diagnosing Network Issues with MTR guide and install MTR on your computer. ![]() MTR also runs several iterations of its tracing algorithm, which means that it can report statistics like average packet loss and latency over the period that the MTR test runs. MTR is similar to the traceroute tool, in that it will trace and display your traffic’s route. It is possible to analyze the route that your traffic takes for possible service interruptions using a tool called MTR. When your network traffic leaves your computer to your Compute Instance, it travels through a series of routers that are administered by your internet service provider, by Linode’s transit providers, and by the various organizations that form the Internet’s backbone. In particular, using your web browser is a fast and simple way to access Lish. To learn about Lish in more detail, and for instructions on how to connect to your Compute Instance via Lish, review the Using the Lish Console guide. Much of your troubleshooting for basic connection issues will be performed from the Lish console. Lish does not establish a network connection to your Compute Instance, so you can use it when your networking is down or SSH is inaccessible. Lish is a shell that provides access to your Compute Instance’s serial console. There are a few core troubleshooting tools you should familiarize yourself with that are used when diagnosing connection problems. Refer to Linode’s Scope of Support for a description of which issues Linode Support can help with. Linode is not responsible for the configuration or installation of software on your Compute Instance. Or, post a new question in the Community Site and include your commands’ output. If the information and logs you gather do not match a solution outlined here, consider searching the Linode Community Site for posts that match your system’s symptoms. For some specific examples of diagnostic information, this guide also explains the corresponding cause of the issue and presents solutions for it. These commands can produce diagnostic information and logs that may expose the root of your connection issues. This guide explains how to use different troubleshooting commands on your Compute Instance. Instead, refer to the Troubleshooting SSH or Troubleshooting Web Servers, Databases, and Other Services guides. ![]() If you can ping your Compute Instance, but you cannot access SSH or other services, this guide will not assist with troubleshooting those services. If you need to troubleshoot memory and networking, read our guide on Troubleshooting Memory and Networking Issues. This guide is designed as a useful resource for either of these scenarios. Similarly, your server may be unresponsive after maintenance was applied by Linode to your server’s host (frequently, this is correlated with software/distribution upgrades performed on your deployment prior to the host’s maintenance). One reason that an instance may be unresponsive is if you recently performed a distribution upgrade or other broad software updates to your system, as those changes can lead to unexpected problems for your core system components. ![]() This guide presents troubleshooting strategies for Compute Instances that are unresponsive to any network access. ![]()
0 Comments
Leave a Reply. |