<p>I'm having an issue that's come up multiple times before, but none of the previous answers seem to help me here.</p>

<p>I'm running Celery (via Docker/Kubernetes) with a Redis back-end. I'm using this command:</p>

<p><code>celery worker --uid 33 -A finimize_django --loglevel=DEBUG -E</code></p>

<p>(I've just set it to debug now)</p>

<p>I am using <code>celery==4.3.0</code> and <code>redis==3.2.1</code>.</p>

<p>Whenever I run <code>celery -A app_name status</code> I get:</p>

<p><code>Error: No nodes replied within time constraint.</code></p>

<p>What's weird is Celery seems to be working fine. I can see tasks being processed, and even if I <code>monitor</code> Redis stuff seems to be running successfully. This has also been running fine in production for months, only for this to start happening last week.</p>

<p>It is causing a problem because my liveness probe kills the pod because of this error message.</p>

<p>How can I debug the underlying issue? There is nothing in the log output that is erroring.</p>

<p>Thanks!</p>

<p>As suggest here in the first answer and the issue on github downgrading kombu to version 4.6.3 itself was not enough I had to change my command a bit and use this one .. :</p>
<pre><code>timeout 120s celery inspect ping -A run:celery -b ${REDIS_URL} -d celery@$HOSTNAME
</code></pre>
<p>Notice redis URL and the hostname.</p>
