Re: ssh failure due to local error

2009-08-17 Thread Wayne Davison
On Mon, Aug 17, 2009 at 09:02:42PM +0100, e-letter wrote: > rsync -t *.txt u...@remote.machine: > No response from the command terminal, except for a new prompt Then it succeeded. If you want it to be more verbose, tell it to be verbose. ..wayne.. -- Please use reply-all for most replies to avo

rsync: connection unexpectedly closed

2009-08-17 Thread dhtmldude
I'm using Rsync 3.1.0 and VanDyke VShell for SSH. Both services have started up in the remote server under the local account nasadmin. I know port 22 is open on the firewall because i was able to see the root directory being created after an rsync command from the server, but no files were synch

Re: ssh failure due to local error

2009-08-17 Thread e-letter
On 17/08/2009, Paul Slootman wrote: > On Mon 17 Aug 2009, Paul Slootman wrote: >> > >> > I have tried the following command: >> > >> > rsync -t *.txt ssh u...@remote.machine: > I removed the ssh from the command: rsync -t *.txt u...@remote.machine: No response from the command terminal, except f

Re: ssh failure due to local error

2009-08-17 Thread e-letter
On 17/08/2009, Paul Slootman wrote: > On Mon 17 Aug 2009, e-letter wrote: >> >> I have tried the following command: >> >> rsync -t *.txt ssh u...@remote.machine: >> >> and receive the following error: >> >> rsync: link_stat "local/machinepath/ssh" failed: No such file or directory >> (2) > > Does:

Re: ssh failure due to local error

2009-08-17 Thread e-letter
On 17/08/2009, si...@tranmeremail.org.uk wrote: > Try rsync -av *.txt:u...@remote.machine/path/to/where/you/want/it/to/go/ > (assuming you only want to rsync the txt files from the current > working directory on the A side - else put the full path in with a > trailing slash). This failed, command

Re: exit_cleanup(code=12, file=io.c, line=609)

2009-08-17 Thread dhtmldude
I got more information: exec request failed on channel 0 rsync: connection unexpectedly closed (0 bytes received so far) [sender] _exit_cleanup(code=12, file=io.c, line=609): entered rsync error: error in rsync protocol data stream (code 12) at io.c(609) [sender= 3.0.6] _exit_cleanup(code=12, fil

Re: exit_cleanup(code=12, file=io.c, line=609)

2009-08-17 Thread dhtmldude
Its not syncronizing anything. It sits there waiting, until i press CTRL C and terminate the batch job, then the log looks like this: cmd=ssh.exe -i C:\cms\PageGenerator\qa_rsa machine=10.243.101.218 user=nasadmin path=/cygdrive/g/EWCMS_SYNC/test_aug17/ cmd[0]=ssh.exe cmd[1]=-i cmd[2]=C:\cms\Pag

Re: ssh failure due to local error

2009-08-17 Thread Paul Slootman
On Mon 17 Aug 2009, Paul Slootman wrote: > > > > I have tried the following command: > > > > rsync -t *.txt ssh u...@remote.machine: Ah, I now see a spurious "ssh" there. That tells rsync that you also want to transfer a file "ssh", in addition to the *.txt files. Do you have a file "ssh" in tha

Re: exit_cleanup(code=12, file=io.c, line=609)

2009-08-17 Thread Paul Slootman
On Mon 17 Aug 2009, dhtmldude wrote: > > I got my SSH working, turns out another process was using port 22 and > VanDyke Vshell was not started. Now Its synchronized a folder but not its > contents. Im not sure what to do next other than put more files in the > source and see if they make it ove

Re: exit_cleanup(code=12, file=io.c, line=609)

2009-08-17 Thread dhtmldude
Paul Slootman-5 wrote: > > Your ssh session is not being established, so rsync doesn't even get a > chance to do its thing. > > First get your ssh working, only then look at rsync. > > > Paul > > I got my SSH working, turns out another process was using port 22 and VanDyke Vshell was not

Re: exit_cleanup(code=12, file=io.c, line=609)

2009-08-17 Thread Paul Slootman
On Mon 17 Aug 2009, dhtmldude wrote: > > Folks, maybe one of you can help me. I've installed Rsync 3.1.0 on both the > client and the server. Im using ssh, my command line follows: > > rsync -avc --delete -e "ssh.exe -i C:\cms\PageGenerator\nasadmin_prod_rsa" > -vvv \\cagecfsu1.saifg.rbc.com\Y

Re: ssh failure due to local error

2009-08-17 Thread Paul Slootman
On Mon 17 Aug 2009, e-letter wrote: > > I have tried the following command: > > rsync -t *.txt ssh u...@remote.machine: > > and receive the following error: > > rsync: link_stat "local/machinepath/ssh" failed: No such file or directory (2) Does: ssh u...@remote.machine actually work to giv

Re: ssh failure due to local error

2009-08-17 Thread simon
Try rsync -av *.txt:u...@remote.machine/path/to/where/you/want/it/to/go/ (assuming you only want to rsync the txt files from the current working directory on the A side - else put the full path in with a trailing slash). Quoting e-letter : Readers, I have tried the following command: rsy

ssh failure due to local error

2009-08-17 Thread e-letter
Readers, I have tried the following command: rsync -t *.txt ssh u...@remote.machine: and receive the following error: rsync: link_stat "local/machinepath/ssh" failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2] My unde

exit_cleanup(code=12, file=io.c, line=609)

2009-08-17 Thread dhtmldude
Folks, maybe one of you can help me. I've installed Rsync 3.1.0 on both the client and the server. Im using ssh, my command line follows: rsync -avc --delete -e "ssh.exe -i C:\cms\PageGenerator\nasadmin_prod_rsa" -vvv \\cagecfsu1.saifg.rbc.com\YCM0\InternalCache\test_aug17/ ad...@10.243.101.