I just installed RabbitMQ in my local machine (ubuntu 10.10, postgres
8.4.8 and rabbitmq 1.8.0, other stuff is the same version) and
everything worked fine (great!).
So I tried to do the same with the dev environment (centos 5.0 final,
rabbitmq 1.7.2 from epel repo). We have 6 machines: 2 cds (where tasks
are executed), 2 cms and 2 db (master/slave, so only master
accessible).
I have tried different RabbitMQ configuration: just in db master host,
in both cds hosts, in all hosts... no way. Always getting same error:
[2011-05-16 14:20:12,084: WARNING/PoolWorker-1] /usr/lib/python2.6/
site-packages/celery-2.2.4-py2.6.egg/celery/worker/job.py:114:
UserWarning: Exception outside body: <class
'psycopg2.InterfaceError'>: connection already closed
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/celery-2.2.4-py2.6.egg/celery/
worker/job.py", line 108, in execute_safe
return self.execute(*args, **kwargs)
File "/usr/lib/python2.6/site-packages/celery-2.2.4-py2.6.egg/celery/
worker/job.py", line 129, in execute
self.loader.on_process_cleanup()
File "/usr/lib/python2.6/site-packages/django_celery-2.2.4-py2.6.egg/
djcelery/loaders.py", line 67, in on_process_cleanup
self.close_database()
File "/usr/lib/python2.6/site-packages/django_celery-2.2.4-py2.6.egg/
djcelery/loaders.py", line 47, in close_database
return django.db.close_connection()
File "/usr/lib/python2.6/site-packages/django/db/__init__.py", line
85, in close_connection
conn.close()
File "/usr/lib/python2.6/site-packages/django/db/backends/
__init__.py", line 244, in close
self.connection.close()
InterfaceError: connection already closed
None
So now, I'm not sure if this is a matter of architecture, version bug
or the connector is not working properly.
BTW, we are not using any db middleware (pgpool or pgbouncer mainly)
Any hint before moving to MySQL?
Otto.
On May 13, 8:21 pm, Shawn Milochik <[email protected]> wrote:
> Are you using RabbitMQ as a backend? We're using both Celery and
> django-celery successfully with Django + Postgres and I've never seen
> the issue you describe. We do all our Celery stuff asynchronously, since
> the main point (for us) is to have the user's page load time as short as
> possible.
>
> Shawn
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
