[
https://issues.apache.org/jira/browse/WHIRR-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134180#comment-13134180
]
Adrian Cole commented on WHIRR-400:
-----------------------------------
There's a socket timeout at the root of the below stacktrace. I'd change the
logging configuration used to trace the category "jclouds.ssh" and see what's
happening. When this occurs, you can look in jclouds-wire.log to see the ssh
key used and log in with it (where sha1 = keyFingerprint).
I can't troubleshoot further, but hope this helps.
Caused by: java.util.concurrent.ExecutionException:
org.jclouds.ssh.SshException:
(ubuntu:rsa[fingerprint(a7:e8:d8:8b:aa:36:e8:c0:ea:07:ba:b6:c1:44:3c:ab),
sha1(5a:fe:9e:d5:64:52:b3:b0:d9:b9:72:5a:cc:92:04:6a:e1:0a:ec:0f)]@107.22.55.221:22)
(ubuntu:rsa[fingerprint(a7:e8:d8:8b:aa:36:e8:c0:ea:07:ba:b6:c1:44:3c:a
b),sha1(5a:fe:9e:d5:64:52:b3:b0:d9:b9:72:5a:cc:92:04:6a:e1:0a:ec:0f)]@107.22.55.221:22)
error acquiring ExecResponse(command=[./setup-adriancole status]):
Read timed out
at
com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:328)
at
com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:301)
at
com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:93)
at
org.jclouds.compute.callables.BlockUntilInitScriptStatusIsZeroThenReturnOutput.get(BlockUntilInitScriptStatusIsZeroThenReturnOutput.java:190)
at
org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.doCall(RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.java:60)
... 8 more
> Upgrade to jclouds 1.2.1
> ------------------------
>
> Key: WHIRR-400
> URL: https://issues.apache.org/jira/browse/WHIRR-400
> Project: Whirr
> Issue Type: Improvement
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.7.0
>
> Attachments: WHIRR-400.patch, WHIRR-400.patch, WHIRR-400.patch
>
>
> Jclouds 1.2.1 was released today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
