You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@whirr.apache.org by Frank Scholten <fr...@frankscholten.nl> on 2012/05/09 11:22:32 UTC

Whirr run-script command

Hi all,

I am using the whirr run-script command like this

$ whirr run-script --script path-to-script --roles role

but I am suprised it asks for a 'cluster-name' and an
'instance-templates' option. Is this correct?

Cheers,

Frank

Re: Whirr run-script command

Posted by Frank Scholten <fr...@frankscholten.nl>.

Ah I can use whirr list-cluster command and some Unix scripting to get
the instance id and from there I can
do the ec2-create and ec2-attach.

Using whirr run-script with the actual mount commands still causes
timeouts though.

On Wed, May 9, 2012 at 3:07 PM, Frank Scholten <fr...@frankscholten.nl> wrote:
> Seems like the EBS creation and attachment should be done locally via
> ec2-api-tools but the actual mounting via Whirr on the instance,
> correct?
>
> On Wed, May 9, 2012 at 2:28 PM, Frank Scholten <fr...@frankscholten.nl> wrote:
>> I am creating a script that creates, attaches and mounts EBS volume.
>>
>> On Wed, May 9, 2012 at 1:59 PM, Frank Scholten <fr...@frankscholten.nl> wrote:
>>> I already get timeouts after around 30 seconds, even though I set
>>> jclouds.compute.timeout.script-complete to 1800000 (30 mins)
>>>
>>>
>>> On Wed, May 9, 2012 at 12:36 PM, Andrei Savu <sa...@gmail.com> wrote:
>>>> Are you running long tasks?
>>>>
>>>> See jclouds.compute.timeout.script-complete
>>>>
>>>> https://whirr.apache.org/docs/0.7.1/configuration-guide.html
>>>>
>>>> -- Andrei Savu / axemblr.com / Tools for Clouds
>>>>
>>>>
>>>> On Wed, May 9, 2012 at 1:33 PM, Frank Scholten <fr...@frankscholten.nl>
>>>> wrote:
>>>>>
>>>>> Hmm I am getting SSH timeouts when running a script on a running cluster
>>>>>
>>>>> ]) (out of retries - max 7): Read timed out
>>>>>        at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:417)
>>>>>        at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:238)
>>>>>        at org.jclouds.sshj.SshjSshClient.exec(SshjSshClient.java:499)
>>>>>        at
>>>>> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.runCommand(RunScriptOnNodeUsingSsh.java:113)
>>>>>        at
>>>>> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.call(RunScriptOnNodeUsingSsh.java:86)
>>>>>        at
>>>>> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:69)
>>>>>        at
>>>>> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:44)
>>>>>        at
>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>>        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>>        at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>        at
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>        at java.lang.Thread.run(Thread.java:662)
>>>>> Caused by: net.schmizz.sshj.connection.ConnectionException: Read timed out
>>>>>        at
>>>>> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:32)
>>>>>        at
>>>>> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:26)
>>>>>        at net.schmizz.concurrent.Promise.deliverError(Promise.java:95)
>>>>>        at net.schmizz.concurrent.Event.deliverError(Event.java:72)
>>>>>        at
>>>>> net.schmizz.concurrent.ErrorDeliveryUtil.alertEvents(ErrorDeliveryUtil.java:34)
>>>>>        at
>>>>> net.schmizz.sshj.connection.channel.AbstractChannel.notifyError(AbstractChannel.java:239)
>>>>>
>>>>> On Wed, May 9, 2012 at 11:47 AM, Frank Scholten <fr...@frankscholten.nl>
>>>>> wrote:
>>>>> > Ah of course, forgot to add the config. Thx!
>>>>> >
>>>>> > On Wed, May 9, 2012 at 11:27 AM, Andrei Savu <sa...@gmail.com>
>>>>> > wrote:
>>>>> >> I usually specify the same config file I've used for launch.
>>>>> >>
>>>>> >> $ whirr run-script --script path-to-script --roles role --config ....
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> On Wed, May 9, 2012 at 12:22 PM, Frank Scholten
>>>>> >> <fr...@frankscholten.nl>
>>>>> >> wrote:
>>>>> >>>
>>>>> >>> Hi all,
>>>>> >>>
>>>>> >>> I am using the whirr run-script command like this
>>>>> >>>
>>>>> >>> $ whirr run-script --script path-to-script --roles role
>>>>> >>>
>>>>> >>> but I am suprised it asks for a 'cluster-name' and an
>>>>> >>> 'instance-templates' option. Is this correct?
>>>>> >>>
>>>>> >>> Cheers,
>>>>> >>>
>>>>> >>> Frank
>>>>> >>
>>>>> >>
>>>>
>>>>

