Inspect Ncloud Tool Kit (Linux)

Prev Next

Available in Classic

Linux Ncloud Tool Kit (Linux NTK) is a tool kit for inspecting Windows server provided on NAVER Cloud Platform. The provided functions are as follows:

  • Linux server status diagnosis functions
    • Check account configuration file
    • Check required processes and required scripts
    • DNS setting status
    • Check the network setting information
    • Root file system status
    • File system mount setting status
    • Check grub information
    • Check kernel image list
    • Repository setting status
    • Check essential package
  • Measuring storage IOPS
Note

This section only describes content related to NAVER Cloud Platform XEN hypervisor Linux server.

Diagnosis of Linux server status

You can diagnose the status of the Linux server and identify the problematic symptoms and causes of them using Linux NTK.

Account Config File

Check the account configuration file.

Function Cause Measures
/etc/passwd Check if the file exists
  • NTK execution result:
    [NOK] /etc/passwd file does not exist
 No /etc/passwd file exists Copy the default backup file by running the following command
# cp -p /etc/passwd- /etc/passwd
/etc/shadow Check if the file exists
  • NTK execution result:
    [NOK] /etc/shadow file does not exist
 No /etc/shadow file exists Copy the default backup file by running the following command
# cp -p /etc/shadow- /etc/shadow
/etc/group Check if the file exists
  • NTK execution result:
    [NOK] /etc/group file does not exist
 No /etc/group file exists Copy the default backup file by running the following command
# cp -p /etc/group- /etc/group

Mandatory Process

Check the processes that are essential to operating NAVER Cloud Platform Linux server.

Function Cause Measures
Check whether the Xentools package is installed
  • NTK execution result:
    [NOK] xe-guest-utilites installation status is Not OK... Please Check
 The Xentools package is not properly installed See Re-installing Xentools (Linux) to re-install Xentools (Linux)
Check the status of Xentools service registration (enable) upon booting
  • NTK execution result:
    [NOK] xentools auto start is Not OK.. Please check
 The Xentools service is not set to auto-start upon booting

Ncloud Setup Script

Check the setup scripts that are essential to operating NAVER Cloud Platform Linux server.

Caution

When you create the My server image, make sure to check the following table to reset the administrator password.

Function Cause Measures
Check the ncloud_auto.sh script
  • NTK execution result:
    [NOK] ncloud_auto.sh file does NOT exist.. Please Check
 No ncloud_auto.sh file exists
  • Install the ncloud_auto.sh setup script
  • Create a new server and copy the /usr/local/etc/ncloud_auto.sh script to under /usr/local/etc/ of the server in question
The ncloud_auto.sh file exists, but the permission does not satisfy the condition Run the following command to configure file permissions
# chmod 700 /usr/local/etc/ncloud_auto.sh
Check the mandatory content in the ncloud_auto.sh script
  • NTK execution result:
    [NOK] Mandatory Content does not exist in ncloud_auto.sh
 The ncloud_auto.sh script contains invalid content
  • Delete the existing ncloud_auto.sh script and re-install the script
  • Create a new server and copy the /usr/local/etc/ncloud_auto.sh script to under /usr/local/etc/ of the server in question
Check the mandatory script settings that must be executed upon booting
  • NTK execution result:
    [NOK] ncloud_auto Not exist in /etc/rc.local... Please Check
 No ncloud_auto.sh syntax exists in rc.local Insert the following syntax in /etc/rc.local
/usr/local/etc/ncloud_auto.sh > /tmp/. ncloud_out.log 2> /tmp/.ncloud_error.log &
Check the status of the mandatory service that must be executed upon booting
  • NTK execution result:
    [NOK] ncloud_auto.service is not enabled... Please Check
 ncloud_auto.service is disabled Run the following command to enable the ncloud_auto service
# systemctl enable ncloud_auto.service
Check the status of the rc.local file and the related services
  • NTK execution result:
    [NOK] /etc/rc.local or permission(-rwxr-xr-x) is Not OK.. Please Check
 Permission of the rc.local file does not meet the condition Run the following command to configure file permissions
# chmod 755 /etc/rc.local
rc-local.service is disabled Run the following command to enable the service
  • CentOS 7.x
    • # systemctl unmask rc-local.service
  • Ubuntu
    • # systemctl enable rc-local.service

DNS Config

Check DNS settings and status.

Function Cause Measures
Check the /etc/resolv.conf file
  • NTK execution result:
    [NOK] There is no exsit /etc/resolv.conf
 No /etc/resolv.conf file exists 1. Run the following command to create the `resolv.conf` file and update permissions
    # touch /etc/resolv.conf
    # chmod 644 /etc/resolv.conf
2. See Check DNS settings to check the DNS settings
Check the connection status with NAVER Cloud Platform internal servers
  • NTK execution result:
    [NOK] Can't connect to Naver Cloud internal server
 Failed to connect to NAVER Cloud's internal server See Check DNS settings to check the DNS settings
