Superb, that worked a treat. Thanks for your help.
Paul

On Oct 24, 10:00 am, Nickolas Toursky <[EMAIL PROTECTED]> wrote:
> As a workaround you can manually send an event indicating startup
> finish to Scalr.
>
> After startingMySQLdo the following:
>
> . /usr/local/aws/lib/lib.sh
>
> ec2_submit_event hostUp
>
> On Oct 24, 11:28 am, "[EMAIL PROTECTED]"
>
> <[EMAIL PROTECTED]> wrote:
> > Is there a way round this situation at the moment that will let me
> > start themysqlinstance? The instance never gets past "initializing",
> > I can log on to the instance, attachEBSand successfully startmysql
> > but scalr doesn't seem to pick this up...utlimately scalr terminates
> > the instance. Can you suggest some way that I can get this instance
> > working correctly and "prod" scalr to detect thatmysqlhas started?
>
> > Thanks,
> > Paul
>
> > On Oct 23, 9:13 pm, "[EMAIL PROTECTED]"
>
> > <[EMAIL PROTECTED]> wrote:
> > > That's fine. I'm quite happy with that. Is it possible to script this
> > > into the image so it automatically attaches the correctEBSvolume?
>
> > > On Oct 23, 8:53 pm, Alex Kovalyov <[EMAIL PROTECTED]> wrote:
>
> > > > > The tutorials that I've read and the fanfare aroundEBSwas based on
> > > > > the fact thatmysql(and a web server) could now be persisted across
> > > > > reboots. So, without wanting the complexity of LVM is it not possible
> > > > > to useEBSwith themysqlinstance? It seems a bit, er, pointless
> > > > > otherwise.
>
> > > > Once again, the currentEBSon Scalr is limited  to manual
> > > > create-attach-detach.
> > > > The "automatic" will be up in couple days.
>
> > > > On 23.10.08 22:34, "[EMAIL PROTECTED]"
>
> > > > <[EMAIL PROTECTED]> wrote:
>
> > > > > I fear I'm going to go over old ground here so apologies...
>
> > > > > The tutorials that I've read and the fanfare aroundEBSwas based on
> > > > > the fact thatmysql(and a web server) could now be persisted across
> > > > > reboots. So, without wanting the complexity of LVM is it not possible
> > > > > to useEBSwith themysqlinstance? It seems a bit, er, pointless
> > > > > otherwise.
>
> > > > > As an aside I had exactly the same problem with the app instance i.e.
> > > > >EBSwasn't available. That didn't stop the instance moving to a
> > > > > "running" state, it's my belief that the same should be true for
> > > > >mysql.
>
> > > > > Thanks,
> > > > > Paul
>
> > > > > On Oct 23, 7:02 pm, Alex Kovalyov <[EMAIL PROTECTED]> wrote:
> > > > >> EC2 glitches, us-east-1c in particular. So they removed it from the 
> > > > >> list of
> > > > >> available zones - I guess its.. out of capacity.
>
> > > > >> On 23.10.08 20:32, "[EMAIL PROTECTED]"
>
> > > > >> <[EMAIL PROTECTED]> wrote:
> > > > >>> Insufficient Capacity
> > > > >>> I can't configure any of my roles to "us-east-1c",
> > > > >>> it's not in the list of availability zones
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to