Re: [Xen-users] Amazon EC2+Slackware 14(64 bit)

["Geetha, ANGLER - EIT" <geetha@xxxxxxxxxxxxxxx>]

Ian,

Please find the attachment of console output.


root@slack64:~/us-east# ssh -i sg_mykey -v
ec2-23-20-223-66.compute-1.amazonaws.com
OpenSSH_5.5p1, OpenSSL 0.9.8n 24 Mar 2010
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to ec2-23-20-223-66.compute-1.amazonaws.com
[23.20.223.66] port 22.
debug1: connect to address 23.20.223.66 port 22: Connection timed out
ssh: connect to host ec2-23-20-223-66.compute-1.amazonaws.com port 22:
Connection timed out 

Regards,
SG

-----Original Message-----
From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx] 
Sent: Monday, July 01, 2013 6:37 PM
To: Geetha, ANGLER - EIT
Cc: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] Amazon EC2+Slackware 14(64 bit)

On Mon, 2013-07-01 at 18:27 +0530, Geetha, ANGLER - EIT wrote:
> On Mon, 2013-07-01 at 18:07 +0530, Geetha, ANGLER - EIT wrote:
> > Ian,
> > 
> > 
> > Thanks for your suggestion.
> > 
> > Actually I am got the below error as I changed xvda to xvde console
> > 
> > Ref url:
> > 
> >
> http://serverfault.com/questions/337695/reboot-fails-on-rhel-6-1-after
> -kernel-update-on-amazon-ec2

That seems to deal with RHEL. I expect it has nothing to do with your issue.
At least I can't see any correlation based upon the limited info you have
given.

> > 
> > Error:
> > 
> > Please stand by while rebooting the system...
> > md: stopping all md devices.
> > xenbus_dev_shutdown: device/console/0: Initialising != Connected,
> skipping
> > Restarting system.
> > 
> > 
> > > getting the below error,
> > > 
> > > 
> > > xenbus_dev_shutdown: device/console/0: Initialising != Connected, 
> > > skipping
> > > [   78.890483] Restarting system.
> > 
> > No errors here, just a warning.
> > 
> > but I could not login to my instance Ian.. 

Well, it's rebooted, so of course not.

Are you saying that it reboots automatically every time you start it? If so
then I think you need to provide complete logs of the guest boot, since what
you have provided only covers the consequences of the issue, not the actual
issue.

This highlights the importance of explaining fully and clearly the behaviour
you are seeing when reporting an issue.

Ian.

Attachment: get_console_output.txt
Description: Text document

Attachment: slackware14_document.rtf
Description: MS-Word document

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users