title: Celery: stuck in infinitly repeating timeouts (Timed out waiting for UP message)
body: <p>I defined some tasks with a time limit of 1200:</p>
  
  <pre><code>@celery.task(time_limit=1200)
  def create_ne_list(text):
      c = Client()
      return c.create_ne_list(text)
  </code></pre>
  
  <p>I'm also using the <code>worker_process_init</code> signal to do some initialization, each time a new process starts:</p>
  
  <pre><code>@worker_process_init.connect
  def init(sender=None, conf=None, **kwargs):
      init_system(celery.conf)
      init_pdf(celery.conf)
  </code></pre>
  
  <p>This initialization function takes several seconds to execute.</p>
  
  <p>Besides that, I'm using the following configuration:</p>
  
  <pre><code>CELERY_RESULT_SERIALIZER = 'json'
  CELERY_TASK_SERIALIZER = 'json'
  CELERY_ACCEPT_CONTENT = ['json']
  BROKER_URL = 'amqp://'
  CELERY_RESULT_BACKEND = 'amqp://'
  CELERY_TIMEZONE = 'Europe/Berlin'
  CELERY_ENABLE_UTC = True
  </code></pre>
  
  <p>and start my worker with the following command:</p>
  
  <pre><code>celery -A isc worker -l info --concurrency=3
  </code></pre>
  
  <p>As expected, starting the worker results in the initialization function being called three times. Now, I can send tasks and they are being executed and everything seems to run smoothly. </p>
  
  <p>BUT: As soon as a tasks exceeds its time limit, the worker gets caught in an infinite loop of spawning and being killed off again because of exceeding the time limit.</p>
  
  <pre><code>[2014-06-13 09:46:18,978: ERROR/MainProcess] Timed out waiting for UP message from &lt;Worker(Worker-20381, started daemon)&gt;
  [2014-06-13 09:46:20,000: ERROR/MainProcess] Process 'Worker-20381' pid:18953 exited with 'signal 9 (SIGKILL)'
  // new worker 20382 getting started, initialization getting triggerd and soon after that --&gt;
  [2014-06-13 09:46:18,978: ERROR/MainProcess] Timed out waiting for UP message from &lt;Worker(Worker-20382, started daemon)&gt;
  [2014-06-13 09:46:20,000: ERROR/MainProcess] Process 'Worker-20382' pid:18954 exited with 'signal 9 (SIGKILL)'
  // and so on....
  </code></pre>
  
  <p>Does anyone has an idea why this is happening?</p>