I have the exact same problem, but with Scalr 2.2.1. I noticed in a previous post you referenced a guide to self-hosting - I realized I also used the same guide, and I am willing to bet the OP did as well.
It seems to me that we all may have the same issue, as a result of a single oversight in this guide. Perhaps if someone more experienced can look at it, we can all solve this issue. On May 5, 7:13 am, Enrico Detoma <[email protected]> wrote: > I have the same problem with Scalr 3.0. > Everything seems to be configured, but no instances are launched when I > launch the farm. > Running /usr/bin/php -q /var/www/app/cron-ng/cron.php --DeployManager > manually, in the log I found: > *Found 0 deployment tasks > *What should I look for, to solve the problem? > Thanks > > Il giorno giovedì 19 gennaio 2012 23:38:12 UTC+1, Dale-Kurt Murray ha > scritto: > > > > > > > > > > > I'm unable to launch AWS EC2 instances, the scalr instance has been > > configured with the 'Event handler URL' and 'Server IP address'. > > > The environment has also been configured for AWS with the account number, > > Access Key, Secret Key, X.509 Certificate file and X.509 Private Key file. > > > A farm and a app-apache-ubuntu-ebs role has been create, however when the > > farm is launched no instances are launched. > > > The cronjob are also setup, in fact I manually executed the following > > command /usr/bin/php -q /var/scalr/app/cron-ng/cron.php --DeployManager > > > If there is anything that I have missed please let me know. -- 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.
