S3Sync.net

General Category => Questions => Topic started by: Glyn on October 23, 2007, 04:35:51 PM



Title: `iconv': invalid encoding
Post by: Glyn on October 23, 2007, 04:35:51 PM
Hi, I'm new to s3sync and I'm trying to get it running on my synology diskstation NAS device.  However, when I run s3cmd (or s3sync) I get the following results (I've already added my "brainbackup" bucket with s3cmd).

I suspect that the solution may lay with S3SYNC_NATIVE_CHARSET, but I don't what this needs to be set to (However, I read the message that it's trying to use UTF-8... so that should be valid??).

Any help gratefully received!
Thanks,
Glyn

Brain> ruby s3cmd.rb listbuckets
brainbackup
Brain> ruby s3cmd.rb list brainbackup
--------------------
./S3encoder.rb:42:in `iconv': invalid encoding ("UTF-8", "ISO-8859-1") (Iconv::I
nvalidEncoding)
        from ./S3encoder.rb:42:in `escape'
        from ./S3.rb:138:in `list_bucket'
        from s3cmd.rb:20:in `map'
        from ./S3.rb:138:in `each'
        from ./S3.rb:138:in `map'
        from ./S3.rb:138:in `list_bucket'
        from ./s3try.rb:57:in `send'
        from ./s3try.rb:57:in `S3try'
        from s3cmd.rb:190:in `s3cmdList'
        from s3cmd.rb:115:in `s3cmdMain'
        from s3cmd.rb:211
Brain>


Further info on Ruby version etc,

Brain> ipkg status
Package: make
Version: 3.81-1
Status: install user installed
Architecture: powerpc
Installed-Time: 1193168956

Package: openssl
Version: 0.9.7m-3
Status: install user installed
Architecture: powerpc

Package: ruby
Version: 1.8.6.110-1
Status: install user installed
Architecture: powerpc

Package: rubygems
Version: 0.9.2-1
Depends: ruby (>= 1.8.4-2)
Status: install user installed
Architecture: powerpc

Package: wget-ssl
Version: 1.10.2-4
Depends: openssl
Conflicts: wget
Status: install user installed
Architecture: powerpc

Package: zlib
Version: 1.2.3-2
Status: install user installed
Architecture: powerpc

Successfully terminated.
Brain>


Title: Re: `iconv': invalid encoding
Post by: Glyn on October 24, 2007, 01:29:48 PM
export S3SYNC_NATIVE_CHARSET=UTF-8

fixed it.