Skip to content
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

Celery Issue : Cannot start edx in sandbox on ec2 aws #1809

Closed
disisid opened this issue Dec 2, 2013 · 4 comments
Closed

Celery Issue : Cannot start edx in sandbox on ec2 aws #1809

disisid opened this issue Dec 2, 2013 · 4 comments

Comments

@disisid
Copy link

disisid commented Dec 2, 2013

hi,
I have been trying to start an edx using the config wiki on a t1.micro ec2 instance. I have followed the steps to install edx on Ubuntu precise 12.04 using ansible but could not access either lms or cms. So, I check the sys log.

Here I found this error repeating:

[service_variant=lms][celery.worker.consumer][env:sandbox] ERROR [ip-172-31-3-58 7979] [consumer.py:397] - consumer: Connection to broker lost. Tryi$
Traceback (most recent call last):
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/celery/worker/consumer.py", line 395, in start
self.consume_messages()
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/celery/worker/consumer.py", line 458, in consume_messages
poll_timeout = (fire_timers(propagate=errors) if scheduled
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/celery/worker/hub.py", line 157, in fire_timers
entry()
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/celery/utils/timer2.py", line 59, in call
return self.fun(_self.args, *_self.kwargs)
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/celery/utils/timer2.py", line 165, in _reschedules
return fun(_args, *_kwargs)
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/kombu/connection.py", line 270, in heartbeat_check
return self.transport.heartbeat_check(self.connection, rate=rate)
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/kombu/transport/pyamqp.py", line 134, in heartbeat_check
return connection.heartbeat_tick(rate=rate)
File "/edx/app/edxapp/venvs/edxapp/local/lib/python2.7/site-packages/amqp/connection.py", line 844, in heartbeat_tick
raise ConnectionError('Too many heartbeats missed')

Can anyone please help me what does this mean. Secondly, do I need to change the defaults in the json files before running ansible.

Here is the public url of the ec2 instance: http://ec2-54-254-185-46.ap-southeast-1.compute.amazonaws.com/

@disisid
Copy link
Author

disisid commented Dec 3, 2013

Can anyone please help on this. I have to launch immediately.
Thanks.

@acs022
Copy link

acs022 commented Dec 9, 2013

I'm not sure if you figured this problem out, but a micro instance is not powerful enough to run edx. Try a m1.large instance with at least 50gb of hard drive space.

@disisid
Copy link
Author

disisid commented Dec 9, 2013

Its working now actually. I am running it on a t1.micro although I have
increased the EBS volume to 30 GB.
Although the performance is a bit compromised. It is live here:
http://54.254.210.163:18010/

On Mon, Dec 9, 2013 at 10:14 PM, Adam Straubel notifications@github.comwrote:

I'm not sure if you figured this problem out, but a micro instance is not
powerful enough to run edx. Try a m1.large instance with at least 50gb of
hard drive space.


Reply to this email directly or view it on GitHubhttps://github.com/edx/edx-platform/issues/1809#issuecomment-30148215
.

@feanil
Copy link
Contributor

feanil commented Mar 24, 2014

Celery as well as elasticsearch have memory requirements that make it difficult to run the whole stack on a t1 micro. The vagrant images suggest 2GB of memory and the same is going to be true of running the whole stack on a single instance.

@feanil feanil closed this as completed Mar 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants