Hi,
Timeouts are configurable in the Farm Designer (under the Advanced Tab -
Timeouts <https://scalr-wiki.atlassian.net/wiki/x/BoBM>). By default, Scalr
waits for 3600 seconds.
If your instances get terminated much faster than that, you should check
the timezone settings on your Scalr host:
- Ensure that the system timezone is set to UTC
- Ensure that MySQL uses UTC
- Ensure that PHP is configured to use UTC
You can use this code to check whether your host is properly configured:
MYSQL_ROOT_PASSWORD="Use your MySQL Root Password here"
mysql_hour=$(mysql --user=root --password="$MYSQL_ROOT_PASSWORD" --skip-
column-names --batch --execute="SELECT DATE_FORMAT(NOW(), '%H')")
php_hour=$(php -r 'echo date("H") . "\n";')
if [ "$mysql_hour" != "$php_hour" ]; then
echo "Configuration NOT OK"
else
echo "Configuration is OK"
fi
Cheers,
On Thursday, August 7, 2014 7:23:51 PM UTC+2, Aatxe Urrutia wrote:
>
> Hello I believe I am seeing the cause of an issue allot of people have
> with scalr in regards to ec2 images constantly getting recycled.
>
>
> Sometimes it works fine sometimes it just kills the nodes in less than 2
> minutes after spinning them up.
>
> I noticed that sometimes aws ec2 from the aws console even delays the
> status of the nodes i.e. doesnt pass the vm status checks and I believe
> Scalr is looking at that through the API to determine if the node is
> healthy and then recycles it.
>
> Is there a way to tell it not to make that call?
>
> The reason being is that all the cases i have seen the VM was fine, it
> actually comes up and I can ssh in and its already running puppet so there
> is no reason for scalr to constantly recycle nodes.
>
--
You received this message because you are subscribed to the Google Groups
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
