Re: [HTCondor-users] condor_ssh_to_job

["Shrum, Donald C" <DCShrum@xxxxxxxxxxxxx>]

Thanks for the replies....

Our condor cluster is a dedicated cluster and I am the sysadmin and perfectly happy for users to ssh_to_job to see what is going on.
User home directories are not on the processing nodes but the logins are enabled and shells present.

[dcshrum@condor-login vanilla]$ condor_q
-- Submitter: condor-login.local : <10.178.6.3:43563> : condor-login.local
 ID      OWNER            SUBMITTED     RUN_TIME ST PRI SIZE CMD               
   2.0   dcshrum         8/21 15:12   0+00:00:01 R  0   0.0  a.out             

 [dcshrum@condor-login vanilla]$ condor_ssh_to_job 2
This account is currently not available.
Connection to condor-job.condor-29.local closed.


[dcshrum@condor-login vanilla]$ ssh dcshrum@condor-29
Warning: Permanently added 'condor-29,10.178.6.29' (RSA) to the list of known hosts.
dcshrum@condor-29's password: 
-sh-4.1$ logout
Connection to condor-29 closed.


There must be a setting I am missing.  
ENABLE_SSH_TO_JOB = true
SCHEDD_ENABLE_SSH_TO_JOB = true

Uncommenting the SSH_TO_JOB_SSH_CMD line seemed to cause more problems... 
That generated the error "Error parsing configuration SSH_TO_JOB_ssh_CMD: Expecting double-quoted input string (V2 format)." 

if someone has a working config file and can share it that would help.

--Donny
FSU Research Computing Center

-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Brian Bockelman
Sent: Wednesday, August 21, 2013 2:15 PM
To: HTCondor-Users Mail List
Cc: condor-users@xxxxxxxxxxx
Subject: Re: [HTCondor-users] condor_ssh_to_job

Hi Donny,

In the end, condor_ssh_to_job relies on the ssh binaries and configuration on the worker node.  If the sysadmins have disabled SSH logins (either via sshd_config or setting the user's shell to nologin), then condor_ssh_to_job won't work.

To some extent, disabling logins in sshd_config is the admins way of setting "site policy" and condor should obey it.  It may be a good idea to talk to your sysadmin.

A purposely limited job-monitoring is "condor_tail".  Depending on what you were trying to do, that may be helpful.

Brian

On Aug 21, 2013, at 12:39 PM, "Shrum, Donald C" <DCShrum@xxxxxxxxxxxxx> wrote:

> When I try to condor_ssh_to_job I get the message... 
> This account is currently not available.
> 
> I'm guessing the job is running as nobody and that there is a setting in condor_config that tells condor to use the id the job was submitted with.  I'm looking in the manual now but if someone has a quick answer I would appreciate it.
> 
> 
> --Donny
> FSU Research Computing Center
> 
> 
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> 
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/


_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

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