Celeryd time constraint error

Question

While running the status command I get the following error:-

Am using rabbitmq as the messaging broker

I am following this blog

 sudo /etc/init.d/celeryd status
Error: No nodes replied within time constraint

How can I Debug this error?

I have also checked this question. The answer there did not help.

django/celery - celery status: Error: No nodes replied within time constraint

Edit:-

After checking the logs of celery beat I found the following error

celerybeat raised exception <class 'gdbm.error'>: error(13, 'Permission denied')

Perhaps you don't have enough free disk space and RabbitMQ is blocking messages, resulting in the timeout? — bradley.ayers, Dec 26 '12 at 20:50
No I checked the disk space with "df - h" plenty space available. — Akash Deshpande, Dec 26 '12 at 20:53
Perhaps use strace to see what it's doing, or increase logging level to DEBUG. — bradley.ayers, Dec 26 '12 at 21:49
I think you've run the application as root inbetween. there is a write or execute right missign somewhere. Can you please check the access rights of all your files — Crazyshezy, Jan 01 '13 at 08:12
I have the exact same problem. I have set error logs to Info and can't see anything. (daemon is by default on warning). When I set it to debug I get all messages from SQS and its too much. Any idea which other path might need permissions? — Houman, Jan 29 '13 at 01:26

score 2 · Accepted Answer · answered Dec 27 '12 at 17:01

Perhaps this is caused by celery not having write permissions for the celerybeat-schedule file. The docs you linked to show celery configured to use /var/run/celerybeat-schedule as the celery beat schedule file.

Does your process have write permissions to that file? If that directory is owned by root (as it should be) and your process is running as anything other than the root user, that could cause the permission denied errors.

Check that your permissions are correct and then try deleting that file then restarting everything.

So in the end the issue was that all the log,run and the schedule files dint have write permissions properly assigned. — Akash Deshpande, Jan 29 '13 at 08:42

score 1 · Answer 2 · answered Jan 21 '15 at 07:25

Use the following command to find the problem :

C_FAKEFORK=1 sh -x /etc/init.d/celeryd start

This usually happens because there are problems in your source project(permission issues, syntax error etc.)

As mentioned in celery docs:-

If the worker starts with “OK” but exits almost immediately afterwards and there is nothing in the log file, then there is probably an error but as the daemons standard outputs are already closed you’ll not be able to see them anywhere. For this situation you can use the C_FAKEFORK environment variable to skip the daemonization step

Good Luck

Source: Celery Docs

max · Answer 3 · 2017-01-09T17:46:57.250

0

I'm having the same problem. Restarting rabbitmq fixed it:

sudo systemctl restart rabbitmq-server

and the strange thing is that I needed to wait at least 100 seconds. For me, I think there is a disk problem.

edited Jan 09 '17 at 17:46

answered Jan 09 '17 at 16:52

max

9,708
15
89
144

Celeryd time constraint error

3 Answers3