Due to low instance startup timeout value, your MySQL instance was terminated while uploading data snapshot. This lead to snapshot corruption and so MySQL could not finish its initialization. We have managed it manually and now your instance is up and running using EBS volume as data storage.
2009/3/11 Nathan Palmer <[email protected]>: > > It's 1354. I just changed the mysql role over to mysqllvm with EBS > storage. But it looks like it's still having the same problem and not > ever finishing the boot up. > > Nathan > > 2009/3/10 Nickolas Toursky <[email protected]>: >> >> Could you please let us know your farm ID ? >> >> Thanks, >> Nick >> >> On 11 мар, 04:19, Nathan Palmer <[email protected]> wrote: >>> I have a farm that I just created and the mysql instance was >>> previously working. Now when it boots up it keeps terminating itself >>> and then starting up another instance. The only thing in the log I >>> found possibly relevant was this. >>> >>> Traceback (most recent call last): >>> File "/usr/bin/s3cmd", line 415, in >>> error("S3 error: " + str(e)) >>> File "/usr/lib/python2.5/site-packages/S3/S3.py", line 41, in __str__ >>> retval += (": %s" % self.info["Code"]) >>> KeyError: 'Code'. Retrying. >>> >>> Any ideas? I can restage this machine but I'm a bit worried that >>> something like this could happen after i go live and I have real live >>> data on the site. >>> >>> Nathan >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
