Re: [Condor-users] condor_ssh_to_job

[Peter Ellevseth <Peter.Ellevseth@xxxxxxxxxx>]

Hi
I 'LogLevel DEBUG3' to the config-file and now the log.sshd files looks like this

Disabling protocol version 1. Could not load host key
debug1: inetd sockets after dupping: 3, 4
Connection from <IP-address of submit machine> port 51587
Did not receive identification string from <IP-address of submit machine>

The two lines in the middle are new.

Peter

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Dan Bradley
Sent: 23. juli 2010 16:36
To: Condor-Users Mail List
Subject: Re: [Condor-users] condor_ssh_to_job

Peter,

I see the same sort of debug output from my working condor_ssh_to_job 
installation, so I don't think any of the debug lines from your ssh 
client explain whatever is going wrong.

Any luck increasing the debug level on the server side?

--Dan

Peter Ellevseth wrote:
> I tried doing 
> Condor_ssh_to_job -ssh 'ssh -vvv' <job.id>
>
> And got the following result.
> I have done some googling on the line
> debug3: Not a RSA1 key file /tmp/pel.condor_ssh_to_job_a7dd8e00/ssh_key.
>
> But without luck. Any ideas
>
> OpenSSH_5.1p1, OpenSSL 0.9.8h 28 May 2008
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Applying options for *
> debug2: ssh_connect: needpriv 0
> debug1: Executing proxy command: exec "condor_ssh_to_job" "-proxy" "3"
> debug1: permanently_drop_suid: 513
> debug3: Not a RSA1 key file /tmp/pel.condor_ssh_to_job_a7dd8e00/ssh_key.
> debug2: key_type_from_name: unknown key type '-----BEGIN'
> debug3: key_read: missing keytype
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug3: key_read: missing whitespace
> debug2: key_type_from_name: unknown key type '-----END'
> debug3: key_read: missing keytype
> debug1: identity file /tmp/pel.condor_ssh_to_job_a7dd8e00/ssh_key type -1
> ssh proxy communication failure: Failed to set socket to non-blocking mode.
> ssh_exchange_identification: Connection closed by remote host
>
> Thanks, Peter
>
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Dan Bradley
> Sent: 13. juli 2010 16:47
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] condor_ssh_to_job
>
> Peter,
>
> The "Disabling protocol" line is expected, but the other line is not.
>
> You could try increasing verbosity.  On the ssh client side, you can get 
> verbose debugging like this:
>
> condor_ssh_to_job -ssh 'ssh -vvv' <jobid>
>
> On the server side, you could add the following line to condor's 
> lib/condor_ssh_to_job_sshd_config_template:
>
> LogLevel DEBUG3
>
> --Dan
>
> Peter Ellevseth wrote:
>   
>> Hi
>>
>> The sshd.log has only two lines
>>
>> Disabling protocol version 1. Could not load host key
>> Did not receive identification string from <IP-address of submit machine>
>>
>> Peter
>>
>>
>> -----Original Message-----
>> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Dan Bradley
>> Sent: 12. juli 2010 16:56
>> To: Condor-Users Mail List
>> Subject: Re: [Condor-users] condor_ssh_to_job
>>
>> Peter,
>>
>> It may help to see why sshd says it is closing the connection.  In the 
>> job's scratch execute directory on the execute machine, you will find a 
>> sub-directory named .condor_ssh_to_job_1.  The sshd logs are inside that 
>> directory in a file named sshd.log.
>>
>> --Dan
>>
>> Peter Ellevseth wrote:
>>   
>>     
>>> Hi
>>>
>>> I am having problems using condor_ssh_to_job
>>>
>>>  
>>>
>>> I get the following error:
>>>
>>>  
>>>
>>> ssh proxy communication failure: Failed to set socket to non-blocking 
>>> mode.
>>>
>>> ssh_exchange_identification: Connection closed by remote host
>>>
>>>  
>>>
>>> Has anybody any experience using this function?
>>>
>>>  
>>>
>>> Peter
>>>
>>>  
>>>
>>>     
>>>       
>> _______________________________________________
>> Condor-users mailing list
>> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>>
>> The archives can be found at:
>> https://lists.cs.wisc.edu/archive/condor-users/
>>
>>
>> _______________________________________________
>> Condor-users mailing list
>> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
>> subject: Unsubscribe
>> You can also unsubscribe by visiting
>> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>>
>> The archives can be found at:
>> https://lists.cs.wisc.edu/archive/condor-users/
>>   
>>     
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>   
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/