ssh daemon hangs after publickey packet sent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
openssh (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
A launched ec2 instance in ap-southeast-1 region is unreachable via ssh.
$ ssh -vvv ec2-175-
shows progress up to :
debug3: authmethod_
debug1: Next authentication method: publickey
debug1: Offering public key: smoser@brickies
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
Then nothing for minutes before session is killed (manually).
In a 'good' connection, the following would be next:
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
I'll attach full 'ssh -vvv' logs good and bad connection.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: openssh-server 1:5.5p1-4ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-14-virtual x86_64
Architecture: amd64
Date: Tue Aug 3 14:45:25 2010
Ec2AMI: ami-9fc4bbcd
Ec2AMIManifest: ubuntu-
Ec2Availability
Ec2InstanceType: m1.large
Ec2Kernel: aki-11d5aa43
Ec2Ramdisk: unavailable
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: openssh
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → Medium |
Changed in openssh (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: iso-testing |
tags: | added: review-request |
Changed in linux (Ubuntu): | |
importance: | Medium → Undecided |
status: | New → Invalid |
Changed in openssh (Ubuntu): | |
status: | New → Confirmed |
Other information:
ssh-keyscan did show results:
# ec2-175- 41-171- 225.ap- southeast- 1.compute. amazonaws. com SSH-2.0- OpenSSH_ 5.5p1 Debian-4ubuntu3 41-171- 225.ap- southeast- 1.compute. amazonaws. com ssh-rsa AAAAB3NzaC1y. ..RzIcF9UuISZaY Jf
ec2-175-
A reboot-instances seems to have no affect.
What is strange here is that there was a key in ssh-keyscan, yet the console shows no key-gen output. This is likely related to the fact that the instance would not reboot.
I suspect kernel problem.