Welcome to YLOAN.COM
yloan.com » misc » Resolving "rsync warning: some files vanished before they could be transferred" on ec2-bundle-vol in an aws ec2 instance
Gadgets and Gizmos misc Design Bankruptcy Licenses performance choices memorabilia bargain carriage tour medical insurance data

Resolving "rsync warning: some files vanished before they could be transferred" on ec2-bundle-vol in an aws ec2 instance

Resolving "rsync warning: some files vanished before they could be transferred" on ec2-bundle-vol in an aws ec2 instance


This article explains how to resolve some of the common errors that you may encounter when bundling an AMI ( Amazon Machine Image) of an AWS EC2 instance. It is indeed a very good practice bundling your AMI frequently as the latest updates of your app gets stored directly to S3. So even if your instance gets crashed you can launch another instance of your latest ami and get your site back live in minutes!.

But bundling can be a big hassle if we get stuck with rsync errors during the process. There are quite a few cases where rsync fails during bundling.

1) No space left on the device


This usually happens when we specify the size of the / partition with the -s parameter that specifies size, in MB of the image file to create. The maximum size is 10240 MB. Removing the "-s" flag and letting the system determine the size of the image itself will fix it. Also the bundling process will try to include all softlinks ( if any ) to other partitions of larger size ( greater than 10GB ). This would try creating an image file larger than 10GB size and hence throw bundle errors. So check for any softlinks before bundling.

2) Size of /tmp

By Default ec2-bundle-vol will try to bundle the image in /tmp. So if the size of /tmp is small this will throw bundling errors too. Specifying "-d /mnt" to point to the ephemeral drive rather than bundling the image in /tmp by default is a fix for this.

3) rsync warning: some files vanished before they could be transferred

This one is quite an interesting error as it is a warning that some files are being deleted while the bundling process is happening. In my case I had an instance with around 2GB free space in / partition. Also there was a 100GB EBS mounted on /home_ebs. I tried bundling the instance by excluding the 100GB EBS, but still it gave rsync error.

Running Bundle Volume from within a running installation may be problematic because partially written files may get copied into the AMI. To minimize the risk the best option is to stop all non essential services and try rebundling. In my case I removed the /var/log/dcpumon directory and went for a rebudling. That did the trick !.

Please note that using the "debug" option with ec2-bundle-vol command will be of immense help in troubleshooting bundling errors. Hope this helps anyone out there !

Visit : http://www.migrate2cloud.com/blog/
THE FASCINATING VISITING CARD Rackspace with Cloud Computing: Hype or Help? Have An Enticing Stay In Barcelona Toilet Seat Covers of Tomorrow, Today Area Rugs: Flooring Accents for Any Room How High Do You Need To Jump To Dunk Why Would You Buy A Rowing Machine Anyway? Benefits Exposed HTC HD7 deals- Capture the best offers on contract How Do Metal Detectors Work? Show Your Team Spirit With Charm Bracelets Trim Your Youthful Lad'sIn-thing Space With Dinosaur Cheap Toddler Bedding Virtualgranny Funky Fudge How Long Will It Take To Ship A Car
print
www.yloan.com guest:  register | login | search IP(216.73.216.114) California / Anaheim Processed in 0.016941 second(s), 7 queries , Gzip enabled , discuz 5.5 through PHP 8.3.9 , debug code: 22 , 2588, 85,
Resolving "rsync warning: some files vanished before they could be transferred" on ec2-bundle-vol in an aws ec2 instance Anaheim