Re: Whirr run-script command

Posted by Frank Scholten <fr...@frankscholten.nl>.

Seems like the EBS creation and attachment should be done locally via
ec2-api-tools but the actual mounting via Whirr on the instance,
correct?

On Wed, May 9, 2012 at 2:28 PM, Frank Scholten <fr...@frankscholten.nl> wrote:
> I am creating a script that creates, attaches and mounts EBS volume.
>
> On Wed, May 9, 2012 at 1:59 PM, Frank Scholten <fr...@frankscholten.nl> wrote:
>> I already get timeouts after around 30 seconds, even though I set
>> jclouds.compute.timeout.script-complete to 1800000 (30 mins)
>>
>>
>> On Wed, May 9, 2012 at 12:36 PM, Andrei Savu <sa...@gmail.com> wrote:
>>> Are you running long tasks?
>>>
>>> See jclouds.compute.timeout.script-complete
>>>
>>> https://whirr.apache.org/docs/0.7.1/configuration-guide.html
>>>
>>> -- Andrei Savu / axemblr.com / Tools for Clouds
>>>
>>>
>>> On Wed, May 9, 2012 at 1:33 PM, Frank Scholten <fr...@frankscholten.nl>
>>> wrote:
>>>>
>>>> Hmm I am getting SSH timeouts when running a script on a running cluster
>>>>
>>>> ]) (out of retries - max 7): Read timed out
>>>>        at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:417)
>>>>        at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:238)
>>>>        at org.jclouds.sshj.SshjSshClient.exec(SshjSshClient.java:499)
>>>>        at
>>>> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.runCommand(RunScriptOnNodeUsingSsh.java:113)
>>>>        at
>>>> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.call(RunScriptOnNodeUsingSsh.java:86)
>>>>        at
>>>> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:69)
>>>>        at
>>>> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:44)
>>>>        at
>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>>        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>>        at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>        at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>        at java.lang.Thread.run(Thread.java:662)
>>>> Caused by: net.schmizz.sshj.connection.ConnectionException: Read timed out
>>>>        at
>>>> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:32)
>>>>        at
>>>> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:26)
>>>>        at net.schmizz.concurrent.Promise.deliverError(Promise.java:95)
>>>>        at net.schmizz.concurrent.Event.deliverError(Event.java:72)
>>>>        at
>>>> net.schmizz.concurrent.ErrorDeliveryUtil.alertEvents(ErrorDeliveryUtil.java:34)
>>>>        at
>>>> net.schmizz.sshj.connection.channel.AbstractChannel.notifyError(AbstractChannel.java:239)
>>>>
>>>> On Wed, May 9, 2012 at 11:47 AM, Frank Scholten <fr...@frankscholten.nl>
>>>> wrote:
>>>> > Ah of course, forgot to add the config. Thx!
>>>> >
>>>> > On Wed, May 9, 2012 at 11:27 AM, Andrei Savu <sa...@gmail.com>
>>>> > wrote:
>>>> >> I usually specify the same config file I've used for launch.
>>>> >>
>>>> >> $ whirr run-script --script path-to-script --roles role --config ....
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Wed, May 9, 2012 at 12:22 PM, Frank Scholten
>>>> >> <fr...@frankscholten.nl>
>>>> >> wrote:
>>>> >>>
>>>> >>> Hi all,
>>>> >>>
>>>> >>> I am using the whirr run-script command like this
>>>> >>>
>>>> >>> $ whirr run-script --script path-to-script --roles role
>>>> >>>
>>>> >>> but I am suprised it asks for a 'cluster-name' and an
>>>> >>> 'instance-templates' option. Is this correct?
>>>> >>>
>>>> >>> Cheers,
>>>> >>>
>>>> >>> Frank
>>>> >>
>>>> >>
>>>
>>>

Re: Whirr run-script command

Posted by Frank Scholten <fr...@frankscholten.nl>.

I am creating a script that creates, attaches and mounts EBS volume.

