Cassandra (domU) is not responding as expected - Revision history

Astropoint at 13:53, 3 August 2013

2013-08-03T13:53:18Z

← Older revision		Revision as of 13:53, 3 August 2013
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 ~~node00002~~.gigatux.com via SSH. If this fails, consider following [[node00001 or node00002 are not responding as expected]].		# 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.

Cocodude: moved Emohawk (domU) is not responding as expected to Cassandra (domU) is not responding as expected

2010-11-29T17:07:08Z

moved Emohawk (domU) is not responding as expected to Cassandra (domU) is not responding as expected

← Older revision	Revision as of 17:07, 29 November 2010
(No difference)

Cocodude at 16:04, 24 March 2010

2010-03-24T16:04:47Z

← Older revision		Revision as of 16:04, 24 March 2010
Line 5:		Line 5:
	# 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.

Cocodude: 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...'

2009-04-28T13:52:26Z

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...'

New page

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 [[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''
# 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.