Details
-
Fix
-
Status: Released (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
Description
If you start YADE on HostA for a transfer via a jump host (HostB) and the YADE installation path on HostA and HostB are the same then the YADE Client on the jump host doesn't get any parameter and the ssh session ends with exit 1.
StdOut of the ssh session where YADE on the jump host is called
(SOSSSHJob2.java:439) ::CheckStdOut stdout = 23679
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ START : JADE.SH +
+ ---------------- +
+ DATE : Fri Feb 27 08:53:19 UTC 2015 +
+ HOSTNAME : hostB +
+ USER : test +
+ CALL : sh +
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
JADE requires parameters. Please see
http://www.sos-berlin.com/doc/en/jade/JADE%20Users%20Manual.pdf
main ERROR 09:53:13,873 (SOSSSHJob2.java:352) ::CheckExitCode SOS-SSH-E-150: remote command terminated with exit code: 1
main ERROR 09:53:13,874 (SOSSSHJob2.java:259) ::Execute SOS-SSH-E-150: remote command terminated with exit code: 1
sos.net.ssh.SOSSSHJob2.CheckExitCode(SOSSSHJob2.java:355)
sos.net.ssh.SOSSSHJob2.Execute(SOSSSHJob2.java:255)
com.sos.DataExchange.Jade4DMZ.executeSSHCommand(Jade4DMZ.java:544)
com.sos.DataExchange.Jade4DMZ.StartTransferFromDMZ2Inet(Jade4DMZ.java:494)
com.sos.DataExchange.Jade4DMZ.Execute(Jade4DMZ.java:177)
com.sos.DataExchange.SOSDataExchangeEngine4DMZMain.Execute(SOSDataExchangeEngine4DMZMain.java:69)
com.sos.DataExchange.SOSDataExchangeEngine4DMZMain.main(SOSDataExchangeEngine4DMZMain.java:28)
This behavior does not occur if a different location of the YADE start script (jade.sh) on the local system and on the jump host are used, e.g.
jump_command = /opt/sos-berlin.com/jade_jump/client/bin/jade.sh
