Ah-ha! So you need to shutdown everything before Synchronizing. That makes sense, now that I think about it....
Thanks, Jeremy On Sep 18, 4:28 pm, Nickolas Toursky <[email protected]> wrote: > Jeremy, > > This often happens due to some files were changed during synchronize. > > Please check the services like splunk, MTA (postfix, exim, etc) are stopped. > > Nick > > 2009/9/18 rhythmandcode <[email protected]>: > > > > > Hi guys, I'm trying to sync an instance and it keeps failing on me. > > Can somebody take a look and let me know what you think? > > > Instance ID: i-145db37c > > > Here's the relevant bit of the log: > > Rebundle output: Checking prerequisites: > > SNMP daemon and SNMP trap daemon ... OK > > OpenSSH server and its configuration ... OK > > Checking Scalr scripts ... OK > > Executing pre-rebundle routines > > * Stopping system log daemon... [80G > > [74G[ OK ] > > * Starting system log daemon... [80G > > [74G[ OK ] > > Copying / into the image file /mnt/backgroundrb-200909181416... > > Excluding: > > /sys > > /proc > > /dev/pts > > /dev > > /media > > /mnt > > /proc > > /sys > > /root/.ssh > > /etc/aws > > /mnt > > /var/run/scalr/trap_ids > > /mnt/backgroundrb-200909181416 > > /mnt/img-mnt > > 1+0 records in > > 1+0 records out > > 1048576 bytes (1.0 MB) copied, 0.023796 s, 44.1 MB/s > > mke2fs 1.40.8 (13-Mar-2008) > > NOTE: rsync with preservation of extended file attributes failed. > > Retrying rsync > > without attempting to preserve extended file attributes... > > execution failed: "rsync -rlpgoD -t -r -S -l --exclude /sys --exclude / > > proc --exclude /dev/pts --exclude /dev --exclude /media --exclude /mnt > > --exclude /proc --exclude /sys --exclude /root/.ssh --exclude /etc/aws > > --exclude /mnt --exclude /var/run/scalr/trap_ids --exclude /mnt/ > > backgroundrb-200909181416 --exclude /mnt/img-mnt /* /mnt/img-mnt 2>&1 > >> /dev/null" > > ec2-bundle-vol failed. > > SSH port is not set to 22. Do not forget to edit default SSH port in > > Scalr settings. > > > I double checked and the SSH port that Scalr knows about is the one > > that the running instance is using. > > > Thanks, > > Jeremy > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
