Re: django-celery connects to localhost but not by ip

[Chad Vernon]

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 auxww | grep celerycam | grep -v "grep" | awk \'{print $2}\' | 
xargs kill')
# Kill existing workers
sudo('ps auxww | grep "celery worker" | grep -v "grep" | awk \'{print 
$2}\' | xargs kill')

with cd('/usr/local/Cellar/daemonize/1.7.4/sbin'):
# Create new workers
sudo('daemonize -u pipeadmin %s/manage.py celery worker -E -B' % 
siteDir)

# Create new celerycam
sudo('rm celerycam.pid', warn_only=True)
sudo('python %s/manage.py celerycam --detach --pidfile=celerycam.pid' % 
siteDir)



On Friday, September 20, 2013 8:47:44 AM UTC-7, Celso Providelo wrote:
>
> 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:
> {{{
> run-celery:   
> 
> $(PYTHON) $(MANAGER) celerycam -l debug  --detach \
> --pidfile=celerycam.pid
> $(PYTHON) $(MANAGER) celery worker -l debug -E -B -n 
> 'local-worker' \
> --pidfile=celeryworker.pid
> }}}
>
> It is highly verbose, but might help you to visualize what is going on.
>
> []
>
>
> On Fri, Sep 20, 2013 at 1:23 AM, 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 -> 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  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...@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.
>>
>
>
>
> -- 
> Celso Providelo
> IRC: cprov,  Skype: cprovidelo
> 1024D/681B6469 C858 2652 1A6E F6A6 037B  B3F7 9FF2 583E 681B 6469
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving 

Re: django-celery connects to localhost but not by ip

[Celso Providelo]

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:
{{{
run-celery:

$(PYTHON) $(MANAGER) celerycam -l debug  --detach \
--pidfile=celerycam.pid
$(PYTHON) $(MANAGER) celery worker -l debug -E -B -n 'local-worker'
\
--pidfile=celeryworker.pid
}}}

It is highly verbose, but might help you to visualize what is going on.

[]


On Fri, Sep 20, 2013 at 1:23 AM, 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 -> 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  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.
>



-- 
Celso Providelo
IRC: cprov,  Skype: cprovidelo
1024D/681B6469 C858 2652 1A6E F6A6 037B  B3F7 9FF2 583E 681B 6469

-- 
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.

Re: django-celery connects to localhost but not by ip

[John DeRosa]

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 -> 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  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.

Re: django-celery connects to localhost but not by ip

[Chad Vernon]

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  
> 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.

Re: django-celery connects to localhost but not by ip

[John DeRosa]

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 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+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.

django-celery connects to localhost but not by ip

[Chad Vernon]

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+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.