Did you start over and re-send the files to S3?  If you used the wrong character set before, the files on S3 will remain wrong!

Just to get this out of the way... are you setting S3SYNC_NATIVE_CHARSET correctly?  On windows the default value isn't correct and should probably be set to "Windows-1252"

Send me a zip file containing a directory structure and files that cause this problem (contact info is in the README) and I'll find some time to take a look at it.  Character encoding issues are supposed to be "solved" already.

I can't extract any more info from that error than what I said in the other post.  The ruby version requirements are in the README.  I'm not trying to be obstinate, I just don't know how else to help.

Forbidden means what it says; suspect your AWS credentials are not being set/read properly or something similar.

No no, don't sync those non-files, you're just asking for pain.  daemontools supervise directories contain weird pipes and stuff, you should exclude them.  The only useful ones are the "run" script files; all the other behind-the-curtain stuff can't be (and doesn't need to be) backed up.

Null stream means what it says; in this case it can't read the file in order to MD5 it and compare to what you have on s3.

md5 hashes of S3 nodes are retrieved in the list operation, and compared to the current md5 of the local item.  If they differ, the item is updated. (whether that means uploaded or downloaded, depends on the direction you are sync'ing)

I actually don't know the answer.. if you are putting the script and the satellite files in different places, maybe define that to be part of the ruby library path?  (I'm not much of a ruby expert..)

I keep them all together, and stand with the current directory as the s3sync dir.  From there I use "full paths" to indicate the operands.

You can't use s3sync with a file argument, only a directory.  This limitation may go away in the future, but probably not.  If you are desperate to transfer a single file you can use s3cmd with the "put" command.

Well I want to help, but for the rest of the week my time is no longer my own 

Even with a totally empty bucket I still can't repro the issue.  I have ruby 1.8.6 here but I'm pretty sure that's not "it".

"listing the files".. what's already in that bucket?  Maybe it's something strange that I'm not expecting?  it's going to be a bit tricky to debug this when I can't cause the problem to occur here.  Bear with me, I want to help!

The first s3 command (list_bucket) is throwing NoMethodError. 

I'm not sure whether this is a real "i don't know where that method is" problem, like if your s3 or http streaming code is borked, or if instead it just can't contact the s3 server.  Ever since I implemented --progress the errors coming out of the stream code are just *useless*.

Can you back up and try something else like "./s3cmd.rb listbuckets" or list bck-backup

Not that I'm aware of.  And it is designed to use as small a memory footprint as possible for the directory recursion.

Thanks.
Why not update the wiki home page and link to it?  That way people don't have to search here.