Mike, with those settings removed I'm still getting the same errors.
And I'm now trying to do everything from scratch in a new server without
virtualenv. Could somebody please help with the last issue I need to fix? I
raised a stack overflow question here -
http://stackoverflow.com/questions/16970
Mike,
Thanks for the last reply! That gives some clarity. So I put the following
settings in my settings file.
_
BROKER_URL = "amqp://:@localhost:5672/"
CELERY_RESULT_BACKEND = "database"
CELERY_RESULT_DBURI =
"postg
Mike,
Please find my replies below.
On 5 June 2013 20:27, Mike wrote:
> Thats why I installed it using the package provided in my Ubuntu linux
> server. Then I used the template .conf file (I think from the celery
> documentation) and customized it for my project. I did have some trouble
> to
Thanks for the reply Mike. I've been trying to setup supervisord for 4
hours now. Just for this celery. I don't know where I'm going wrong. Looks
like nobody else is having a problem.
On 5 June 2013 19:13, Mike wrote:
> Have you tried supervisord? I installed supervisord from my linux distro
>
jango-celery
> both are installed in the same virtualenv and not globally?
>
>
> On Tue, Jun 4, 2013 at 4:36 PM, manuga...@gmail.com
> wrote:
>
>> Yeah Vineet,
>>
>> I've gone through that. I mentioned it in the first question on SO. You
>> will ev
Yeah Vineet,
I've gone through that. I mentioned it in the first question on SO. You
will even see my settings there.
Regards,
On 4 June 2013 15:55, Vineet Naik wrote:
> Hi Manu,
>
> Have you seen the "Running the worker as a daemon" section of celery docs
> - http://docs.celeryproject.org/en
6 matches
Mail list logo
