On Tue, 28 Jun 2011 21:44:28 +0200, Andrew Colin Kissa wrote:
> On 28 Jun 2011, at 9:05 PM, Johan Hendriks wrote:
>
>>
>> /usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa/manage.py:
>> error: no such option: --uid
>
>
> you may have to run celeryd from /etc/rc until am able to provide you
> with a proper
> init script for freebsd, the generic script does not seem to do it.
>
> --
> Baruwa - www.baruwa.org
>
> _______________________________________________
> Baruwa mailing list
> [email protected]
> http://lists.baruwa.org/mailman/listinfo/baruwa
Ok i am a little further now.
if i run the following, the celeryd is starting ok and works. (as far
as i can see that is)
/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa//manage.py
celeryd_multi start beasty --uid=celery --gid=celery
'--workdir="/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa/"'
--pidfile=/var/run/celery/celeryd.pid
--logfile=/var/log/celery/celeryd.log --loglevel=INFO
--cmd=/usr/local/bin/celeryd --time-limit=300 --concurrency=8
The strange thing is that i got that line from doing a sh -x
/usr/local/etc/rc.d/celery start
it gave me this output
beasty # sh -x /usr/local/etc/rc.d/celery start
+ set -e
+ DEFAULT_PID_FILE=/var/run/celery/celeryd.pid
+ DEFAULT_LOG_FILE=/var/log/celery/celeryd.log
+ DEFAULT_CELERYD=/usr/local/bin/celeryd
+ DEFAULT_LOG_LEVEL=INFO
+ DEFAULT_NODES=celery
+ test -f /usr/local/etc/baruwa/baruwa
+ . /usr/local/etc/baruwa/baruwa
+ hostname -s
+ CELERYD_NODES=beasty
+
CELERYD_CHDIR=/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa/
+
CELERYD_MULTI='/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa//manage.py
celeryd_multi'
+ CELERYD_OPTS='--time-limit=300 --concurrency=8'
+ CELERY_CONFIG_MODULE=celeryconfig
+ CELERYD_LOG_FILE=/var/log/celery/celeryd.log
+ CELERYD_PID_FILE=/var/run/celery/celeryd.pid
+ CELERYD_USER=celery
+ CELERYD_GROUP=celery
+ export DJANGO_SETTINGS_MODULE=settings
+ CELERYD_PID_FILE=/var/run/celery/celeryd.pid
+ CELERYD_LOG_FILE=/var/log/celery/celeryd.log
+ CELERYD_LOG_LEVEL=INFO
+
CELERYD_MULTI='/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa//manage.py
celeryd_multi'
+ CELERYD=/usr/local/bin/celeryd
+ CELERYD_NODES=beasty
+ export CELERY_LOADER
+ [ -n '' ]
+ [ -n celery ]
+ DAEMON_OPTS=' --uid=celery'
+ [ -n celery ]
+ DAEMON_OPTS=' --uid=celery --gid=celery'
+ [ -n
/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa/ ]
+ DAEMON_OPTS=' --uid=celery --gid=celery
--workdir="/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa/"'
+ export
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin:/usr/local/sbin:/sbin:/usr/sbin:/usr/bin:/usr/local/bin
+ check_dev_null
+ [ ! -c /dev/null ]
+ start_workers
+
/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa//manage.py
celeryd_multi start beasty --uid=celery --gid=celery
'--workdir="/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa/"'
--pidfile=/var/run/celery/celeryd.pid
--logfile=/var/log/celery/celeryd.log --loglevel=INFO
--cmd=/usr/local/bin/celeryd --time-limit=300 --concurrency=8
celeryd-multi v2.2.6
> Starting nodes...
> beasty.beasty.double-l.local: OK
+ exit 0
If i run the file /usr/local/etc/rc.d/celery it does not work, if i use
the same command that the init script uses, it runs fine?
I do not know the difference between the 2!!!
So to sum up
using the script
beasty # /usr/local/etc/rc.d/celery start
celeryd-multi v2.2.6
> Starting nodes...
> beasty.beasty.double-l.local: OK
beasty #
I see this in the log /var/log/celery/celeryd.log
[2011-06-28 22:16:47,302: WARNING/MainProcess] --------------
[email protected]
ty.double-l.local v2.2.6
---- **** -----
--- * *** * -- [Configuration]
-- * - **** --- . broker: amqplib://guest@localhost:5672/
- ** ---------- . loader: celery.loaders.default.Loader
- ** ---------- . logfile: /var/log/celery/celeryd.log@INFO
- ** ---------- . concurrency: 8
- ** ---------- . events: OFF
- *** --- * --- . beat: OFF
-- ******* ----
--- ***** ----- [Queues]
-------------- . celery: exchange:celery (direct)
binding:celery
[Tasks]
[2011-06-28 22:16:47,315: INFO/PoolWorker-1] child process calling
self.run()
[2011-06-28 22:16:47,318: INFO/PoolWorker-2] child process calling
self.run()
[2011-06-28 22:16:47,325: INFO/PoolWorker-4] child process calling
self.run()
[2011-06-28 22:16:47,327: INFO/PoolWorker-3] child process calling
self.run()
[2011-06-28 22:16:47,328: INFO/PoolWorker-5] child process calling
self.run()
[2011-06-28 22:16:47,329: INFO/PoolWorker-6] child process calling
self.run()
[2011-06-28 22:16:47,335: INFO/PoolWorker-7] child process calling
self.run()
[2011-06-28 22:16:47,338: INFO/PoolWorker-8] child process calling
self.run()
[2011-06-28 22:16:47,340: WARNING/MainProcess]
[email protected]
al has started.
[2011-06-28 22:16:50,346: ERROR/MainProcess] Consumer: Connection
Error: Socket
closed. Trying again in 2 seconds...
And so on
For some reason it is guest@
However
if i run the following:
beasty #
/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa//manage.py
celeryd_multi start beasty --uid=celery --gid=celery
'--workdir="/usr/local/lib/python2.7/site-packages/baruwa-1.1.0-py2.7.egg/baruwa/"'
--pidfile=/var/run/celery/celeryd.pid
--logfile=/var/log/celery/celeryd.log --loglevel=INFO
--cmd=/usr/local/bin/celeryd --time-limit=300 --concurrency=8
celeryd-multi v2.2.6
> Starting nodes...
> beasty.beasty.double-l.local: OK
beasty #
Then i see this in the log.
[2011-06-28 22:22:49,961: WARNING/MainProcess] --------------
[email protected]
ty.double-l.local v2.2.6
---- **** -----
--- * *** * -- [Configuration]
-- * - **** --- . broker:
amqplib://[email protected]:5672/baruwa
- ** ---------- . loader: djcelery.loaders.DjangoLoader
- ** ---------- . logfile: /var/log/celery/celeryd.log@INFO
- ** ---------- . concurrency: 8
- ** ---------- . events: OFF
- *** --- * --- . beat: OFF
-- ******* ----
--- ***** ----- [Queues]
-------------- . beasty.double-l.local: exchange:default (direct)
binding:bea
sty.double-l.local
. default: exchange:default (direct)
binding:default
[Tasks]
. preview-message
. process-quarantine
. process-quarantined-msg
. release-message
. test-smtp-server
[2011-06-28 22:22:49,978: INFO/PoolWorker-1] child process calling
self.run()
[2011-06-28 22:22:49,982: INFO/PoolWorker-2] child process calling
self.run()
[2011-06-28 22:22:49,986: INFO/PoolWorker-3] child process calling
self.run()
[2011-06-28 22:22:49,994: INFO/PoolWorker-4] child process calling
self.run()
[2011-06-28 22:22:49,995: INFO/PoolWorker-5] child process calling
self.run()
[2011-06-28 22:22:49,999: INFO/PoolWorker-8] child process calling
self.run()
[2011-06-28 22:22:49,999: INFO/PoolWorker-7] child process calling
self.run()
[2011-06-28 22:22:49,999: INFO/PoolWorker-6] child process calling
self.run()
[2011-06-28 22:22:50,002: WARNING/MainProcess]
[email protected]
al has started.
It runs fine as far i can see.
Thanks again
regards,
Johan Hendriks
_______________________________________________
Baruwa mailing list
[email protected]
http://lists.baruwa.org/mailman/listinfo/baruwa
