1. Zuhause
  2. Frage und Antwort
  3. Django Sellerie Implementierung - OSError: [Errno 38] Funktion nicht implementiert

Django Sellerie Implementierung - OSError: [Errno 38] Funktion nicht implementiert

2010-07-22 7 views
10

Ich habe Django-Sellerie installiert und ich habe versucht, den Worker-Server zu starten, aber ich bekomme einen OSError, dass eine Funktion nicht implementiert ist. Ich bin mit CentOS 5.4 (Final) freigeben auf einem VPS:Django Sellerie Implementierung - OSError: [Errno 38] Funktion nicht implementiert

. broker -> amqp://[email protected]:5672/ 
    . queues -> 
     . celery -> exchange:celery (direct) binding:celery 
    . concurrency -> 4 
    . loader -> djcelery.loaders.DjangoLoader 
    . logfile -> [stderr]@WARNING 
    . events -> OFF 
    . beat -> OFF 
[2010-07-22 17:10:01,364: WARNING/MainProcess] Traceback (most recent call last): 
[2010-07-22 17:10:01,364: WARNING/MainProcess] File "manage.py", line 11, in <module> 
[2010-07-22 17:10:01,364: WARNING/MainProcess] execute_manager(settings) 
[2010-07-22 17:10:01,364: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/django/core/management/__init__.py", line 438, in execute_manager 
[2010-07-22 17:10:01,364: WARNING/MainProcess] utility.execute() 
[2010-07-22 17:10:01,364: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/django/core/management/__init__.py", line 379, in execute 
[2010-07-22 17:10:01,365: WARNING/MainProcess] self.fetch_command(subcommand).run_from_argv(self.argv) 
[2010-07-22 17:10:01,365: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/django/core/management/base.py", line 191, in run_from_argv 
[2010-07-22 17:10:01,365: WARNING/MainProcess] self.execute(*args, **options.__dict__) 
[2010-07-22 17:10:01,365: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/django/core/management/base.py", line 218, in execute 
[2010-07-22 17:10:01,365: WARNING/MainProcess] output = self.handle(*args, **options) 
[2010-07-22 17:10:01,365: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/django_celery-2.0.0-py2.6.egg/djcelery/management/commands/celeryd.py", line 22, in handle 
[2010-07-22 17:10:01,366: WARNING/MainProcess] run_worker(**options) 
[2010-07-22 17:10:01,366: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/celery-2.0.1-py2.6.egg/celery/bin/celeryd.py", line 385, in run_worker 
[2010-07-22 17:10:01,366: WARNING/MainProcess] return Worker(**options).run() 
[2010-07-22 17:10:01,366: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/celery-2.0.1-py2.6.egg/celery/bin/celeryd.py", line 218, in run 
[2010-07-22 17:10:01,366: WARNING/MainProcess] self.run_worker() 
[2010-07-22 17:10:01,366: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/celery-2.0.1-py2.6.egg/celery/bin/celeryd.py", line 312, in run_worker 
[2010-07-22 17:10:01,367: WARNING/MainProcess] worker.start() 
[2010-07-22 17:10:01,367: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/celery-2.0.1-py2.6.egg/celery/worker/__init__.py", line 206, in start 
[2010-07-22 17:10:01,367: WARNING/MainProcess] component.start() 
[2010-07-22 17:10:01,367: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/celery-2.0.1-py2.6.egg/celery/concurrency/processes/__init__.py", line 54, in start 
[2010-07-22 17:10:01,367: WARNING/MainProcess] maxtasksperchild=self.maxtasksperchild) 
[2010-07-22 17:10:01,367: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/celery-2.0.1-py2.6.egg/celery/concurrency/processes/pool.py", line 448, in __init__ 
[2010-07-22 17:10:01,368: WARNING/MainProcess] self._setup_queues() 
[2010-07-22 17:10:01,368: WARNING/MainProcess] File "/usr/local/lib/python2.6/site-packages/celery-2.0.1-py2.6.egg/celery/concurrency/processes/pool.py", line 564, in _setup_queues 
[2010-07-22 17:10:01,368: WARNING/MainProcess] self._inqueue = SimpleQueue() 
[2010-07-22 17:10:01,368: WARNING/MainProcess] File "/usr/local/lib/python2.6/multiprocessing/queues.py", line 315, in __init__ 
[2010-07-22 17:10:01,368: WARNING/MainProcess] self._rlock = Lock() 
[2010-07-22 17:10:01,368: WARNING/MainProcess] File "/usr/local/lib/python2.6/multiprocessing/synchronize.py", line 117, in __init__ 
[2010-07-22 17:10:01,369: WARNING/MainProcess] SemLock.__init__(self, SEMAPHORE, 1, 1) 
[2010-07-22 17:10:01,369: WARNING/MainProcess] File "/usr/local/lib/python2.6/multiprocessing/synchronize.py", line 49, in __init__ 
[2010-07-22 17:10:01,369: WARNING/MainProcess] sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue) 
[2010-07-22 17:10:01,369: WARNING/MainProcess] OSError 
[2010-07-22 17:10:01,369: WARNING/MainProcess] : 
[2010-07-22 17:10:01,369: WARNING/MainProcess] [Errno 38] Function not implemented

Bin ich einfach total verschraubt oder gibt es eine einfache Möglichkeit, dieses Problem zu lösen?

Quelle

2010-07-22 Jordan Messina

+0

Diese Antwort auf eine andere Frage montieren scheint, dass Multiprozessing zu zeigen, zumindest arbeiten auf CentOS 5.4: http://stackoverflow.com/questions/ 2009278/python-multiprocessing-permission-denied Sie sind wahrscheinlich nicht weit davon entfernt, es zu lösen. – asksol

Antwort

12

gleiche Problem auf ubuntu 10, auch nach der vollständigen Rechte an shmem gegeben - Problem noch hier ...

UP- endlich fertig,/dev/shm wurde nicht angebracht. so Add shm fstab shm gesetzt volle 777-Berechtigungen auf/dev/shm

Quelle

2010-09-13 09:36:40 Andrew

+0

Ich habe genau dieses Problem,/dev/shm war da, aber nicht 777, also habe ich es chmoded, aber nachdem das Problem noch besteht (Ubuntu 10.10 VPS). Irgendeine Idee, wie man es repariert (ich weiß nicht einmal, was das Problem wirklich ist)? – cerberos

+4

Es funktionierte durch Hinzufügen von 'none/dev/shm tmpfs rw, nosuid, nodev, noexec 0 0 'zu'/etc/fstab' und Neustart, habe diese Informationen von http://stackoverflow.com/questions/2009278/python -multiprocessing-permission-denied # comment-6467139 – cerberos

+2

Warum neu starten? Ist "mount -a" nicht genug? – Federico

Verwandte Themen

 Verwandte Themen