On Wed, May 9, 2012 at 1:59 PM, Frank Scholten <fr...@frankscholten.nl> wrote:
> I already get timeouts after around 30 seconds, even though I set
> jclouds.compute.timeout.script-complete to 1800000 (30 mins)
>
>
> On Wed, May 9, 2012 at 12:36 PM, Andrei Savu <sa...@gmail.com> wrote:
>> Are you running long tasks?
>>
>> See jclouds.compute.timeout.script-complete
>>
>> https://whirr.apache.org/docs/0.7.1/configuration-guide.html
>>
>> -- Andrei Savu / axemblr.com / Tools for Clouds
>>
>>
>> On Wed, May 9, 2012 at 1:33 PM, Frank Scholten <fr...@frankscholten.nl>
>> wrote:
>>>
>>> Hmm I am getting SSH timeouts when running a script on a running cluster
>>>
>>> ]) (out of retries - max 7): Read timed out
>>>        at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:417)
>>>        at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:238)
>>>        at org.jclouds.sshj.SshjSshClient.exec(SshjSshClient.java:499)
>>>        at
>>> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.runCommand(RunScriptOnNodeUsingSsh.java:113)
>>>        at
>>> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.call(RunScriptOnNodeUsingSsh.java:86)
>>>        at
>>> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:69)
>>>        at
>>> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:44)
>>>        at
>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>>        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>>        at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>        at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>        at java.lang.Thread.run(Thread.java:662)
>>> Caused by: net.schmizz.sshj.connection.ConnectionException: Read timed out
>>>        at
>>> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:32)
>>>        at
>>> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:26)
>>>        at net.schmizz.concurrent.Promise.deliverError(Promise.java:95)
>>>        at net.schmizz.concurrent.Event.deliverError(Event.java:72)
>>>        at
>>> net.schmizz.concurrent.ErrorDeliveryUtil.alertEvents(ErrorDeliveryUtil.java:34)
>>>        at
>>> net.schmizz.sshj.connection.channel.AbstractChannel.notifyError(AbstractChannel.java:239)
>>>
>>> On Wed, May 9, 2012 at 11:47 AM, Frank Scholten <fr...@frankscholten.nl>
>>> wrote:
>>> > Ah of course, forgot to add the config. Thx!
>>> >
>>> > On Wed, May 9, 2012 at 11:27 AM, Andrei Savu <sa...@gmail.com>
>>> > wrote:
>>> >> I usually specify the same config file I've used for launch.
>>> >>
>>> >> $ whirr run-script --script path-to-script --roles role --config ....
>>> >>
>>> >>
>>> >>
>>> >> On Wed, May 9, 2012 at 12:22 PM, Frank Scholten
>>> >> <fr...@frankscholten.nl>
>>> >> wrote:
>>> >>>
>>> >>> Hi all,
>>> >>>
>>> >>> I am using the whirr run-script command like this
>>> >>>
>>> >>> $ whirr run-script --script path-to-script --roles role
>>> >>>
>>> >>> but I am suprised it asks for a 'cluster-name' and an
>>> >>> 'instance-templates' option. Is this correct?
>>> >>>
>>> >>> Cheers,
>>> >>>
>>> >>> Frank
>>> >>
>>> >>
>>
>>

Re: Whirr run-script command

Posted by Frank Scholten <fr...@frankscholten.nl>.

I already get timeouts after around 30 seconds, even though I set
jclouds.compute.timeout.script-complete to 1800000 (30 mins)

]) (out of retries - max 7): Read timed out
	at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:417)
	at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:238)
	at org.jclouds.sshj.SshjSshClient.exec(SshjSshClient.java:499)
	at org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.runCommand(RunScriptOnNodeUsingSsh.java:113)
	at org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.call(RunScriptOnNodeUsingSsh.java:86)
	at org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:69)
	at org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:44)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: net.schmizz.sshj.connection.ConnectionException: Read timed out
	at net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:32)
	at net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:26)
	at net.schmizz.concurrent.Promise.deliverError(Promise.java:95)
	at net.schmizz.concurrent.Event.deliverError(Event.java:72)
	at net.schmizz.concurrent.ErrorDeliveryUtil.alertEvents(ErrorDeliveryUtil.java:34)
	at net.schmizz.sshj.connection.channel.AbstractChannel.notifyError(AbstractChannel.java:239)
	at net.schmizz.sshj.connection.channel.direct.SessionChannel.notifyError(SessionChannel.java:249)
	at net.schmizz.sshj.common.ErrorNotifiable$Util.alertAll(ErrorNotifiable.java:35)
	at net.schmizz.sshj.connection.ConnectionImpl.notifyError(ConnectionImpl.java:250)
	at net.schmizz.sshj.transport.TransportImpl.die(TransportImpl.java:578)
	at net.schmizz.sshj.transport.Reader.run(Reader.java:79)
