Contents x
Check Ncloud Tool Kit
  • Print
  • PDF
Contents

Check Ncloud Tool Kit

  • Print
  • PDF

The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.

Available in VPC

Before use

Q. What is Ncloud Tool Kit (NTK)?
The following functions are provided as a tool kit for Linux servers provided by Ncloud.

(1) Linux server status diagnosis

  • Required account verification
  • Check the startup script
  • Check Xentools
  • Check key file settings
  • Check network settings
  • Check whether the kernel is updated
  • Check the file system

(2) IO test
(3) GPU log collection
(4) Upload log data collected by NTK
(5) system patch

Diagnose Linux Server Status

Diagnose the status of the Linux server, check the symptoms and causes, and proceed according to the measures.

Required account verification

Symptoms Cause Action Plan
1. Check whether the monitoring account exists
NTK execution result: [NOK] nbpmon is NOT OK		 The monitoring account does not exist. Please create an account with the command below.
groupadd -g 1000 nbpmon
useradd -m -d /home1/nbpmon -s /bin/bash -c "agent-account" -u
1000 -g 1000 nbpmon

Check the startup (setup) script

Symptoms Cause Measures to be taken
1. Check essential setup script for server creation/setting
※ Required for creating my server image and initializing the administrator password in the console.
NTK execution result: [NOK] ncloud_auto.sh file does NOT exist.. Please Check		 The ncloud_auto.sh file does not exist.
  • Ncloud_auth.sh setup script needs to be installed.
  • After creating a new server, add /usr/local/etc/ncloud_auto.sh script to /usr/local/etc/ sub Please move it to
You need to check the permissions of the ncloud_auto.sh file. Set file permissions with the command below.
chmod 700 /usr/local/etc/ncloud_auto.sh
2. Check the required script settings to be executed at boot time
NTK execution result: [NOK] nsight_updater, ncloud_auto Not exist in /etc/rc.local... Please Check 		ncloud_auto.sh syntax does not exist in rc.local. Put the following syntax in /etc/rc.local.
/usr/local/etc/ncloud_auto.sh > /tmp/. ncloud_out.log 2> /tmp/.ncloud_error.log &
3. Check rc.local file permission and service registration
NTK execution result: [NOK] /etc/rc.local or permission(-rwxr-xr-x) is Not OK.. Please Check < /td> 		rc.local file permissions do not match criteria. Set file permissions with the command below.
chmod 755 /etc/rc.local
rc.local systemd service is disabled. Enable the service with the command below.
centos 7.x) systemctl unmask rc-local.service
ubuntu) systemctl enable rc-local.service

Check Agent

