Server Status Check

Available in VPC

This section describes how to check the server status when a Server Status Check alarm occurs while using the server. The Xentools Agent operate as the Xen Guest Monitoring role on NAVER Cloud Platform's server. 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.

The causes and solutions to Server Status Check alarms for each error message are as follows:

Server operation-related errors

When a server operating error occurs, the following error messages are displayed.

Guest Agent has been deactivated. Check the server status. To stop the server by force, click the Force stop button on the console.

Cause 1: Xentools version issue

An alarm 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
     • Reinstall Xentools in Windows

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.
     

     

2. If the monitoring data is not properly collected, contact Customer support 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

An alarm 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
     • Reinstall Xentools in Windows

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.
   
2. Check the error in fstab and make any necessary corrections.

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 Manager server 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:

• CentOS 7: Kernel update restoration procedure
• Rocky Linux 8: Kernel update restoration procedure
• Ubuntu 20.04: Kernel update restoration procedure

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. Click the environment you are using in the Region menu and Platform menu of NAVER Cloud Platform console.
2. Click the Services > Compute > Server menus, in that order.
3. Click to select the server where the error occurred in the server list.
   • You can see that the [Force terminate] button is activated.
4. Click the [Force terminate] button.
   • For more information on force terminate, see Force terminate.
5. 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.

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. Click the environment you are using in the Region menu and Platform menu of NAVER Cloud Platform console.
2. Click the Services > Compute > Server menus, in that order.
3. Click to select the server where the error occurred in the server list.
   • You can see that the [Force stop] button is activated.
4. Click the [Force stop] button.
   • For more information on force stop, see Force stop.
   • The [Server connection console] button of the server is activated.
5. Click the [Server connection console] button, remove the setting error, and restart the server.

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 &