[Swift-devel] command line ssh provider...

[Jonathan Monette]

I am assuming that I have to get the sshcl provider to fail again for the stdout/stderr to be recorded?  I typed the correct password in and this is what showed up:

2-01-17 11:25:16,375-0600 DEBUG JobSubmissionTaskHandler Job: 
	executable: /bin/bash
	arguments:  /home/jonmon/Workspace/Swift/swift.workdir/hostname-20120117-1125-ora1c4k1/shared/_swiftwrap hostname-km209rlk -jobdir k -scratch  -e /bin/hostname -out hostname.txt -err stderr.txt -i -d  -if  -of hostname.txt -k  -cdmfile  -status provider -a
	stdout:     null
	stderr:     null
	directory:  /home/jonmon/Workspace/Swift/swift.workdir/hostname-20120117-1125-ora1c4k1
	batch:      false
	redirected: false
	attributes: null
	env:        SWIFT_GEN_SCRIPTS=1

This is what shows up in ps:
jonmon   19162  0.0  0.0  59456  3344 pts/0    S+   11:25   0:00 ssh -v bridled.ci.uchicago.edu /bin/bash -s

so -v is being used in the ssh command but Swift isn't recording the output.

I have also tried entering in the wrong password but Swift just keeps asking for the password until I type the correct one in.

I see in the JobSubmissionTaskHandler file there is a way to specify a username.  In the sites file I use the line: <execution provider="ssh-cl" username="jonmon" url="bridled.ci.uchicago.edu"/>

but the username is not used, I do not see the -l in the command line of the sshcl provider.  I wanted to try providing a username to the ssh command to see if that some how made it realize to use the agent set up for the user jonmon.


On Jan 16, 2012, at 9:31 PM, Jonathan Monette wrote:

> I will give that a try to see if that sheds light on why the agent is not being used.
> 
> On Jan 16, 2012, at 9:29 PM, Mihael Hategan wrote:
> 
>> Hmm.
>> 
>> I added logging of stdout/stderr in the local provider when the job
>> fails. You may need to enable DEBUG in log4j.properties on
>> org.globus.cog.abstraction.impl.execution.local.JobSubmissionTaskHandler.
>> 
>> Mihael
>> 
>> On Mon, 2012-01-16 at 15:24 -0600, Jonathan Monette wrote:
>>> So. I started a Swift run and when it was waiting for me to type in a password I opened another terminal and kill what looked like the process that was connecting to bridled.  Swift just started a new process.  I then kill -9 the process and this time Swift crashed.  Still no ssh debug messages appear in the logs.
>>> On Jan 16, 2012, at 1:16 PM, Mihael Hategan wrote:
>>> 
>>>> On Mon, 2012-01-16 at 11:14 -0800, Mihael Hategan wrote:
>>>>> On Mon, 2012-01-16 at 13:10 -0600, Jonathan Monette wrote:
>>>>> 
>>>>>> as the first parameter in the ArrayList.  However I cannot make
>>>>>> anything show up in the logs.  I tried entering in the wrong password
>>>>>> as well as the correct password.  Is there anything else that needs to
>>>>>> be added to the JobSubmissionTaskHandler file?  Or where else should I
>>>>>> look besides the logs?
>>>>> 
>>>>> You need to type some wrong password to make the job fail which captures
>>>>> the output.
>>>> 
>>>> But then that won't work without a GUI askpass so, nevermind. You can
>>>> try to kill the ssh sub-process?
>>>> 
>>> 
>> 
>> 
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel