Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Tried booting through the aws dashboard.

Also tried creating from the command line api tools.

Checked ssh with -vvv and made sure it was trying the key (note that an old instance with the same key is accessible)...

Checked the system log on AWS console (never seems to finish (stuck on keygen for the host) - despite waiting approx. 60m).

System log last line: ec2: -----END SSH HOST KEY FINGERPRINTS----- ec2: #############################################################

System log also contains errors (however I'm led to believe that the error is irrelevant):

init: console-setup main process (63) terminated with status 1


    %Ginit: plymouth-splash main process (228) terminated with status 2

init: plymouth main process (45) killed by SEGV signal
share|improve this question
    
Are you using the same AMI for both instances? –  Rob Olmos Dec 7 '10 at 19:05
    
@rob: nope, I haven't tried that using ami-a403f7cd for the new one. –  waldo Dec 8 '10 at 12:49

1 Answer 1

up vote 0 down vote accepted

I've experienced this problem a couple of different times because I messed something up in /etc/fstab that was causing problems on boot (referring to an EBS volume that wasn't mounted, usually). It seems like other people have had the same misdiagnosed plymouth problem that masked an fstab snafu.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.