Amazon EC2 instance dies on installing Java

[jbr...@snapapp.com]

Hi all,

I'm using the Amazon EC2 plugin to create new agents. I've set it up to use the Ubuntu 16.04 AMI. Security groups, availability zones, and remote user (ubuntu) are all correct. The EC2 key pair is correct and successfully connects on testing. I specified that the root prefix should be `sudo`. However, when I attempt to provision a new node, I get the following:

INFO: Connecting to xxx.xxx.xxx.xxx on port 22, with timeout 10000.
Dec 05, 2016 9:36:57 PM null
INFO: Connected via SSH.
Dec 05, 2016 9:36:57 PM null
INFO: Creating tmp directory (/tmp) if it does not exist
Dec 05, 2016 9:36:57 PM null
INFO: Verifying that java exists
bash: java: command not found
Dec 05, 2016 9:36:57 PM null
INFO: Installing Java
failed: Connection timed out.
failed: Connection timed out.

What am I getting wrong here?

Thanks!

Jack

[Victor Martinez]

Hi Jack,

Although I'm not really familiar with this plugin, I'd recommend you to look at:

- https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin

There is a section about some timeouts and extending the time with some 

And also see whether those timeout issues references are in any jira ticket:

- https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20%27ec2-plugin%27

Besides of that, if you still get the same issues, then it's time to add some verbose output with the log recorders:

- https://wiki.jenkins-ci.org/display/JENKINS/Logging

In that case you need to use those loggers from the source code:

- https://github.com/jenkinsci/ec2-plugin/search?utf8=%E2%9C%93&q=log&type=Code

Hope it helps

Cheers