I wasn't running celerycam, but now I am. I also wasn't using the -E -B
flags. The result is still False though but in the Django Admin, the task
has a state of SUCCESS.
I don't know if it matters or not, but this is how I am starting my
workers, celerycam through Fabric:
sudo('ps auxw
Hi Chad,
Are you running a celery worker instance ? (`manage.py celery worker -E -B`)
You also have to run `manage.py celerycam` in order to see celery
action/history in the django admin interface
I use the following makefile rule in order to activate djcelery in
development environments:
{{{
ru
Nope… Good luck!
On Sep 19, 2013, at 9:23 PM, Chad Vernon wrote:
> Thanks, I found the issue after checking the logs.
>
> I saw in the log that it listed the AMQP connection that it accepts:
>
> =INFO REPORT 19-Sep-2013::20:52:57 ===
> accepting AMQP connection <0.403.0> (127.0.0.1:59930 -
Thanks, I found the issue after checking the logs.
I saw in the log that it listed the AMQP connection that it accepts:
=INFO REPORT 19-Sep-2013::20:52:57 ===
accepting AMQP connection <0.403.0> (127.0.0.1:59930 -> 127.0.0.1:5672)
So if that is stating the obvious, I assumed it was blocking
First things to check:
Check the firewall on the RabbitMQ server. Can you access that server?
Did you set up the vhost and account on the RabbitMQ server?
Look in the RabbitMQ logs. Did the request make it to RabbitMQ?
John
On Sep 19, 2013, at 7:34 PM, Chad Vernon wrote:
> I am using djceler
I am using djcelery and rabbitmq. Everything runs fine when the
BROKER_HOST is localhost but when I change it to the ip of the machine it
no longer runs.
Basically I am trying to be able to run python commands on a separate
machine to be picked up by the RabbitMQ server on a different machine. B
6 matches
Mail list logo
