Cassandra (domU) is not responding as expected

From GigaTux Wiki
Revision as of 13:52, 28 April 2009 by Cocodude (talk | contribs) (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...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Something's gone wrong with the domU and you cannot access emohawk.gigatux.com via SSH.

  1. Try and connect to node00002.gigatux.com via SSH. If this fails, consider following node00001 or node00002 are not responding as expected.
  2. Log in with your username and su to root.
  3. Type xm list to get a list of running domUs. Emohawk is xen01.
  4. 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
  5. Examine the xen01 console by typing xm console xen01
  6. 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.