Home > FAQs > Why is my server "stranded in booting" when I reboot the instance?

Copyright (c) 2006-2014 MindTouch Inc.

This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).

At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.

A complete copy of the MSA is available at http://www.mindtouch.com/msa

Why is my server "stranded in booting" when I reboot the instance?

Table of Contents
Background Information

When you reboot the instance, the server is left in the "stranded in booting" state.



RightScale generally does not recommend rebooting a server. Typically, if a server is in an error state that requires a reboot, this is a good indicator that the instance has become unstable. In such cases, it is better to launch a new instance instead of trying to reboot and troubleshoot a problematic server. However, a reboot can be useful for troubleshooting and testing purposes.

When you reboot a server, the boot scripts will be run again.  See the Server States diagram to understand what happens on the instance during each server state.

There are a few scripts that are not "reboot safe." The best way to determine whether or not a script is reboot safe, is to reboot the server and see if the server has a problem running its boot scripts and becoming fully operational. For example, if you reboot a server and the boot scripts are run a second time (during a reboot and not a first-time server launch), you receive an error and the server immediately stops executing scripts and displays a "stranded" status. In such cases, one or more of your boot scripts is not reboot safe. You will have to disable the script prior to rebooting the server, by selecting the Scripts tab for the "Next" server and deselecting that boot script.

Note: If you've already successfully rebooted the server and it is stranded, you can also force the "stranded" server to become operational.

See also

You must to post a comment.
Last modified
21:25, 16 May 2013



This page has no classifications.



Glossary | 用語용어 Site Map | Site Help Community Corporate Site Get Support Dashboard Login
Doc Feedback Product Feedback Resources MultiCloud Marketplace Forums

Dashboard Status

© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.