According to the answer in my Google Groups post you can (or not) start poller via
sudo service resque-worker start
if you have installed gitorious via ce-installer. In my case the setup is a weird mix up with ce-installer and custom repair work. So this does not work for me (service unknown).
But the resque-worker
leads to /etc/init/resque-worker.conf
.
If you look inside /etc/init/resque-worker.conf
:
description "Run a Resque worker on all queues"
author "Marius Mårnes Mathiesen <marius@gitorious.com>"
start on started rc RUNLEVEL=[35]
stop on runlevel [06]
env PATH=/bin:/usr/bin:/usr/local/bin
env QUEUE=*
env PIDFILE=/var/www/gitorious/app/tmp/pids/resque-worker1.pid
exec /usr/local/bin/chruby-exec ruby-1.9.3-p448 -- /var/www/gitorious/app/bin/rake resque:work
respawn
Now i've temporary executed QUEUE=* /var/www/gitorious/app/bin/rake resque:work
which started inside the current terminal.
According to the ./script/diagnose
the poller is now running and I'm receiving notification mails and the activity stream is updated.
The last step (hopefully) is to repair the script, to run it as service. I will update this post ASAP.
In ce-installer/upgrade.sh
, line 71 (function start-gitorious) I've found the solution to start the resque-worker
. Just type:
start resque-worker
(not !sudo service resque-worker start
)