Troubleshooting server
- Print
- PDF
Troubleshooting server
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic
It describes problematic situations users may encounter when using Server, as well as their causes and resolutions.
Server access failure
The following describes the symptoms and causes of failing to access to the server and their solutions:
| Symptom | Cause | Solution | Reference guide |
|---|---|---|---|
| Can't access server | Server is stopped | Start the server from the NAVER Cloud Platform console and reconnect | - |
| The computer attempting to access and its network is not allowed in the ACG setting | Add a rule to the ACG to allow network access to the computer attempting to connect | See ACG | |
| Network connection failure of the computer attempting to access | Check the network connection status and reconnect | - | |
| IP or external port input error | Check the port forwarding or public IP information under the console's server details, enter it correctly, and then reconnect | See access Server | |
| Entered wrong password error | See manage server |
Server creation failure
The following are the causes and solutions for each warning text about the situation where server creation fails:
| Warning message | Cause | Solution |
|---|---|---|
| Server can't be created as the server creation limit has been exceeded. | Server creation limit set on the account exceeded |
|
| An error occurred while creating the server. | Internal error |
|
Failed to detach storage from server
If you try to detach block storage from the server but fail, the following warning messages, solutions, and troubleshooting tips are as follows: For information on how to detach storage, see using storage.
| Warning message | Cause | Solution |
|---|---|---|
| The storage is mounted on the server. Unmount the storage and try again. | The storage status is failed to detach since it has failed to Detach the additional storage | 1. Click [Recover] next to the storage status to restore it to In-use 2. Upon changing the storage status to In-use, access to the console to unmount, and retry disconnecting the server |
| In case of storage connected to a Linux server, an error due to the mount information (garbage) value | ||
| Unable to detach since the I/O on storage connected to the server is in progress |
Server Status Check alarm occurs
Server Status Check is a message activated when an error occurs while you're using Server. The symptoms, causes, and solutions to Server Status Check alarms are as follows:
| Server operation circumstance | Server Status Check message | Cause | Solution |
|---|---|---|---|
| Server running | Guest Agent is disabled. Check the server status. See the manual for how to check the status. To force stop the server, click the force stop button on the console. | Server Hang and insufficient resource | See Server Status Check |
| Xentools version problem | Reinstall Xentools (see Windows, Linux) | ||
| Stopping or restarting a running server | The server reboot or stop was not completed properly. A server status check is required. To force stop the server, click the force stop button on the console. See the manual for information on how to check the status and take necessary measures. | Server internal errors may delay or prevent server restart or server creation If none of these are applicable, contact customer support |
Diagnosis of server status
If you want to diagnose the status of the server, you can perform the status diagnosis through the Ncloud Tool Kit (NTK) provided by NAVER Cloud Platform. For more information, see Inspect Ncloud Tool Kit (Linux/Windows).
Was this article helpful?