February 02, 2014, 01:33:21 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
   Home   Help Search Login Register  
Pages: [1]
Author Topic: error while syncing  (Read 3839 times)
« on: August 16, 2007, 10:05:34 AM »

I was able to upload an entire directory yesterday, but when I try to sync today, I'm getting the following error. Sometimes several files will get updated before the error happens, but I've tried 5 times and haven't been able to complete the sync.

# s3sync.rb -r --ssl --delete --progress ./akira.daily pettomato:backup
Update node etc/tinydns/log/supervise/control
Null stream error:
Skipping backup/akira.daily/etc/tinydns/log/supervise/control: undefined method `closed?' for nil:S3sync::ProgressStream
Update node etc/tinydns/log/supervise/ok
Null stream error:
Skipping backup/akira.daily/etc/tinydns/log/supervise/ok: undefined method `closed?' for nil:S3sync::ProgressStream
Update node etc/tinydns/supervise/control
Null stream error:
Skipping backup/akira.daily/etc/tinydns/supervise/control: undefined method `closed?' for nil:S3sync::ProgressStream
Update node etc/tinydns/supervise/ok
Null stream error:
Skipping backup/akira.daily/etc/tinydns/supervise/ok: undefined method `closed?' for nil:S3sync::ProgressStream
/usr/lib64/ruby/1.8/rexml/parsers/baseparser.rb:338:in `pull': malformed XML: missing tag start (REXML::ParseException)
Last 80 unconsumed characters:
                                    [2tMXH<^J({M#U from /usr/lib64/ruby/1.8/rexml/parsers/streamparser.rb:16:in `parse'
from /usr/lib64/ruby/1.8/rexml/document.rb:185:in `parse_stream'
from /home/astro/software/s3sync/S3.rb:595:in `initialize'
from /home/astro/software/s3sync/S3.rb:141:in `new'
from /home/astro/software/s3sync/S3.rb:141:in `list_bucket'
from /home/astro/software/s3sync/s3try.rb:57:in `send'
from /home/astro/software/s3sync/s3try.rb:57:in `S3try'
from /root/bin/s3sync.rb:287:in `s3TreeRecurse'
... 31 levels...
from /home/astro/software/s3sync/thread_generator.rb:76:in `initialize'
from /root/bin/s3sync.rb:269:in `new'
from /root/bin/s3sync.rb:269:in `main'
from /root/bin/s3sync.rb:708
Sr. Member
Posts: 363

(I am greg13070 on AWS forum)

View Profile
« Reply #1 on: August 16, 2007, 07:08:03 PM »

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.
« Reply #2 on: August 16, 2007, 07:43:06 PM »

ok, thanks. I'll exclude those and see how it goes.
edit: Yeah, that did it. My mistake. I added
to my rdiff-backup script that runs prior to s3sync and it cleared out all those special files. That'll save me from uploading hundreds of useless files as well.

Thanks and thank you very much for s3sync and s3cmd. They're great.
« Last Edit: August 16, 2007, 08:22:13 PM by ahaas » Logged
Pages: [1]
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!