AMQP Messaging, Task, and Queue handling in Python using Celery. ()

zvikico | 9 Jun 2012 00:06

Mismatching definition for 'celeryd.pidbox' in celery-cam

Hi,

I updated today to the latest Celery release (2.5.5). I'm using celery with Django-celery (2.5.5) and RabbitMQ.

For some reason, the Celery-cam process is not working anymore. It seems that the 'celeryd.pidbox' exchange is not defined correctly there.

On the RabbitMQ server I'm gettings:

{amqp_error,precondition_failed,

"cannot redeclare exchange 'celeryd.pidbox' in vhost 'myhost' with different type, durable, internal or autodelete value",

'exchange.declare'}

On the cam server, I'm getting:

SchedulingError: Couldn't apply scheduled task update-aggregates: 'NoneType' object has no attribute 'method_writer'

(Googling it seems to point to the same issue of mismatching definitions)

I should point out that I have many celeryd servers and one beat server, all working happily.

To be on the safe side, I completely erased the RabbitMQ mnesia directory and recreated my vhost from scratch. Still same problem.

Is it a bug? Am I missing something on my end.

Thanks,

--
You received this message because you are subscribed to the Google Groups "celery-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/celery-users/-/ZLvDyiKNT7YJ.
To post to this group, send email to celery-users-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to celery-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/celery-users?hl=en.

headers

Ask Solem | 9 Jun 2012 11:15

Re: Mismatching definition for 'celeryd.pidbox' in celery-cam


On 8 Jun 2012, at 23:06, zvikico wrote:

> Hi,
> 
> I updated today to the latest Celery release (2.5.5). I'm using celery with Django-celery (2.5.5) and RabbitMQ.
> 
> For some reason, the Celery-cam process is not working anymore. It seems that the 'celeryd.pidbox'
exchange is not defined correctly there. 
> 
> On the RabbitMQ server I'm gettings:
> 
> {amqp_error,precondition_failed,
>             "cannot redeclare exchange 'celeryd.pidbox' in vhost 'myhost' with different type, durable, internal
or autodelete value",
>             'exchange.declare'} 
> 
> On the cam server, I'm getting:
> SchedulingError: Couldn't apply scheduled task update-aggregates: 'NoneType' object has no
attribute 'method_writer'
> (Googling it seems to point to the same issue of mismatching definitions)
> 
> I should point out that I have many celeryd servers and one beat server, all working happily. 
> To be on the safe side, I completely erased the RabbitMQ mnesia directory and recreated my vhost from
scratch. Still same problem.
> 
> Is it a bug?  Am I missing something on my end.

Hey,

I'm sorry, celery 2.5.5 is only a dummy release that changes
the kombu version requirements so that it won't force upgrade you to
Kombu 2.2.0.

Somehow it seems that you have ended up with kombu 2.2 anyway,
(which is a mystery).

You can downgrade to kombu 2.1.8:

$ pip install kombu==2.1.8

The celerycam problem you're having, could you open
up an issue for that?  (it will probably be fixed if you downgrade
to kombu 2.1.8, but it may be a regression).

(The changelog for kombu 2.2 is here:
http://kombu.readthedocs.org/en/latest/changelog.html#version-2-2-0)

--

-- 
Ask Solem
twitter.com/asksol | +44 (0)7713357179

headers

zvikico | 12 Jun 2012 01:32

Re: Mismatching definition for 'celeryd.pidbox' in celery-cam

That explains a lot. If I recall correctly, I was actually upgrading my cam/beat box from 2.4.4 to 2.5.3 and then to 2.5.5, while the workers jumped from 2.4.4 to 2.5.5. The cam box had kombu 2.2 while the workers had 2.1.8. Downgrading to 2.1.8 solved the problem on the beat part.

So I'm guessing there's no need to open an issue on that.

Thanks for the response.

Z

On Saturday, June 9, 2012 2:15:47 AM UTC-7, Ask Solem wrote:

On 8 Jun 2012, at 23:06, zvikico wrote:

> Hi,
>
> I updated today to the latest Celery release (2.5.5). I'm using celery with Django-celery (2.5.5) and RabbitMQ.
>
> For some reason, the Celery-cam process is not working anymore. It seems that the 'celeryd.pidbox' exchange is not defined correctly there.
>
> On the RabbitMQ server I'm gettings:
>
> {amqp_error,precondition_failed,
> "cannot redeclare exchange 'celeryd.pidbox' in vhost 'myhost' with different type, durable, internal or autodelete value",
> 'exchange.declare'}
>
> On the cam server, I'm getting:
> SchedulingError: Couldn't apply scheduled task update-aggregates: 'NoneType' object has no attribute 'method_writer'
> (Googling it seems to point to the same issue of mismatching definitions)
>
> I should point out that I have many celeryd servers and one beat server, all working happily.
> To be on the safe side, I completely erased the RabbitMQ mnesia directory and recreated my vhost from scratch. Still same problem.
>
> Is it a bug? Am I missing something on my end.

Hey,

I'm sorry, celery 2.5.5 is only a dummy release that changes
the kombu version requirements so that it won't force upgrade you to
Kombu 2.2.0.

Somehow it seems that you have ended up with kombu 2.2 anyway,
(which is a mystery).

You can downgrade to kombu 2.1.8:

$ pip install kombu==2.1.8

The celerycam problem you're having, could you open
up an issue for that? (it will probably be fixed if you downgrade
to kombu 2.1.8, but it may be a regression).

(The changelog for kombu 2.2 is here:
http://kombu.readthedocs.org/en/latest/changelog.html#version-2-2-0)

--
Ask Solem
twitter.com/asksol | +44 (0)7713357179

--
You received this message because you are subscribed to the Google Groups "celery-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/celery-users/-/jAwroHYFjC8J.
To post to this group, send email to celery-users-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to celery-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/celery-users?hl=en.