I got a new coworker, so I am setting up his Linux user and environment. One of the scripts we have copies projects from a development server to the production server.
The output from scp ran from the script would lead you to believe the scp command worked, but the file is nowhere to be found on the server it was sent to.
Code from the script:
Code:
# send .tsk file to corp
CMD="scp ${POLL}/${PROJ}.tsk dave@corp:/home/dave/poll/${PROJ}.tsk"
echo "Sending .tsk file to CORP: ${CMD}"
${CMD} #2>/dev/null
Output from the script:
Code:
Sending .tsk file to CORP: scp /u/home/dave/poll/test.tsk dave@corp:/home/dave/poll/test.tsk
logname: no login name
test.tsk 100% 66 0.1KB/s 00:00
Here is the verbose:
Code:
Sending .tsk file to CORP: scp -v /u/home/dave/poll/test.tsk dave@corp:/home/dave/poll/test.tsk
Executing: program /usr/bin/ssh host corp, user dave, command scp -v -t /home/dave/poll/test.tsk
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to corp [192.168.200.105] port 22.
debug1: Connection established.
debug1: identity file /u/home/dave/.ssh/identity type -1
debug1: identity file /u/home/dave/.ssh/id_rsa type -1
debug1: identity file /u/home/dave/.ssh/id_dsa type 2
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'corp' is known and matches the RSA host key.
debug1: Found key in /u/home/dave/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
Unknown code krb5 195
debug1: Unspecified GSS failure. Minor code may provide more information
Unknown code krb5 195
debug1: Unspecified GSS failure. Minor code may provide more information
Unknown code krb5 195
debug1: Next authentication method: publickey
debug1: Trying private key: /u/home/dave/.ssh/identity
debug1: Trying private key: /u/home/dave/.ssh/id_rsa
debug1: Offering public key: /u/home/dave/.ssh/id_dsa
debug1: Server accepts key: pkalg ssh-dss blen 434
debug1: read PEM private key done: type DSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending command: scp -v -t /home/dave/poll/test.tsk
logname: no login name
Sending file modes: C0666 66 test.tsk
Sink: C0666 66 test.tsk
test.tsk 100% 66 0.1KB/s 00:00
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0
If I copy and paste the command used directly into the terminal command line, and check the other server, the file will be there.