Just for the record, the long bundling job was totally my fault. I had about 8 gigs of stuff that I had moved onto an instance in order to get in into S3 quickly. I just forgot about it and then rebundled the instance, which resulted in a really large AMI. D'oh!
Jeremy On Aug 10, 2:46 pm, rhythmandcode <[email protected]> wrote: > Over an hour ago I terminated farm 2082 and chose to synchronize the > rails role. The farm is still marked as "Synchronizing" and the > instance is still up. > > Here's what the bundle log shows: > > 2009-08-10 13:19:00 Synchronization started. > 2009-08-10 13:19:01 Executing pre-synchronization routines. > 2009-08-10 13:19:02 Clearing sensitive files. > 2009-08-10 13:19:03 Patching configs. > 2009-08-10 13:19:04 Creating image. > 2009-08-10 14:26:48 Uploading image to S3 (1 attempt). > > It looks like creating the image took a really long time for some > reason, and then the upload to S3 may have failed? Anyway, should I > just wait this out or what? > > 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 -~----------~----~----~----~------~----~------~--~---
