On Apr 05, 2011, at 15:07, Ted Ts'o wrote: > On Tue, Apr 05, 2011 at 10:30:11AM -0500, Moffett, Kyle D wrote: >> Well, the base image is essentially a somewhat basic Debian "squeeze" >> for EC2 with our SSH public keys and a couple generic customizations >> applied. It does not have Postfix installed or configured, so there >> would be some work involved. > > Well, if you can share that image in AWS with the ssh keys stripped > out it would save me a bunch of time. I assume it's not setup to > automatically set ssh keys and pass them back to AWS like the generic > images can?
Well, the generic images just download to ~root/.ssh/authorized_keys from http://169.254.169.254/meta-data/public-keys/0/openssh-key They don't really "generate" a keypair themselves, that's just what AWS does and provides the pubkey via that URL. The 169.254.169.254 is just the link-local address for some virtualization infrastructure software. These days they even let you upload your own pubkey. Unfortunately our images don't do that download, although the patched D-I image does do that when initially setting up the network console. If you send me an SSH key and AWS account number in private email then I will cook an updated image and share it out to you. >> I also didn't see any problems with the system at all until the >> queue got backed up with ~100-120 stuck emails. After Postfix tried >> and failed to deliver a bunch of emails I would get the OOPS. > > Yeah, what I'd probably try to do is install postfix and then send a > few hundred messages to foo...@example.com and see if I can repro the OOPS. Not sure if it's related, but the particular SMTP error that was causing things to back up in the first place was by the remote server rejecting emails via SMTP errors after a *successful* connection. > Thanks for investigating! Thanks for debugging! Cheers, Kyle Moffett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