Check the mandatory content in the /etc/resolv.conf file
  • NTK execution result:
    [NOK] The configuration does not exist or is incorrect(127.0.0.53) in resolv.conf
    [NOK] The configuration does not exist or is incorrect(10.250.255.11,10.250.255.12) in resolv.conf
 Required settings are missing or erroneous in the /etc/resolv.conf file
Check the first DNS information in the /etc/resolv.conf file or systemd-resolve
  • NTK execution result:
    [NOK] First DNS Information in /etc/resolv.conf
    [NOK] First DNS Information in systemd-resolve
 The first DNS information is not the IP information provided by NAVER Cloud Platform

Network Config

Check the network setting information.

Function Cause Measures
Check network configuration files
  • NTK execution result:
    [NOK] /etc/networks file does not exist
    [NOK] /etc/sysconfig/network file does not exist
 No network configuration file exists Recreate the network configuration file and restart the network service
Check eth0 interface DHCP setting
  • NTK execution result:
    [NOK] eth0 is configured by [BOOTPROTO value]
 BOOTPROTO of eth0 is not set to DHCP Change the BOOTPROTO value to DHCP and restart network service
  • CentOS file path: /etc/sysconfig/network-scripts/ifcfg-eth0
    DEVICE=eth0
    MTU=8950
    BOOTPROTO=dhcp
    ONBOOT=yes
  • Ubuntu file path: /etc/network/interfaces
    auto eth0
    iface eth0 inet dhcp
    post-up /sbin/ifconfig eth0 mtu 8950
Check additional network interface BOOTPROTO value setting
  • NTK execution result:
    [NOK] BOOTPROTO entry does not exist in [NIC name]
 BOOTPROTO has no value set in the additional network interface Assign a value to BOOTPROTO and restart the network service
Check Network Manager service status (CentOS 7 only)
  • NTK execution result:
    [NOK] NetworkManager is active
 If the network manager is enabled in a CentOS 7 environment, then DHCP operation will cause an error Run the following command to disable the Network Manager service
# systemctl disable NetworkManager
# systemctl stop NetworkManager
# systemctl mask NetworkManager
# chkconfig network on
# systemctl restart network.service

Root file system

Check the root file system status.

Function Cause Measures
Check root file system (/) overall utilization
  • NTK execution result:
    [NOK] rootfs is Not OK.. (90%) Please Check
    [NOK] rootfs can't write(/tmp)
    [NOK] rootfs can't touch and delete(/tmp/rotest-temps)
 The root file system (/) has a high usage rate (90% or higher) Delete unnecessary files from the root file system (/)
Check if the /tmp directory exists
  • NTK execution result:
    [NOK] /tmp does not exist.
 No /tmp directory exists Run the following command to create the directory
# mkdir /tmp
Check the /tmp directory permission
  • NTK execution result:
    [NOK] /tmp permission(drwxrwxrwt.) is not ok
 Permission of /tmp does not meet the condition Run the following command to configure permissions
# chmod 1777 /tmp
Check the /tmp directory owner
  • NTK execution result:
    [NOK] /tmp user (user name) is not ok
 Owner of /tmp does not meet the condition Run the following command to set the directory owner
# chown root: /tmp
Check the owner group of the /tmp directory
  • NTK execution result:
    [NOK] /tmp group (user name) is not ok
 Owner group of /tmp does not meet the condition Run the following command to set the directory owner group
# chown :root /tmp

fstab File

Check the file system mount information configuration file (/etc/fstab).

Function Cause Measures
Check if /etc/fstab exists
  • NTK execution result:
    [NOK] /etc/fstab file does not exist
 No /etc/fstab file exists Run the following command to create the file and then see Using fstab to check the fstab file
# touch /etc/fstab
# chmod 644 /etc/fstab
Check the /etc/fstab syntax
  • NTK execution result:
    Field(*),Number of fields in fstab: [NOK]
    Field(1),Source device: [NOK]
    Field(2),Mount point dir: [NOK]
    Field(3),Filesystem exist: [NOK]
    Field(4),Options value: [NOK]
    Field(5),Config of filesystem dump: [NOK]
    Field(6),Config of filesystem check: [NOK]
 The content registered in /etc/fstab is incorrect or of an invalid format See Using fstab to check the fstab file

grub Config

Check the configured grub information.

Function Cause Measures
Check grub files
  • NTK execution result:
    [NOK] /boot/grub2/grub.cfg file does not exist
    [NOK] /boot/grub/grub.cfg file does not exist
 The mandatory file for booting has been deleted or damaged 1. Create and restore a new server after backing up the storage snapshot
2. Run the following command to create the grub file
# grub2-mkconfig -o /boot/grub2/grub.cfg

Kernel Image

Check the kernel image list.

Function Cause Measures
Check kernel images
  • NTK execution result:
    [NOK]/boot folder does not exist
 No /boot directory exists Create and restore a new server after backing up the storage snapshot

Repo Config

Check the repository configuration file.

Function Cause Measures
Check repository configuration directory
  • NTK execution result:
    [NOK] /etc/apt folder does not exist
    [NOK] /etc/yum.repos.d folder does not exist
 No repository configuration directory exists Run the following command to create a repository configuration directory
  • CentOS
    • # mkdir -p /etc/yum.repos.d/
  • Ubuntu
    • # mkdir -p /etc/apt/
