--- title: "Server Status Check" slug: "server-ts-statuscheck-vpc" tags: ["VPC", "Server", "Server Status Check", "Troubleshooting"] updated: 2026-10-08T06:54:15Z published: 2026-10-08T06:54:15Z canonical: "guide.ncloud-docs.com/server-ts-statuscheck-vpc" --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Server Status Check Available in VPC This section describes how to check the server status when a Server Status Check notification occurs while using the server. The Xentools Agent, which performs Xen guest monitoring, runs on NAVER Cloud Platform servers. Server Status Checker is displayed on the console server list as follows if Xentools Agent is not functioning properly or if a server is operating abnormally due to other reasons. ![compute-19-1-10_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/compute-19-1-10_en.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A24%3A52Z&se=2026-11-14T06%3A24%3A52Z&sr=c&sp=r&sig=wUPWWkhyZo6BvEqigY3%2F44q7DiiWvb2pfdczzvJkLfA%3D) The causes and solutions to Server Status Check notification for each error message are as follows: | Error message | Cause | Solution | | --- | --- | --- | | Guest Agent is disabled. Check the server status. To stop the server by force, click Force stop in the console. | Xentools version issue | See [Cause 1: Xentools version issue](/docs/en/server-ts-statuscheck-vpc#원인1Xentools버전이슈1). | | Server error | See [Cause 2: Server error](/docs/en/server-ts-statuscheck-vpc#원인2서버오류). | | The guest agent couldn't be started because the mount has been misconfigured. | Xentools version issue | See [Cause 1: Xentools version issue](/docs/en/server-ts-statuscheck-vpc#원인1Xentools버전이슈2). | | fstab setting error | See [Cause 2: fstab setting error](/docs/en/server-ts-statuscheck-vpc#원인2fstab설정오류). | | Delayed booting due to Windows update and file system check | See [Cause 3: Delayed booting due to Windows update and file system check](/docs/en/server-ts-statuscheck-vpc#원인3Windows업데이트및파일시스템체크로인한부팅지연). | | Kernel update error | See [Cause 4: Kernel update error](/docs/en/server-ts-statuscheck-vpc#원인4커널업데이트오류). | | Other system setup errors | See [Cause 5: Other system setup errors](/docs/en/server-ts-statuscheck-vpc#원인5기타시스템설정오류). | | Guest Agent has not been installed. Servers without the Agent installed may experience errors in some features. Refer to the guide for Agent installation. If an error occurs after installation, contact Customer Support. | The KVM server's Guest Agent not installed properly (The Guest Agent must be installed on KVM servers that display this notification.) | - [Check KVM Guest Agent (Linux)](https://guide.ncloud-docs.com/docs/en/kvm-guest-agent-check-linux) - [Check Virtio Win and KVM Guest Agent (Windows)](https://guide.ncloud-docs.com/docs/en/server-ts-kvm-win-vpc#kvm-guest-agent-점검) | Note If the problem persists even after inspection and measures, contact [Customer Support](https://www.ncloud.com/support/question/service). ## Server operation-related errors When a server operating error occurs, the following error messages are displayed. Guest Agent is disabled. Check the server status. To stop the server by force, click Force stop in the console. ### Cause 1: Xentools version issue A notification may occur due to a version error following an update to Xentools agent package, or a service error in Xentools Agent Service. The following shows how to resolve the Xentools version issue. 1. Enter the following command to check the version and operation of Xentools. - CentOS ``` rpm -qa | grep xe-guest-utilities systemctl status xe-linux-distribution.service ``` - Ubuntu ``` dpkg -l | grep xe-guest-utilities systemctl status xe-linux-distribution.service ``` 2. If a problem is found as a result of checking Xentools Agent Service, reinstall Xentools. - For more information on installing Xentools, see the following guides. - [Reinstall Xentools in Linux](/docs/en/server-ts-xen-lin-vpc) - [Reinstall Xentools in Windows](/docs/en/server-ts-xen-win-vpc) ### Cause 2: Server error Monitoring data collection may fail due to server hangs, kernel errors, disk I/O, OOM, and so on. The following describes how to resolve server errors. 1. Check the status information of CPU, memory, and so on collected by the server. - If monitoring data are collected normally, the graph below can be checked. ![server-ts-statuscheck-vpc_compute-19-1-1](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-statuscheck-vpc_compute-19-1-1.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A24%3A52Z&se=2026-11-14T06%3A24%3A52Z&sr=c&sp=r&sig=wUPWWkhyZo6BvEqigY3%2F44q7DiiWvb2pfdczzvJkLfA%3D) ![server-ts-statuscheck-vpc_compute-19-1-2](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-statuscheck-vpc_compute-19-1-2.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A24%3A52Z&se=2026-11-14T06%3A24%3A52Z&sr=c&sp=r&sig=wUPWWkhyZo6BvEqigY3%2F44q7DiiWvb2pfdczzvJkLfA%3D) 2. If the monitoring data is not properly collected, contact [Customer Support](https://www.ncloud.com/support/question/service) to have the status of the server checked. ## Errors related to creating and rebooting the server The following error messages are displayed if errors occur related to creating and rebooting the server. The guest agent couldn't be started because the mount has been misconfigured. ### Cause 1: Xentools version issue A notification may occur due to a version error following an update to Xentools agent package, or a service error in Xentools Agent Service. The following shows how to resolve the Xentools version issue. 1. Enter the following command to check the version and operation of Xentools. - CentOS ``` rpm -qa | grep xe-guest-utilities systemctl status xe-linux-distribution.service ``` - Ubuntu ``` dpkg -l | grep xe-guest-utilities systemctl status xe-linux-distribution.service ``` 2. If a problem is found as a result of checking Xentools Agent Service, reinstall Xentools. - For more information on installing Xentools, see the following guides. - [Reinstall Xentools in Linux](/docs/en/server-ts-xen-lin-vpc) - [Reinstall Xentools in Windows](/docs/en/server-ts-xen-win-vpc) ### Cause 2: fstab setting error An error may have occurred due to incorrect fstab settings. Check the fstab settings with the following procedure. 1. Enter the `mount -av` command and diagnose the `/etc/fstab` details. ![server-ts-statuscheck-vpc_compute-19-1-9](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-statuscheck-vpc_compute-19-1-9.png?sv=2026-02-06&spr=https&st=2026-11-14T05%3A24%3A52Z&se=2026-11-14T06%3A24%3A52Z&sr=c&sp=r&sig=wUPWWkhyZo6BvEqigY3%2F44q7DiiWvb2pfdczzvJkLfA%3D) 2. Check the error in fstab and edit the necessary information. ### Cause 3: Delayed booting due to Windows update and file system check An error may have occurred due to a delay in Windows updates or file system check. See [Manage server](/docs/en/server-manage-vpc) to check the current server status. ### Cause 4: Kernel update error Updating with a kernel version not provided by NAVER Cloud Platform can cause errors. Check the solutions in accordance with the time when the error occurred. #### If restart fails after a kernel update If restart fails after a kernel update, you must revert to the previous version of the kernel. For more details on reverting to a previous version of kernel, see the following: - NAVIX 9: [Kernel update restoration procedure](/docs/en/navix9-kernel-update#%EC%BB%A4%EB%84%90%EC%97%85%EB%8D%B0%EC%9D%B4%ED%8A%B8%EC%9B%90%EB%B3%B5) - Rocky Linux 8: [Kernel update restoration procedure](/docs/en/rockylinux8-kernel-update#%EC%BB%A4%EB%84%90%EC%97%85%EB%8D%B0%EC%9D%B4%ED%8A%B8%EC%9B%90%EB%B3%B5) - Rocky Linux 9: [Kernel update restoration procedure](/docs/en/rockylinux9-kernel-update#%EC%BB%A4%EB%84%90%EC%97%85%EB%8D%B0%EC%9D%B4%ED%8A%B8%EC%9B%90%EB%B3%B5) - Ubuntu 22.04: [Kernel update restoration procedure](/docs/en/ubuntu22-kernel-update#%EC%BB%A4%EB%84%90%EC%97%85%EB%8D%B0%EC%9D%B4%ED%8A%B8%EC%9B%90%EB%B3%B5) - Ubuntu 24.04: [Kernel update restoration procedure](/docs/en/ubuntu24-kernel-update#%EC%BB%A4%EB%84%90%EC%97%85%EB%8D%B0%EC%9D%B4%ED%8A%B8%EC%9B%90%EB%B3%B5) #### If an error occurs during creation of My server image The following shows how to resolve errors that occur during creation of My server image. 1. In the VPC environment of the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Compute** > **Server**. 2. Click to select the server where the error occurred in the server list. - You can see that the **[Force return]** button is enabled. 3. Click **[Force return]**. - For more information on force return, see [Force return](/docs/en/server-ts-return-vpc#%EA%B0%95%EC%A0%9C%EB%B0%98%EB%82%A9). 4. Remove the error in the original server and re-create the My server image. - For detailed information on creating My server image, see [Create My server image](/docs/en/server-serverimage-vpc#%EB%82%B4%EC%84%9C%EB%B2%84%EC%9D%B4%EB%AF%B8%EC%A7%80%EC%83%9D%EC%84%B1). #### If an error occurs when you re-start the operating server or try to restart after stopping The following shows how to resolve errors that have occurred when you restart the operating server or try to restart after stopping. 1. In the VPC environment of the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Compute** > **Server**. 2. Click to select the server where the error occurred in the server list. - You can see that the **[Force stop]** button is enabled. 3. Click **[Force stop]**. - For more information on force stop, see [Force stop](/docs/en/server-ts-return-vpc#%EA%B0%95%EC%A0%9C%EC%A0%95%EC%A7%80). - The **[Server connection console]** button of the server is enabled. 4. Click **[Server connection console]**, remove the setting error, and restart the server. Note If **[Server connection console]** is disabled, contact [Customer Support](https://www.ncloud.com/support/question/service). ### Cause 5: Other system setup errors Syntax changes within `resolve.conf` and `rc.local` can cause errors. Enter the appropriate command for the server image to check the standard settings. - For Ubuntu 18 or higher: Check the `/run/systemd/resolve/resolv.conf` file. ``` nameserver 169.254.169.53 nameserver 169.254.169.54 ``` - For other server images: Check the `/etc/rc.local` file. ``` /usr/local/etc/ncloud_auto.sh > /tmp/.ncloud_out.log 2> /tmp/.ncloud_error.log & ```