SSH cmd hanging in workflow's external task

We are trying to execute a script on another server using the SSH from Teamsite (6.7.1), OS-Linux.

It is hanging ... at SSH cmd, but we checked on the target server the script is executed.

when we execute the same perl on command line outside workflow... it is working perfectly.

ssh cmd in perl: ssh dba@targetserver '~/.profile; /abcbatch/net/abcrod/ps/scripts/ps_schema_import.sh -f pmrsb -o xysrosb' 2>&1

checked the real/effective userid/groupid .. looks same for me... below are the process details of the task process and ssh process.

$ id iwmaster
uid=123(iwmaster) gid=123(iwmaster)

task process:

iwmaster 11669 28596 0 11:05 ? 00:00:00 iwperl /iwhome/iw-home/local/config/wft/nextgen/dotcom/berkeley/scripts/wft_dotcom_berkeleydb_refresh.ipl 14462914 14462920 /abc/main/dotcom/application/WORKAREA/application

ssh process:

iwmaster 11674 11669 0 11:05 ? 00:00:00 sh -c ssh dba@targetserver '~/.profile; /abcbatch/net/abcrod/ps/scripts/ps_schema_import.sh -f pmrsb -o xysrosb' 2>&1
iwmaster 11675 11674 0 11:05 ? 00:00:00 ssh dba@targetserver ~/.profile; /abcbatch/net/abcrod/ps/scripts/ps_schema_import.sh -f pmrsb -o xysrosb

there was similar thread , but no solution: /t5/OpenDeploy/ssh-command-in-WFM-external-task/m-p/146936

thanks,

Balaveera.

Find more posts tagged with

Comments

nipper

You may need to load Net: Smiley Frustrated SH: Smiley Tongue erl

and use that instead of trying SSH through system

Also are you checking to see if it worked ? If not you can then just fork it off and forget it.

Balaveera Thatikonda

@nipper

Tried with Net: Smiley Frustrated SH: Smiley Tongue erl as well , same situation ... hanging....

Adam Stoller

Check the environment infomation both from outside the workflow and from within the script executed by the workflow - chances are you may be missing some important environment settings that may be preventing ssh from working via the script.

Balaveera Thatikonda

Not sure what variable I should look for but I found a difference for "HOME" variable:

From - workflow-script:
HOME = /

Outside of workflow-script
HOME = /home/iwts

used this code to get the env values
foreach my $key (keys %ENV) {
print "$key = $ENV{$key}\n";
}

Adam Stoller

I would start with ANY difference - try hard-coding all those environment variables - in a BEGIN block, just to test to see if you set them all whether the code starts working. If so, then start commenting out each setting and figuring out where/when it starts breaking.

Balaveera Thatikonda

Hi,

I tried changing couple of env variables, but its the same problem.

In the interest of the time, we achieved it by using OpenDeploy's DNR functionality.

Thanks everyone for the suggestions.