root@relay-2:~# su - celeryd -s /bin/bash -c 'baruwa-admin celeryd'
[2013-03-14 09:28:20,621: WARNING/MainProcess]
-------------- [email protected] v2.4.6
---- **** -----
--- * *** * -- [Configuration]
-- * - **** --- . broker: amqp://baruwa@localhost:5672/baruwa
- ** ---------- . loader: djcelery.loaders.DjangoLoader
- ** ---------- . logfile: [stderr]@WARNING
- ** ---------- . concurrency: 1
- ** ---------- . events: OFF
- *** --- * --- . beat: OFF
-- ******* ----
--- ***** ----- [Queues]
-------------- . default: exchange:default (direct) binding:default
. relay-2.domain.org: exchange:default (direct)
binding:relay-2.domain.org
[2013-03-14 09:28:20,657: WARNING/MainProcess] [email protected]
has started.
No errors from celeryd
Service baruwa status still reports celeryd is not running and nothing
in /var/log/baruwa/celeryd.log
On 03/14/2013 08:25 AM, Andrew Colin Kissa wrote:
On 14 Mar 2013, at 1:33 PM, Raymond Norton wrote:
root@relay-2:/var/run# ls -l /var/log/baruwa
total 0
-rw-r--r-- 1 celeryd celeryd 0 Mar 13 17:47 celeryd.log
What happens when you start it on the command line like this.
su - celeryd -s /bin/bash -c 'baruwa-admin celeryd'
--
www.baruwa.org
_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056
--
Raymond Norton
LCTN
952.955.7766
_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056