Caused by: net.schmizz.sshj.common.SSHException: Read timed out
	at net.schmizz.sshj.common.SSHException$1.chain(SSHException.java:56)
	at net.schmizz.sshj.common.SSHException$1.chain(SSHException.java:49)
	at net.schmizz.sshj.transport.TransportImpl.die(TransportImpl.java:572)
	... 1 more
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:129)
	at net.schmizz.sshj.transport.Reader.run(Reader.java:68)

On Wed, May 9, 2012 at 12:36 PM, Andrei Savu <sa...@gmail.com> wrote:
> Are you running long tasks?
>
> See jclouds.compute.timeout.script-complete
>
> https://whirr.apache.org/docs/0.7.1/configuration-guide.html
>
> -- Andrei Savu / axemblr.com / Tools for Clouds
>
>
> On Wed, May 9, 2012 at 1:33 PM, Frank Scholten <fr...@frankscholten.nl>
> wrote:
>>
>> Hmm I am getting SSH timeouts when running a script on a running cluster
>>
>> ]) (out of retries - max 7): Read timed out
>>        at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:417)
>>        at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:238)
>>        at org.jclouds.sshj.SshjSshClient.exec(SshjSshClient.java:499)
>>        at
>> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.runCommand(RunScriptOnNodeUsingSsh.java:113)
>>        at
>> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.call(RunScriptOnNodeUsingSsh.java:86)
>>        at
>> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:69)
>>        at
>> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:44)
>>        at
>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>        at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>        at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>        at java.lang.Thread.run(Thread.java:662)
>> Caused by: net.schmizz.sshj.connection.ConnectionException: Read timed out
>>        at
>> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:32)
>>        at
>> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:26)
>>        at net.schmizz.concurrent.Promise.deliverError(Promise.java:95)
>>        at net.schmizz.concurrent.Event.deliverError(Event.java:72)
>>        at
>> net.schmizz.concurrent.ErrorDeliveryUtil.alertEvents(ErrorDeliveryUtil.java:34)
>>        at
>> net.schmizz.sshj.connection.channel.AbstractChannel.notifyError(AbstractChannel.java:239)
>>
>> On Wed, May 9, 2012 at 11:47 AM, Frank Scholten <fr...@frankscholten.nl>
>> wrote:
>> > Ah of course, forgot to add the config. Thx!
>> >
>> > On Wed, May 9, 2012 at 11:27 AM, Andrei Savu <sa...@gmail.com>
>> > wrote:
>> >> I usually specify the same config file I've used for launch.
>> >>
>> >> $ whirr run-script --script path-to-script --roles role --config ....
>> >>
>> >>
>> >>
>> >> On Wed, May 9, 2012 at 12:22 PM, Frank Scholten
>> >> <fr...@frankscholten.nl>
>> >> wrote:
>> >>>
>> >>> Hi all,
>> >>>
>> >>> I am using the whirr run-script command like this
>> >>>
>> >>> $ whirr run-script --script path-to-script --roles role
>> >>>
>> >>> but I am suprised it asks for a 'cluster-name' and an
>> >>> 'instance-templates' option. Is this correct?
>> >>>
>> >>> Cheers,
>> >>>
>> >>> Frank
>> >>
>> >>
>
>

Re: Whirr run-script command

Posted by Andrei Savu <sa...@gmail.com>.

Are you running long tasks?

See jclouds.compute.timeout.script-complete

https://whirr.apache.org/docs/0.7.1/configuration-guide.html

-- Andrei Savu / axemblr.com / Tools for Clouds

On Wed, May 9, 2012 at 1:33 PM, Frank Scholten <fr...@frankscholten.nl>wrote:

> Hmm I am getting SSH timeouts when running a script on a running cluster
>
> ]) (out of retries - max 7): Read timed out
>        at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:417)
>        at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:238)
>        at org.jclouds.sshj.SshjSshClient.exec(SshjSshClient.java:499)
>        at
> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.runCommand(RunScriptOnNodeUsingSsh.java:113)
>        at
> org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.call(RunScriptOnNodeUsingSsh.java:86)
>        at
> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:69)
>        at
> org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:44)
>        at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>        at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>        at java.lang.Thread.run(Thread.java:662)
> Caused by: net.schmizz.sshj.connection.ConnectionException: Read timed out
>        at
> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:32)
>        at
> net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:26)
>        at net.schmizz.concurrent.Promise.deliverError(Promise.java:95)
>        at net.schmizz.concurrent.Event.deliverError(Event.java:72)
>        at
> net.schmizz.concurrent.ErrorDeliveryUtil.alertEvents(ErrorDeliveryUtil.java:34)
>        at
> net.schmizz.sshj.connection.channel.AbstractChannel.notifyError(AbstractChannel.java:239)
>
> On Wed, May 9, 2012 at 11:47 AM, Frank Scholten <fr...@frankscholten.nl>
> wrote:
> > Ah of course, forgot to add the config. Thx!
> >
> > On Wed, May 9, 2012 at 11:27 AM, Andrei Savu <sa...@gmail.com>
> wrote:
> >> I usually specify the same config file I've used for launch.
> >>
> >> $ whirr run-script --script path-to-script --roles role --config ....
> >>
> >>
> >>
> >> On Wed, May 9, 2012 at 12:22 PM, Frank Scholten <frank@frankscholten.nl
> >
> >> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I am using the whirr run-script command like this
> >>>
> >>> $ whirr run-script --script path-to-script --roles role
> >>>
> >>> but I am suprised it asks for a 'cluster-name' and an
> >>> 'instance-templates' option. Is this correct?
> >>>
> >>> Cheers,
> >>>
> >>> Frank
> >>
> >>
>

