RodneyQ, Thanks for your kindly reply.

I reinstall scalr with the following step:
 1) 
http://blog.getasysadmin.com/2008/11/how-to-install-scalr-on-ubuntu-810-ec2.html
 2) http://blog.getasysadmin.com/2008/11/scalr-errors-after-install.html

and more,

> 1. Check the settings on your Core Settings->AWS settings.

I configured settings with above 1).

> 2. , Core Settings-> DNS Settings to create zones

I couldn't change Settings->Core settings->DNS settings at all,
because I couldn't understand the mean of these settings.

> 3.   Check your Core-> Application Settings to point correct event
> handler URL. Also if snmpd running?

I changed Event handler URL (Settings->Core settings->Application
settings)
from server.net to the IP-address of the host at which scalr running.
Also I installed snmpd and ran it on the host.

> 4. Settings-> Nameserver ->View All , edit your nameserver set the
> root user/password, etc.

I changed root password via ssh-terminal.
Login by admin, Settings -> Nameservers -> Add new,
and set the host at which scalr running, and root password.

After above all, I created a client and application, then launched it.
I met following message:

    Unrecoverable error
    Cannot init transport

But instances were started. I extended timeout 300->1200.
In "Instances >> View", IP-address has appeared,
and state has changed pending->Initializing, but stay Initializing,
and timed out.

What's wrong with these settings or others...
Please let me know.

Regards,
osa2

> On Dec 18, 3:20 pm, osm <[email protected]> wrote:
>
> > I got log as follows.
>
> > 18-12-2008 05:56:04     INFO  PollerProcess     Starting new instance.
> > InstanceID = i-e5358c8c.
> > 18-12-2008 05:56:03     WARN    PollerProcess   Disaster: No instances
> > running in role app!
> > 18-12-2008 05:55:05     INFO    PollerProcess   Starting new instance.
> > InstanceID = i-eb358c82.
> > 18-12-2008 05:55:05     WARN    PollerProcess   Instance 'i-51358c38' did
> > not send 'hostInit' event in 300 seconds after launch. Considering it
> > broken. Terminating instance.
> > 18-12-2008 05:55:04     INFO    PollerProcess   Starting new instance.
> > InstanceID = i-e9358c80.
> > 18-12-2008 05:55:04     WARN    PollerProcess   Disaster: No instances
> > running in role www!
> > 18-12-2008 05:55:03     WARN    PollerProcess   Disaster: No instances
> > running in role mysql!
> > 18-12-2008 05:54:05     WARN    PollerProcess   Instance 'i-5c358c35' did
> > not send 'hostInit' event in 300 seconds after launch. Considering it
> > broken. Terminating instance.
> > 18-12-2008 05:54:05     WARN    PollerProcess   Instance 'i-5e358c37' did
> > not send 'hostInit' event in 300 seconds after launch. Considering it
> > broken. Terminating instance.
> > 18-12-2008 05:49:05     INFO    PollerProcess   Starting new instance.
> > InstanceID = i-51358c38.
> > 18-12-2008 05:49:04     INFO    PollerProcess   Starting new instance.
> > InstanceID = i-5c358c35.
> > 18-12-2008 05:49:04     INFO    PollerProcess   Starting new instance.
> > InstanceID = i-5e358c37.
>
> > Thanks,
> > osa2
>
> > On 12月18ζ—₯, 午後2:40, osm <[email protected]> wrote:
>
> > > Hello,
>
> > > I have set up Scalr, and create a farm with 3 instances(www, app,
> > > mysql).
>
> > > But these instances were terminated in about 7 minutes after these
> > > instances started.
> > > And then, new instances are reborn. And these children also go down in
> > > 7 min.
> > > "Instances >> View" shows that these instances are pending at any
> > > time.
>
> > > I create a farm looking the screencast. but if some settings are
> > > wrong,
> > > please show me the right way.
>
> > > Regards,
> > > osa2

--~--~---------~--~----~------------~-------~--~----~
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