Symptoms Cause Measures to be taken
1. Check required files for monitoring
NTK execution result: [NOK] cloud insight agent is Not exist.. Please Check		 Required file does not exist in directory /home1/nbpmon/agent_controller_linux/ Please refer to the relevant guide to reinstall.
  • Troubleshooting
    • 2. Check monitoring update settings
    NTK execution result: [NOK] cloud insight updater Not exist or permission(-rwxr-xr-x) is Not OK... Please Check     		The monitoring update file does not exist. Please refer to the relevant guide to reinstall.
  • Troubleshooting
    • The permissions of the monitoring update file do not match the criteria. Change the permission with the command below.
    chmod 544 /home1/nbpmon/agent_controller_linux/agent_updater.py
    3. Monitoring service registration status check
    NTK execution result: [NOK] cloud insight process auto start is Not OK.. Please check     		Monitoring service registration status is disabled. Register the monitoring service with the command below.
    systemctl enable nsight-agent.service

    Check Xentools

    Symptoms Cause Action Plan
    1. Confirmation of normal Xentools installation
    NTK execution result: [NOK] xe-guest-utilites installation status is Not OK... Please Check    		 Xentools installation status is abnormal. Please refer to the relevant guide to reinstall Xentools.
  • Using fstab
    		•
    2. Check service registration status (enable) when booting Xentools
    NTK execution result: [NOK] xentools auto start is Not OK.. Please check    		 The Xentools service is not set to run at boot time. Please refer to the relevant guide to reinstall Xentools.
  • Using fstab
    		•

    Check file settings

    Symptoms Cause Action Plan
    1. Check whether /etc/fstab exists
    NTK execution result: [NOK] /etc/fstab file does not exist    		 The /etc/fstab file does not exist. After creating a file with the command below, check it by referring to the related guide.
    touch /etc/fstab
    chmod 644 /etc/fstab
  • Using fstab
    		•
    2. Check the syntax of /etc/fstab
    NTK execution result: Field(*),Number of fields in fstab: [NOK]
    Field(1),Source device: [NOK]< br>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 contents registered in /etc/fstab are not in the correct format or have incorrect contents. Please check the related guides.
  • Using fstab
    		•
    3. Check /etc/passwd, /etc/shadow, /etc/group
    NTK execution result: [NOK]/etc/passwd file does not exist
    [NOK] /etc/ shadow file does not exist
    [NOK] /etc/group file does not exist    		 OS essential files do not exist. Please use it after creating and restoring a new VM after backing up the storage snapshot.
    4. Check the existence of grub file
    NTK execution result: [NOK] /boot/grub2/grub.cfg file does not exist
    [NOK] /boot/grub/grub.cfg file does not exist    		 Essential files required for booting have been deleted and corrupted. Please use it after creating and restoring a new VM after backing up the storage snapshot.

    Etc

    The directory The file
    Symptoms Cause Measures to be taken
    1. Check kernel image
    NTK execution result: [NOK] /boot folder does not exist    		 /boot directory does not exist Please use it after backing up the storage snapshot, creating a new VM and restoring it.
    2. Check the default yum file and settings
    NTK execution result: [NOK] /etc/yum.repos.d folder does not exist
    [NOK] /etc/apt folder does not exist
    [NOK] /etc/yum.repos.d/CentOS-Base.repo file does not exist
    [NOK] /etc/apt/sources.list file does not exist     		/etc/yum.repos.d does not exist.
    The /etc/apt directory does not exist.
  • Please refer to the example below to create it.
    /etc/yum.repos.d/CentOS-Base.repo
    1) CentOS 7.8
    [base]
    name=CentOS-$releasever - Base
    baseurl=http://mirror.ncloud.com/centos/$releasever/os/$basearch
    gpgcheck=1
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7
    [update]
    name=CentOS-$releasever - Updates
    baseurl=http://mirror.ncloud.com/centos/$releasever/updates/$basearch/
    gpgcheck=1
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7
    [extras]
    name=CentOS-$releasever - Extras
    baseurl=http://mirror.ncloud.com/centos/$releasever/extras/$basearch/
    gpgcheck=1
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7
    [centosplus]
    name=CentOS-$releasever - Plus
    baseurl=http://mirror.ncloud.com/centos /$releasever/centosplus/$basearch/
    gpgcheck=1
    enabled=0
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7
    [contrib]
    name=CentOS-$releasever - Contrib
    baseurl=http://mirror.ncloud.com/centos /$releasever/contrib/$basearch/
    gpgcheck=1
    enabled=0
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7

    2) CentOS 7.3
    [base]
    name=CentOS-$releasever - Base
    baseurl=http://mirror.ncloud.com/centos /$releasever/os/$basearch
    gpgcheck=1
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7
    [update]
    name=CentOS-$releasever - Updates
    baseurl=http://mirror.ncloud.com/centos/$releasever/updates/$basearch/
    gpgcheck=1
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7
    [extras]
    name=CentOS-$releasever - Extras
    baseurl=http://mirror.ncloud.com/centos/$releasever/extras/$basearch/
    gpgcheck=1
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7
    [centosplus]
    name=CentOS-$releasever - Plus
    baseurl=http://mirror.ncloud.com/centos/$releasever/centosplus/$basearch/
    gpgcheck=1
    enabled=0
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7
    [contrib]
    name=CentOS-$releasever - Contrib
    baseurl=http://mirror.ncloud.com/centos/$releasever/contrib/$basearch/
    gpgcheck=1
    enabled=0
    gpgkey=http://mirror.ncloud.com/centos/RPM-GPG-KEY-centos7
    [root@pub-vpc-cent73 ~]# cat /etc/yum.repos.d /CentOS-Base.repo | egrep -v "#"

    /etc/apt/sources.list
    3) ubuntu 20.04
    deb http://repo.ncloud.com/ubuntu focal main restricted
    deb http://repo.ncloud.com/ubuntu focal-updates main restricted
    deb http://repo.ncloud.com/ubuntu focal universe
    deb http://repo.ncloud.com/ubuntu focal-updates universe
    deb http://repo.ncloud.com/ubuntu focal multiverse
    deb http://repo.ncloud.com/ubuntu focal-updates multiverse
    deb http://repo.ncloud.com/ubuntu focal-backports main restricted universe multiverse
    deb http://repo.ncloud.com/ubuntu focal-security main restrict
    deb http://repo.ncloud.com/ubuntu focal-security universe
    deb http://repo.ncloud.com/ubuntu focal-security multiverse

    4) ubuntu 18.04
    deb http://archive.ubuntu.com/ubuntu bionic main restricted
    deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted
    deb http://archive.ubuntu.com/ubuntu bionic universe
    deb http://archive.ubuntu.com/ubuntu bionic-updates universe
    deb http://archive.ubuntu.com/ubuntu bionic multiverse
    deb http://archive.ubuntu.com/ubuntu bionic-updates multiverse
    deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
    deb http://archive.ubuntu.com/ubuntu bionic-security main restricted
    deb http://archive.ubuntu.com/ubuntu bionic-security main restricted
    deb http://archive.ubuntu.com/ubuntu bionic-security main restricted

    5) ubuntu 16.04
    deb http://kr.archive.ubuntu.com/ubuntu/ xenial main restricted
    deb http://kr.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
    deb http://kr.archive.ubuntu.com/ubuntu/ xenial universe
    deb http://kr.archive.ubuntu.com/ubuntu/ xenial-updates universe
    deb http://kr.archive.ubuntu.com/ubuntu/ xenial multiverse
    deb http://kr.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
    deb http://kr.archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse
    deb http://security.ubuntu.com/ubuntu xenial-security main restricted
    deb http://security.ubuntu.com/ubuntu xenial-security universe
    deb http://security.ubuntu.com/ubuntu xenial-security multiverse
    • /etc/yum.repos.d/CentOS-Base.repo does not exist.
    The file /etc/apt/sources.list does not exist.
    3. Check Network Manager activation (CentOS 7 only)
    NTK execution result: [NOK] NetworkManager is active     		When Network Manager is activated in a CentOS 7 environment, an error occurs in dhcp operation. Disable the Network Manager service with the command below.
    systemctl disable NetworkManager
    Was this article helpful?
    What's Next