interruptServerInstance

Available in VPC

Run an interrupt for diagnosing a server instance (VM) with an abnormal action.
For more information, see User guide > Server > VPC > Server troubleshooting> Diagnostic interrupt.

Caution

Only server instances (VMs) that are currently running are supported. The KVM hypervisor type supports Linux and Windows-based operating systems, while the XEN hypervisor type supports only Windows-based operating systems.

Syntax

The interruptServerInstance syntax is as follows:

./ncloud vserver interruptServerInstance \
    --serverInstanceNo <server-instance-no> \
    [--regionCode <KR|SGN|JPN>] \
    [--output <json|xml>]

Options

This section describes the options available when running interruptServerInstance.

Required options

The following options are required for interruptServerInstance.

Options	Type	Required	Description
`--serverInstanceNo`	String	Required	Server instance number See getServerInstanceList.

Common options

For information about the options common to all vserver subcommands, see Server (VPC) options.

Examples

If the diagnostic interrupt request is successful, the server's latest information is returned.

Command

The command example is as follows:

./ncloud vserver interruptServerInstance \
    --serverInstanceNo 34567890 \
    --regionCode KR \
    --output json

Output

The output example is as follows:

<interruptServerInstanceResponse>
  <returnCode>0</returnCode>
  <returnMessage>success</returnMessage>
  <totalRows>1</totalRows>
  <serverInstanceList>
    <serverInstance>
      <serverInstanceNo>***4299</serverInstanceNo>
        <serverName>test-***</serverName>
        <serverDescription></serverDescription>
        <cpuCount>2</cpuCount>
        <memorySize>4294967296</memorySize>
        <platformType>
          <code>LNX64</code>
          <codeName>Linux 64 Bit</codeName>
        </platformType>
        <loginKeyName>test-***</loginKeyName>
        <publicIpInstanceNo></publicIpInstanceNo>
        <publicIp></publicIp>
      <serverInstanceStatus>
        <code>RUN</code>
        <codeName>Server run state</codeName>
      </serverInstanceStatus>
      <serverInstanceOperation>
        <code>SHTDN</code>
        <codeName>Server SHUTDOWN OP</codeName>
      </serverInstanceOperation>
      <serverInstanceStatusName>shutting down</serverInstanceStatusName>
      <createDate>2020-08-24T09:41:23+0900</createDate>
      <uptime>2020-08-24T09:51:26+0900</uptime>
      <serverImageProductCode>SW.VSVR.OS.LNX64.CNTOS.0703.B050</serverImageProductCode>
      <serverProductCode>SVR.VSVR.STAND.C002.M004.NET.SSD.B050.G001</serverProductCode>
      <isProtectServerTermination>false</isProtectServerTermination>
      <zoneCode>KR-1</zoneCode>
      <regionCode>KR</regionCode>
      <vpcNo>***04</vpcNo>
      <subnetNo>***43</subnetNo>
      <networkInterfaceNoList>
        <networkInterfaceNo>***87</networkInterfaceNo>
      </networkInterfaceNoList>
      <initScriptNo>***44</initScriptNo>
      <serverInstanceType>
        <code>STAND</code>
        <codeName>Standard</codeName>
      </serverInstanceType>
      <baseBlockStorageDiskType>
        <code>NET</code>
        <codeName>Network Storage</codeName>
      </baseBlockStorageDiskType>
      <baseBlockStorageDiskDetailType>
        <code>SSD</code>
        <codeName>SSD</codeName>
      </baseBlockStorageDiskDetailType>
      <placementGroupNo>***61</placementGroupNo>
      <placementGroupName>test-***</placementGroupName>
    </serverInstance>
  </serverInstanceList>
</interruptServerInstanceResponse>