(mt):Reboot server

  • This page was last modified on February 18, 2011, at 17:43.
The (mt) Community Wiki is a collaborative project. Any (mt) Media Temple customer or employee may contribute. Not all articles and/or content have been tested for accuracy by (mt) Media Temple.

For officially moderated and tested articles, be sure to visit our KnowledgeBase.

From (mt) Community Wiki

Contents

This method provides a way to reboot the server for a specific (mt) Media Temple service that is associated with the authenticated account.

Request Info

The following URL and HTTP method should be used:

HTTP Method URL
POSThttps://api.mediatemple.net/api/v1/services/{serviceId}/reboot

The following parameters must be provided in the URL:

Parameter Type Description
serviceIdintThe service id

Response Info

The response will return an HTTP status code to indicate the general category of success or failure to the client. More specific error codes and messages will be contained in the response data itself, if provided. For more information on response codes and parsing response data, see Parsing API responses.

Sample Request

To get a list of services in JSON format, do the following:

curl -D log.txt -s -X "POST" "https://api.mediatemple.net/api/v1/services/556/reboot.json?apikey=a5h34sf62..."

Sample Response

Here is an example of the returned result:

{
"response" : {
"statusCode" : 202,
"timeStamp" : 1284609174311,
"date" : "2010-09-16T03:52:54.311+0000",
"errors" : [ ],
"custom" : [ ]
}
}

Sample Operation Pending

If another set reboot operation is already pending (e.g. the above request is called a second time before the reboot job has completed), then you can expect a response like the following:

{
"response" : {
"statusCode" : 409,
"timeStamp" : 1284609198593,
"date" : "2010-09-16T03:53:18.593+0000",
"errors" : [ {
"errorCode" : "OperationPending",
"message" : "An existing operation that conflicts is currently pending.  This operation cannot be scheduled until it completes."
} ],
"custom" : [ ]
}
}

Response Fields

All responses should be in the standard response format. For more information, see Parsing API responses.

Response Errors

Status Code Error Code Error Description
404InvalidServiceThe specified serviceId was invalid
409OperationPendingThere is an existing operation that has not completed.
500UnknownErrorThere was an unexpected error.