Nope… Good luck! On Sep 19, 2013, at 9:23 PM, Chad Vernon <chadver...@gmail.com> 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 -> 127.0.0.1:5672) > > So if that is stating the obvious, I assumed it was blocking all other ips. > So I found this page > http://superuser.com/questions/464311/open-port-5672-tcp-for-access-to-rabbitmq-on-mac > and removed NODE_IP_ADDRESS from rabbitmq-env.conf and that seems to work. > But I guess my first assumption was incorrect about what the log displayed > because when I run the command again, the log just says my machine connected > and displays the port range of that ip address. > > However, one issue that still is strange is that the ASyncResult returned > from the task always seems to return False from the .ready() method even > though it seems to have completed the task. Any ideas on that? > > > On Thursday, September 19, 2013 7:36:41 PM UTC-7, John DeRosa (work) wrote: > 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 <chadv...@gmail.com> wrote: > >> 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. But >> to test first I am doing it all on the same machine. But as I said it >> doesn't seem to work when I change from localhost to the machine ip. I just >> get socket.error: [Errno 61] Connection refused. >> >> Any ideas? >> >> Thanks, >> Chad >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users...@googlegroups.com. >> To post to this group, send email to django...@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-users. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
