Automator and "Run Shell Script" error

Question

Automator and "Run Shell Script" error

First, if I'm in the wrong place with this- sorry. Figured this was an OS kind-of thing.

I recently migrated to a new iMac ... I brought along an Automator script; I've been using it for years to perform a little rsync backup to an USB HDD. It's 'never' given me any problems ... until now!

"*Run Shell Script*" encountered an error .. but alas, the system log is devoid of messages ... and the verbose log I have running indicates that all the files are copied/backed-up ... I would love any input on this that might help me get back on the feet. .....

*Here's what my Shell Script Looks like:*
Shell Option: /bin/bash
Pass Input: to stdin

rm -dfr '/Volumes/Backup HD/ *********'
rm -dfr '/Users/ ***********/Library/Logs/Profile_Backup.log'

rsync -rltv /Users/ ******** '/Volumes/Backup HD/' > /Users/ *******/Library/Logs/Profile_Backup.log

(I'm sure there's way to only sync the changed stuff between backups ... but I've simply preferred the fresh copy approach).

*I do however note this in my logs when I open Automator:*
12/14/10 3:15:46 PM [0x0-0x42042].com.apple.automator.Backup[464] Application Stub: OpenScripting.framework - scripting addition "/Library/ScriptingAdditions/Adobe Unit Types.osax" declares no loadable handlers.

iMac 27", Mac OS X (10.6.5)

Posted on Dec 14, 2010 1:46 PM

Reply

Answer 1

Tony T1

Level 6

10,232 points

Dec 14, 2010 4:53 PM in response to SeraphicImago

Not sure if this will fix the problem, but:
1) give the rsync path: /usr/bin/rsync
2) instead or directing output to the log file, use the rsync --log-file option:
--log-file="Users/ *******/Library/Logs/Profile_Backup.log"
3) no need for 'v' now use:


 /usr/bin/rsync-rlt --log-file="Users/*******/Library/Logs/Profile_Backup.log" /Users/******** '/Volumes/Backup HD/'

If this doesn't work, see what errors are in Profile_Backup.log

Reply

Answer 2

Dec 14, 2010 5:22 PM in response to Tony T1

@Tony T1

Thanks, I'll certainly adjust the log file as suggested 😉

In troubleshooting the problem I went the terminal route - and issued each command ... during the rsync process I was getting an error ... turns out when it was syncing the SyncServices folder it was encountering a copy of the keychain ... which had root permissions - naturally rsync was not able to copy the file (personally I have no idea why the keychain would be being sync'd with anything)!

I removed the file from the sync ... I'm still doing some "debugging" to correct the problem-

Again, thanks for the assist!

Reply