Celery fails when installed on Windows 7
Issue #119
resolved
If the openrem folder is on the Python path in a Windows install, Celery will start but all the workers will be immediately killed as they are created.
The issue is described here: https://groups.google.com/forum/?pli=1#!topic/celery-users/i4sxrsfFStc
I have filed a bug report against Celery here: https://github.com/celery/celery/issues/2247
Comments (10)
-
reporter
-
reporter
OpenREM user @dplatten has not reported having this difficulty with his OpenREM 0.4.3b3 install on Windows server 2008. I have tried it on Windows 7 Professional 64 bit as installed by HP on a laptop, and also the same OS version installed in a Virtual Machine.
-
reporter
Changed name of django project folder to openremproject, changed all references accordingly. Refs
#119.→ <<cset 4caaa930e9b9>>
-
reporter
0.4.3b7 has been installed and tested on Windows 7 x64 in a virtual environment. It worked :-)
-
reporter
0.4.3b7 has been installed and tested on Windows 7 x64 in a system wide install. It worked :-)
-
reporter
Making changes in docs from openrem --> openremproject for the inner Django project folder. Addeded comment to restart Celery in the generic release upgrade notes. Haven't tackled upgrades yet. Refs
#119.→ <<cset c01ca070926a>>
-
reporter
Updating docs for upgrade of 0.4.3b7 over earlier versions. Refs
#119.→ <<cset 6bf393b621ba>>
-
reporter
Corrected use of back-ticks to highlight folder names etc. Refs
#119.→ <<cset 81d93bad620a>>
-
reporter
0.4.3b7 has been installed and tested on Ubuntu in a site wide install as an upgrade to an earlier beta version. It worked :-)
-
reporter
- changed status to resolved
Debug mode now set to false. Docs updated to reflect debug mode and the change in the django project folder from openrem to openremproject. Fixes
#119, should fix#39.→ <<cset 62554d709c4e>>
- Log in to comment
Options are:
Option 1 might be a headache depending on how much it changes the database tables. Otherwise it will be a case of changing import arguments and all the documentation.
Option 2 might not ever happen. If it does, it might be possible to add some instructions to the documentation for Windows users to manually apply the patch. Otherwise this version of OpenREM would not be available to them until a later version of Celery was released, which we have no control over.