Skip to content Skip to sidebar Skip to footer

Running Celery As Daemon With Supervisor And Django On Elastic Beanstalk

I am attempting to get Celery to run on an EB environment with Django and I have gotten super close to getting it all running. I have this config file for supervisor #!/usr/bin/env

Solution 1:

1 - Follow the answer of this question: https://stackoverflow.com/a/41097851/3407986

2 - You must add libcurl-devel in packages eb configuration file/section, see my .ebextensions/02_packages.config file:

packages:
  yum:
    // ... your another packages where ...// add libcurl-devel, dependency of pycurl package
    libcurl-devel: []

Solution 2:

Try SSH to your instance and importing pycurl yourself, using the same python that EB is using to run your app. Then you'll see the actual error.

For example, here's what I got when I built pycurl without --global-option="--with-nss":

[root@ip-172-31-2-149 log]# /opt/python/run/venv/local/bin/python Python 3.4.3 (default, Sep 1 2016, 23:33:38) [GCC 4.8.3 20140911 (Red Hat 4.8.3-9)] on linux Type "help", "copyright", "credits" or "license" for more information. \>>> import pycurl Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: pycurl: libcurl link-time ssl backend (nss) is different from compile-time ssl backend (none/other)

Post a Comment for "Running Celery As Daemon With Supervisor And Django On Elastic Beanstalk"