Re: Whirr run-script command

Posted by Frank Scholten <fr...@frankscholten.nl>.

Hmm I am getting SSH timeouts when running a script on a running cluster

]) (out of retries - max 7): Read timed out
	at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:417)
	at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:238)
	at org.jclouds.sshj.SshjSshClient.exec(SshjSshClient.java:499)
	at org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.runCommand(RunScriptOnNodeUsingSsh.java:113)
	at org.jclouds.compute.callables.RunScriptOnNodeUsingSsh.call(RunScriptOnNodeUsingSsh.java:86)
	at org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:69)
	at org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:44)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: net.schmizz.sshj.connection.ConnectionException: Read timed out
	at net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:32)
	at net.schmizz.sshj.connection.ConnectionException$1.chain(ConnectionException.java:26)
	at net.schmizz.concurrent.Promise.deliverError(Promise.java:95)
	at net.schmizz.concurrent.Event.deliverError(Event.java:72)
	at net.schmizz.concurrent.ErrorDeliveryUtil.alertEvents(ErrorDeliveryUtil.java:34)
	at net.schmizz.sshj.connection.channel.AbstractChannel.notifyError(AbstractChannel.java:239)

On Wed, May 9, 2012 at 11:47 AM, Frank Scholten <fr...@frankscholten.nl> wrote:
> Ah of course, forgot to add the config. Thx!
>
> On Wed, May 9, 2012 at 11:27 AM, Andrei Savu <sa...@gmail.com> wrote:
>> I usually specify the same config file I've used for launch.
>>
>> $ whirr run-script --script path-to-script --roles role --config ....
>>
>>
>>
>> On Wed, May 9, 2012 at 12:22 PM, Frank Scholten <fr...@frankscholten.nl>
>> wrote:
>>>
>>> Hi all,
>>>
>>> I am using the whirr run-script command like this
>>>
>>> $ whirr run-script --script path-to-script --roles role
>>>
>>> but I am suprised it asks for a 'cluster-name' and an
>>> 'instance-templates' option. Is this correct?
>>>
>>> Cheers,
>>>
>>> Frank
>>
>>

Re: Whirr run-script command

Posted by Frank Scholten <fr...@frankscholten.nl>.

Ah of course, forgot to add the config. Thx!

On Wed, May 9, 2012 at 11:27 AM, Andrei Savu <sa...@gmail.com> wrote:
> I usually specify the same config file I've used for launch.
>
> $ whirr run-script --script path-to-script --roles role --config ....
>
>
>
> On Wed, May 9, 2012 at 12:22 PM, Frank Scholten <fr...@frankscholten.nl>
> wrote:
>>
>> Hi all,
>>
>> I am using the whirr run-script command like this
>>
>> $ whirr run-script --script path-to-script --roles role
>>
>> but I am suprised it asks for a 'cluster-name' and an
>> 'instance-templates' option. Is this correct?
>>
>> Cheers,
>>
>> Frank
>
>

Re: Whirr run-script command

Posted by Andrei Savu <sa...@gmail.com>.

I usually specify the same config file I've used for launch.

$ whirr run-script --script path-to-script --roles role --config ....

On Wed, May 9, 2012 at 12:22 PM, Frank Scholten <fr...@frankscholten.nl>wrote:

> Hi all,
>
> I am using the whirr run-script command like this
>
> $ whirr run-script --script path-to-script --roles role
>
> but I am suprised it asks for a 'cluster-name' and an
> 'instance-templates' option. Is this correct?
>
> Cheers,
>
> Frank
>