ask/celery — Issue #627: Celery 2.5.0 workers immediately shut down
Author: lsemel
Created: 2012-02-29 20:58:12+00:00
State: open

When using CELERYD_FORCE_EXECV = True setting, workers start and immediately shut down with an error:

2012-02-29 15:57:06,705: DEBUG/PoolWorker-111] Process PoolWorker-111:
[2012-02-29 15:57:06,705: DEBUG/PoolWorker-111] Traceback (most recent call last):
[2012-02-29 15:57:06,705: DEBUG/PoolWorker-111] File "/usr/lib/python2.6/multiprocessing/process.py", line 232, in _bootstrap
[2012-02-29 15:57:06,705: DEBUG/PoolWorker-111] self.run()
[2012-02-29 15:57:06,705: DEBUG/PoolWorker-111] File "/usr/lib/python2.6/multiprocessing/process.py", line 88, in run
[2012-02-29 15:57:06,720: DEBUG/PoolWorker-111] self._target(*self._args, **self._kwargs)
[2012-02-29 15:57:06,721: DEBUG/PoolWorker-111] File "/opt/virtualenvs/muckrack/lib/python2.6/site-packages/celery/concurrency/processes/pool.py", line 192, in worker
[2012-02-29 15:57:06,721: DEBUG/PoolWorker-111] if sentinel is not None and sentinel.is_set():
[2012-02-29 15:57:06,721: DEBUG/PoolWorker-111] File "/usr/lib/python2.6/multiprocessing/synchronize.py", line 279, in is_set
[2012-02-29 15:57:06,722: DEBUG/PoolWorker-111] self._cond.release()
[2012-02-29 15:57:06,722: DEBUG/PoolWorker-111] ValueError: semaphore or lock released too many times
[2012-02-29 15:57:06,722: INFO/PoolWorker-111] process exiting with exitcode 1