rebootServerInstances

Prev Next

Overview

Restart a server instance (VM).

Request

Request parameters

Parameter name Required Type Restrictions Description
serverInstanceNoList.N Yes List<String> It can't be duplicated. - List of the server instance numbers to be restarted
Servers that are stopped can't be restarted.
serverInstanceNo can be obtained through the getServerInstanceList action.
e.g., serverInstanceNoList.1=937507&serverInstanceNoList.2=1021003
responseFormatType No String - Response result's format type
Options: xml | json
Default: xml

Response

Response body

Examples

Request example

GET {SERVER_API_URL}/rebootServerInstances
?serverInstanceNoList.1=937507

Response example

<rebootServerInstancesResponse>
  <requestId>ee5ec8d8-a700-4d5e-a2de-d59c90fb0d61</requestId>
  <returnCode>0</returnCode>
  <returnMessage>success</returnMessage>
  <totalRows>1</totalRows>
  <serverInstanceList>
    <serverInstance>
      <serverInstanceNo>937507</serverInstanceNo>
      <serverName>s165d2104110</serverName>
      <serverDescription></serverDescription>
      <cpuCount>1</cpuCount>
      <memorySize>2147483648</memorySize>
      <baseBlockStorageSize>53687091200</baseBlockStorageSize>
      <platformType>
        <code>LNX64</code>
        <codeName>Linux 64 Bit</codeName>
      </platformType>
      <loginKeyName>juhoonkim</loginKeyName>
      <isFeeChargingMonitoring>false</isFeeChargingMonitoring>
      <publicIp></publicIp>
      <privateIp>10.41.0.56</privateIp>
      <serverImageName>centos-6.6-64</serverImageName>
      <serverInstanceStatus>
        <code>RUN</code>
        <codeName>Server run state</codeName>
      </serverInstanceStatus>
      <serverInstanceOperation>
        <code>RESTA</code>
        <codeName>Server RESTART OP</codeName>
      </serverInstanceOperation>
      <serverInstanceStatusName>rebooting</serverInstanceStatusName>
      <createDate>2018-09-13T17:33:26+0900</createDate>
      <uptime>2018-11-23T17:32:23+0900</uptime>
      <serverImageProductCode>SPSW0LINUX000044</serverImageProductCode>
      <serverProductCode>SPSVRSTAND000003</serverProductCode>
      <isProtectServerTermination>false</isProtectServerTermination>
      <portForwardingPublicIp>106.10.51.90</portForwardingPublicIp>
      <zone>
        <zoneNo>3</zoneNo>
        <zoneName>KR-2</zoneName>
        <zoneCode>KR-2</zoneCode>
        <zoneDescription>Pyeongchon zone</zoneDescription>
        <regionNo>1</regionNo>
      </zone>
      <region>
        <regionNo>1</regionNo>
        <regionCode>KR</regionCode>
        <regionName>Korea</regionName>
      </region>
      <baseBlockStorageDiskType>
        <code>NET</code>
        <codeName>Network Storage</codeName>
      </baseBlockStorageDiskType>
      <baseBlockStorageDiskDetailType>
        <code>HDD</code>
        <codeName>HDD</codeName>
      </baseBlockStorageDiskDetailType>
      <serverInstanceType>
        <code>COMPT</code>
        <codeName>Compact Server</codeName>
      </serverInstanceType>
      <userData></userData>
      <initScriptNo></initScriptNo>
      <accessControlGroupList>
        <accessControlGroup>
          <accessControlGroupConfigurationNo>39995</accessControlGroupConfigurationNo>
          <accessControlGroupName>ncloud-default-acg</accessControlGroupName>
          <accessControlGroupDescription>Default AccessControlGroup</accessControlGroupDescription>
          <isDefault>true</isDefault>
          <createDate>2018-04-09T11:12:54+0900</createDate>
        </accessControlGroup>
      </accessControlGroupList>
      <instanceTagList/>
    </serverInstance>
  </serverInstanceList>
</rebootServerInstancesResponse>

Errors

Errors that may occur while using this action are listed below. For more information about common errors, see NAVER Cloud Platform API.

HTTP Response Code Return code Return message
400 22001 {1} among {0} servers failed for operation. The problem is being handle* Please hold for a moment.
400 24109 The input parameter instance number is invalid..
400 24120 The input parameter server instance number is invalid.
400 25014 Unable to control the server since (other) user is currently operating storage allocated to the server.
400 25041 Unable to perform operation command since (other) user is either manipulating the target server or a problem in target server. Please confirm server status once again.
400 28004 Unable to perform restart command since target server is already suspended. (Other) user might have suspended the server by connecting through terminal. Please confirm the server status once again.