Servers in a pending state (self-hosted)

[Dale-Kurt Murray]

I have a self-hosted scalr and server farm configured with 4 roles. When the farm is launched the server stay in a 'pending' state and the following log message is sent.

2011-11-14 23:00:09,900 - WARN [tran4ec19d737d541:Logger@827] - 'Cannot add tags to server: AWS error [https://us-east-1.ec2.amazonaws.com/]: The instance ID \'i-83039de0\' does not exist'
2011-11-14 23:00:13,900 - WARN [tran4ec19d737d541:Logger@827] - 'Cannot add tags to server: AWS error [https://us-east-1.ec2.amazonaws.com/]: The instance ID \'i-8d039dee\' does not exist'

It seems the server instances have not yet been created yet on AWS while sclar is attempting to add tags.

UPDATE

I notice that the instances are being launched and terminated (see screenshots).

Scalr - http://cl.ly/1j3C1G3u240j050A1z01
AWS EC2 - http://cl.ly/312T0Q303j392r2H2o1h

2011-11-15 04:41:04,561 - WARN [18745:Logger@235] - [FarmID: 2] Server 'a5f7cea6-f6dd-4385-8330-f7401a91703a' did not send 'hostInit' event in 2400 seconds after launch (Try increasing timeouts in role settings). Considering it broken. Terminating instance.
2011-11-15 04:41:04,561 - WARN [18745:Logger@499] - [FarmID: 2] Terminating instance 'a5f7cea6-f6dd-4385-8330-f7401a91703a' (O).
2011-11-15 04:41:05,561 - WARN [18745:Logger@235] - [FarmID: 2] Server '15a111bd-ac2e-418d-8549-6348a4a36fb3' did not send 'hostInit' event in 2400 seconds after launch (Try increasing timeouts in role settings). Considering it broken. Terminating instance.
2011-11-15 04:41:05,561 - WARN [18745:Logger@499] - [FarmID: 2] Terminating instance '15a111bd-ac2e-418d-8549-6348a4a36fb3' (O).
2011-11-15 04:41:05,561 - WARN [18745:Logger@235] - [FarmID: 2] Server '92f7ea51-d878-4fcf-8d0e-44a8805ed92a' did not send 'hostInit' event in 2400 seconds after launch (Try increasing timeouts in role settings). Considering it broken. Terminating instance.
2011-11-15 04:41:05,561 - WARN [18745:Logger@499] - [FarmID: 2] Terminating instance '92f7ea51-d878-4fcf-8d0e-44a8805ed92a' (O).
2011-11-15 04:41:06,561 - WARN [18745:Logger@235] - [FarmID: 2] Server 'ef1a878f-32d9-4668-a401-1c18614cf547' did not send 'hostInit' event in 2400 seconds after launch (Try increasing timeouts in role settings). Considering it broken. Terminating instance.
2011-11-15 04:41:06,561 - WARN [18745:Logger@499] - [FarmID: 2] Terminating instance 'ef1a878f-32d9-4668-a401-1c18614cf547' (O).

[DicsyDel]

This means that messaging between scalr and instances doesn't work.
Most likely you've not configured scalr properly. Make sure that
'Event handler URL' in Settings -> System settings configured
correctly and points to scalr server.

Regards,
Igor

On Nov 15, 4:18 pm, Dale-Kurt Murray <dalekurt.mur...@gmail.com>
wrote:

> I have a self-hosted scalr and server farm configured with 4 roles. When
> the farm is launched the server stay in a 'pending' state and the following
> log message is sent.
>
> 2011-11-14 23:00:09,900 - WARN [tran4ec19d737d541:Logger@827] - 'Cannot add
> tags to server: AWS error [https://us-east-1.ec2.amazonaws.com/]: The
> instance ID \'i-83039de0\' does not exist'
> 2011-11-14 23:00:13,900 - WARN [tran4ec19d737d541:Logger@827] - 'Cannot add
> tags to server: AWS error [https://us-east-1.ec2.amazonaws.com/]: The
> instance ID \'i-8d039dee\' does not exist'
>
> It seems the server instances have not yet been created yet on AWS while
> sclar is attempting to add tags.
>
> UPDATE
>
> I notice that the instances are being launched and terminated (see
> screenshots).
>
> Scalr -http://cl.ly/1j3C1G3u240j050A1z01

> AWS EC2 -http://cl.ly/312T0Q303j392r2H2o1h

[Dale-Kurt Murray]

Thank you, that worked!