Cannot get s3sync to invoke

[edstuart]

Hi,

I have Ruby, verson 1.8.6, on my MBP running Tiger and when I attempt to execute backup.sh from its /Library/s3backup directory, I receive the following errors:

        /usr/lib/ruby/1.8/yaml.rb:119:in `load': parse error on line 3, col -1: `' (ArgumentError)
                from /usr/lib/ruby/1.8/yaml.rb:119:in `load'
                from /usr/lib/ruby/1.8/yaml.rb:130:in `load_file'
                from /usr/lib/ruby/1.8/yaml.rb:129:in `open'
                from /usr/lib/ruby/1.8/yaml.rb:129:in `load_file'
                from ./s3config.rb:19
                from ./s3config.rb:17:in `each'
                from ./s3config.rb:17
                from /Library/s3backup/s3sync.rb:28:in `require'
                from /Library/s3backup/s3sync.rb:28

As I know nothing about ruby, would someone be so kind as to give me a pointer or two here?

Thanx,
Ed

[s3user]

I have the same error, running on Ubuntu.

I took the example config file, put in the appropriate keys and CERT directory, placed it in my home dir in ~/s3conf/s3config.yml, and ran this as a test (let's back up the s3sync dir):

./s3sync/s3sync.rb ./s3sync

I got the following:

/usr/lib/ruby/1.8/yaml.rb:133:in `load': syntax error on line 3, col -1: `' (ArgumentError)
   from /usr/lib/ruby/1.8/yaml.rb:133:in `load'
   from /usr/lib/ruby/1.8/yaml.rb:144:in `load_file'
   from /usr/lib/ruby/1.8/yaml.rb:143:in `open'
   from /usr/lib/ruby/1.8/yaml.rb:143:in `load_file'
   from /home/blueplate/s3sync/s3config.rb:19
   from /home/blueplate/s3sync/s3config.rb:17:in `each'
   from /home/blueplate/s3sync/s3config.rb:17
   from ./s3sync/s3sync.rb:28:in `require'
   from ./s3sync/s3sync.rb:28

I can't tell from the error what's going on. Is it not seeing my conf file? Is the file corrupt? Pointers appreciated.

[s3user]

Note: if I completely delete my config file, I then get a more normal result:

$ ./s3sync/s3sync.rb ./s3sync
You didn't set up your environment variables; see README.txt
s3sync.rb [options] <source> <destination>      version 1.2.6
  --help    -h          --verbose     -v     --dryrun    -n   
  --ssl     -s          --recursive   -r     --delete
...

[Admin]

It's impossible to tell without seeing at least a redacted config file.