Strange error launching custom AMI
Paolo Di Tommaso
Adrian Cole
This isn't an issue launching, rather one sshing in. When you launch manually, what user do you connect with? What ami or base ami is this made from.
-A
--
You received this message because you are subscribed to the Google Groups "jclouds" group.
To view this discussion on the web visit https://groups.google.com/d/msg/jclouds/-/PZYhAqlXdGcJ.
To post to this group, send email to jcl...@googlegroups.com.
To unsubscribe from this group, send email to jclouds+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jclouds?hl=en.
Aled Sage
The symptoms sound very similar to those reported in [1].
There, we fixed sshj to report the more helpful "Invalid packet: indicated length %d too large", rather than going into an infinite loop.
Could the underlying cause for you be related to what Alex thought:
The log message was:I think I am using the wrong credentials, based on a log message, but I
think the credentials is confusing so maybe that could be cleaned up.
Received SSH_MSG_DEBUG (display=false) 'Forced command: echo 'Please login as the ubuntu user rather than root user.';echo;sleep 10'
Aled
[1] https://groups.google.com/group/jclouds-dev/browse_thread/thread/c17d71019c7fc932/a3a990bb7c271efd?lnk=gst&q=sshj+hangs#a3a990bb7c271efd
[2] https://gist.github.com/2489273
Aled Sage
My guess is that's the underlying cause.
Aled
Paolo Di Tommaso
Adrian Cole
Inline
On May 19, 2012 4:36 PM, "Paolo Di Tommaso" <paolo.d...@gmail.com> wrote:
>
> Hi guys,
>
> Thanks for your feedbac. I'm also thinking that something related to wrong credentials, but also there should be something broken in my workflow.
>
> I'm trying to create a custom AMI starting from a Amazon Linux AMI. What I do is the following:
>
> 1) Launch the Amazon Linux AMI from AWS dashboard using the default settings
> 2) Log in to the instance using the Amazon provided key and install sw packages
> 3) Create a new AMI with the ec2-create-image command
> 4) When the AMI is ready I try to launch it with JClouds using my own key-pair and user-name. I use this code:
>
> AdminAccess admin = new AdminAccess.Builder()
> .adminUsername( conf.userName )
> .adminPublicKey( conf.publicKeyFile )
> .adminPrivateKey( conf.privateKeyFile )
> .build()
> templateOptions.runScript(admin)
>
>
> After that I get the Invalid packet: indicated length 1349281121 too large exception.
Ok. AdminAccess is about the user to install once the vm is booted. Jclouds needs to login in order to create this user. Jclouds has parsers to decide the name of the login user for some common amis. This is by convention as EC2 exposes no API about the login name of a particular image. For custom amis, jclouds will have no idea what the login user should be, and blindly attempts with root. If you are using a custom ami which doesn't allow root login, you need to specify the login user and likely also the private key you installed.
This would be the TemplateOption overrideLoginCredentials
Again AdminAcess is to install a user overrideLoginCredentials is to specify one.
Paolo Di Tommaso
Paolo
Adrian Cole
We generate a temporary key.. that's the secret ingredient ;)
We are missing an example of using our image extension to cover the use case you are doing. Ill try to nudge that along this week.