Check repository configuration files
  • NTK execution result:
    [NOK] /etc/apt/sources.list file does not exist
    [NOK] /etc/yum.repos.d/CentOS-Base.repo file does not exist
 No repository configuration file exists Run the following commands to download the repository configuration file
  • CentOS 7.x
    • # wget -q http://init.ncloud.com/server/linux/repo/centos7/CentOS-Base.repo -O /etc/yum.repos.d/CentOS-Base.repo
  • Ubuntu 18.04
    • # wget -q http://init.ncloud.com/server/linux/repo/ubuntu18/sources.list -O /etc/apt/sources.list

Mandatory Package

Check the packages that are essential to operating NAVER Cloud Platform Linux server.

Function Cause Measures
Check if the wget package exists
  • NTK execution result:
    [NOK] wget package is not installed
 No wget package is installed Run the following commands to download the package
  • CentOS
    • # yum install wget
  • Ubuntu
    • # apt install wget
Check if /usr/bin/wget file can run
  • NTK execution result:
    [NOK] /usr/bin/wget file does not exist or permission is not OK... Please Check
 No wget execution file exists or there is no permission to run the file Run the following commands to download the package
  • CentOS
    • # yum install wget
  • Ubuntu
    • # apt install wget
Check if the dos2unix package exists
  • NTK execution result:
    [NOK] dos2unix package is not installed
 No dos2unix package is installed Run the following commands to download the package
  • CentOS
    • # yum install dos2unix
  • Ubuntu
    • # apt install dos2unix
Check if /usr/bin/dos2unix file can run
  • NTK execution result:
    [NOK] /usr/bin/dos2unix file does not exist or permission is not OK... Please Check
 No dos2unix execution file exists or there is no permission to run the file Run the following commands to download the package
  • CentOS
    • # yum install dos2unix
  • Ubuntu
    • # apt install dos2unix
Check if the rpcbind package exists (except for Ubuntu)
  • NTK execution result:
    [NOK] rpcbind package is not installed
 No rpcbind package is installed Run the following command to download the package
  • CentOS
    • # yum install rpcbind
Check if the /usr/sbin/rpcbind file can run (except for Ubuntu)
  • NTK execution result:
    [NOK] /usr/sbin/rpcbind file does not exist or permission is not OK... Please Check
 No rpcbind execution file exists or there is no permission to execute the file Run the following command to download the package
  • CentOS
    • # yum install rpcbind
Check if the chrony package exists (except for Ubuntu)
  • NTK execution result:
    [NOK] chrony package is not installed
 No chronyd package is installed Run the following command to download the package
  • CentOS
    • # yum install chrony
Check if the /usr/sbin/chronyd file can run (except for Ubuntu)
  • NTK execution result:
    [NOK] /usr/sbin/chronyd file does not exist or permission is not OK... Please Check
 No chrony execution file exists or there is no permission to run the file Run the following command to download the package
  • CentOS
    • # yum install chrony

Measuring storage IOPS

Linux NTK provides FIO test tools to measure the performance of storage attached to Linux servers.

1. Run Linux NTK

To run Linux NTK, do the following:

  1. Enter the cd /usr/local/etc command.
    • You are moved to the path where NTK is located.
  2. Enter the tar zxvf ntk.tar.gz command.
    • The NTK file is unzipped.
    • If no ntk.tar.gz file exists or if you wish to replace the existing file with the latest version, enter wget -P /usr/local/etc http://init.ncloud.com/server/ntk/linux/xen/ntk.tar.gz to download the file.
  3. Enter the following commands to run NTK.
    # cd /usr/local/etc/ntk
# ./ntk

2. Run FIO TEST

To measure IOPS on storage disks, do the following:

  1. After running NTK, click (E) EXECUTE - << Run System Apps >>.
    server-ts-ntk-classic_fio-test-01

  2. Click (F) FIO TEST - << FOR DISK IO TEST >>.
    server-ts-ntk-classic_fio-test-02

  3. Click the [YES] button to measure disk IOPS.
    server-ts-ntk-classic_fio-test-03

  4. Select the disk to measure the IOPS for and click the [OK] button.

    Note

    If the server has only 1 disk connected, this step is skipped and the disk is automatically selected.

    server-ts-ntk-classic_fio-test-04

  5. Select the IOPS test options and click the [OK] button.
    server-ts-ntk-classic_fio-test-05

    • random read: random reading
    • random write: random writing
    • Disk IOPS is measured.
      server-ts-ntk-classic_fio-test-06

  6. Check the result upon completing the measurement, and click the [OK] button.
    server-ts-ntk-classic_fio-test-07

  7. Click the [Yes] button to forward the log file to NAVER Cloud Platform's technical support center. If you will not forward it, click the [No] button to exit.
    server-ts-ntk-classic_fio-test-08

    • If the logs have been successfully forwarded, you can see the log download short-URL with a delivery success message.