Rsync Permission denied errors.

KroniK · 08-10-2012, 03:11 AM

Hello Guys,

I have been making a script to automatically rsync about 40 different directories to 40 other different directories. I finally got all the syntax and everything worked out but I'm having some permissions errors pop up when I try to do the rsync.

Here is my bash script: http://pastebin.com/uph49vHd

The error I get when I run it is:

Code:

[root@KISKA Tech]# ./websync.sh
doing some cleanup
writing directory names to kiskasys.txt
I am now nusak at foo.bar.net
just wrote directory names to websys.txt
websys.txt                                                                                                                                  100%  244     0.2KB/s   00:00
Just coppied websys.txt from webserver to KISKA.nusalaska.com
rsync: Failed to exec /nusdata/staff/NUS/NUS/Systems/101 greenbrook/: Permission denied (13)
rsync error: error in IPC code (code 14) at pipe.c(84) [sender=3.0.6]
rsync: writefd_unbuffered failed to write 6 bytes to fd 4 [sender]: Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(1525) [sender=3.0.6]

I ran the script as root so I would figure that the local file would have no permissions issues... but obviously I am missing something.

Any help would be appreciated!

KroniK · 08-10-2012, 03:10 PM

Found the problem. I was using -e before both the local directory and the ssh command... the -e has to go after the local directory but before the ssh command

Reuti · 08-13-2012, 10:28 AM

It should also work if the -e including its argument are before the local directory. More important is, that -e needs an argument. Most likely you are referring to this argument by “ssh command”.

suicidaleggroll · 08-13-2012, 12:39 PM

Flags such as -e require an argument. The syntax is "program flag argument", so your ssh argument needs to immediately follow the -e flag.

-e tells rsync what remote shell to use for the transfer (such as ssh or rsh). By putting your local directory name after -e, rsync is trying to use your local directory AS the transfer shell. In other words, you're telling rsync that the directory is actually a program that rsync should execute in order to facilitate the transfer. That's why you got the error, rsync was unable to "execute" the directory: "rsync: Failed to exec /nusdata/staff/..."