Troubleshooting server

Troubleshooting Server

Article Summary

Share feedback

Thanks for sharing your feedback!

Available in Classic

It describes problematic situations users may encounter when using Server, as well as their causes and resolutions.

Server connection failure

The following describes the symptoms and causes of failing to connect 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 connect 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 connect	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	Check the admin password from the console, enter the password correctly, and then reconnect If you can't remember the admin password you changed, reset it on the console and reconnect	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	Applied for fewer servers than server creation limit If you need more servers than the limit, contact Customer support to increase the server creation limit and retry
An error occurred while creating the server.	Internal error	After a short pause, retry creating the server Adjust the number of servers to create <example> If you need 10 servers, try creating 5 servers in 2 batches or 1 server in 10 batches Change the zone to retry creating a server Downgrade the server spec to retry creating If the above does not work, contact Customer support{target="_blank"}

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 shown. 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, connect 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	After unmounting the file system from the OS, delete the mount information from /etc/fstab and retry If the above method does not solve the problem, contact Customer support
	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
Server running		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 Cause 1: Xentools version problem Cause 2: DHCP setting error Cause 3: fstab setting error Cause 4: delayed Windows update and file system check Cause 5: kernel update error Cause 6: server hang while performing diagnostic interrupt If none of these are applicable, contact Customer support	For more detailed measures by cause, see Server Status Check For issues related to the Xentools version, see Reinstall Xentools (Windows, Linux)

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?

What's Next

Inspecting DNS configuration

Table of contents

Server connection failure
Server creation failure
Failed to detach storage from server
Server Status Check alarm occurs
Diagnosis of server status