Cassandra (domU) is not responding as expected: Difference between revisions
Jump to navigation
Jump to search
Created page with 'Something's gone wrong with the domU and you cannot access emohawk.gigatux.com via SSH. # Try and connect to node00002.gigatux.com via SSH. If this fails, consider following [[n...' |
Astropoint (talk | contribs) mNo edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
Something's gone wrong with the domU and you cannot access emohawk.gigatux.com via SSH. | Something's gone wrong with the domU and you cannot access emohawk.gigatux.com via SSH. | ||
# Try and connect to | # Try and connect to node00004.gigatux.com via SSH. If this fails, consider following [[node00001 or node00002 are not responding as expected]]. | ||
# Log in with your username and ''su'' to root. | # Log in with your username and ''su'' to root. | ||
# Type ''xm list'' to get a list of running domUs. Emohawk is xen01. | # Type ''xm list'' to get a list of running domUs. Emohawk is xen01. | ||
# If xen01's state is 'r' or 'b', all is expected. If it is 's', it is in a shutdown state and you will need to ''xm destroy'' it and restart it by typing ''xm create /etc/xen/xen01'' | # If xen01's state is 'r' or 'b', all is expected. If it is 's', it is in a shutdown state and you will need to ''xm destroy'' it and restart it by typing ''xm create /etc/xen/xen01'' | ||
# Examine the xen01 console by typing ''xm console xen01'' | # Examine the xen01 console by typing ''xm console xen01''. Press return and you should see a login prompt. If you don't after a few seconds, it is likely something is wrong and the VPS might have crashed. | ||
# Try and figure things out from there :) The Xen commands you can use from the domU are: | # Try and figure things out from there :) The Xen commands you can use from the domU are: | ||
#:* ''xm list'' - List domUs. | #:* ''xm list'' - List domUs. | ||
Latest revision as of 13:53, 3 August 2013
Something's gone wrong with the domU and you cannot access emohawk.gigatux.com via SSH.
- Try and connect to node00004.gigatux.com via SSH. If this fails, consider following node00001 or node00002 are not responding as expected.
- Log in with your username and su to root.
- Type xm list to get a list of running domUs. Emohawk is xen01.
- If xen01's state is 'r' or 'b', all is expected. If it is 's', it is in a shutdown state and you will need to xm destroy it and restart it by typing xm create /etc/xen/xen01
- Examine the xen01 console by typing xm console xen01. Press return and you should see a login prompt. If you don't after a few seconds, it is likely something is wrong and the VPS might have crashed.
- Try and figure things out from there :) The Xen commands you can use from the domU are:
- xm list - List domUs.
- xm create /etc/xen/xenXY - Start up domU XY.
- xm shutdown xenXY - Shut down domU XY. Note that may not fully remove the domU, so examine the console and if things are not disappearing, issue a destroy command.
- xm destroy xenXY - Forcibly shut down domU XY.
- xm console xenXY - Examine the console of domU XY. Type Ctrl-D or Ctrl-] to exit.