-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RabbitMQ doesn't work for App Engine apps in EC2 #2
Milestone
Comments
Note that it does work fine for a two node Xen deployment - maybe a public / private IP problem with RabbitMQ or where we point App Engine at for RabbitMQ? |
shatterednirvana
added a commit
that referenced
this issue
May 23, 2012
Turns out the problem was caused by how we start nodes with the rabbitmq_slave role - got the fix from Vaibav, tested, and verified it on two node Xen and EC2 deployments. Fixed as of 797bffc. |
shatterednirvana
pushed a commit
to shatterednirvana/appscale
that referenced
this issue
Apr 17, 2013
bring branch up to date
menivaitsi
referenced
this issue
in menivaitsi/appscale
May 19, 2014
Updated scripts to improve appscale-tools installation on Lucid
menivaitsi
referenced
this issue
in menivaitsi/appscale
May 19, 2014
cdonati
added a commit
to cdonati/appscale
that referenced
this issue
Jan 23, 2017
Obscure creds that contain full cloud ID. This fixes broken unit tests.
cdonati
pushed a commit
to cdonati/appscale
that referenced
this issue
Jan 23, 2017
Addressing code review comments
sjones4
pushed a commit
that referenced
this issue
Oct 15, 2019
Use HAProxy location for the host header
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Google App Engine apps start in Amazon EC2 in a standard two node deployment, they throw this stack trace:
Right now we just see this for Sisyphus, as it's the first App Engine app to start and it blocks all others from starting.
The text was updated successfully, but these errors were encountered: