You can clone with
No one assigned
Hi, The mailer jobs in the resqueue just stays up in my queue and no notifications mails are being sent out, I will be glad if you can help me out. I have the lattest stable version of gitlab running.
Try ps aux, and look for the resque process, is there something like PAUSE behind it? did you make /etc/init.d/gitlab restart? if yes, see here for solution:#984
I have a same issue. For me the resque process not gets started through the init.d-script, I can't see it in ps. If I start the resque process manually all mails get sent and the web hooks are displayed.
sounds like the pidfile is owned by root, look in /home/gitlab/gitlab/tmp
Yes the pidfiles are owned by root: root@xxx:/home/gitlab/gitlab/tmp/pids# stat -c %U resque_worker.pid
What should I do against?
if you followed the tutorial, this happens. just delete it and make a /etc/init.d/gitlab start. To describe the problem: The init-script runs the resque-process as user gitlab, and this user cannot overwrite the root-user file
I dont use init scripts. Even when I run resque.sh I still have those workers lying. I use sendmail+null mailer to send mails
okay, here a checklist:
1. ps aux |grep -i resque get the id of resque, if running
2. sudo kill -QUIT RESQUE_PID shut resque down
3. sudo rm /home/gitlab/gitlab/tmp/pids/resque_worker.pid delete existing pid file
4. sudo find /home/gitlab/ -! -uid `id -u gitlab` -print0 |xargs -0r chown gitlab:gitlab Change owner if fileowner isn't gitlab <-- Warning, guarantee for nothing
5. sudo -u gitlab sh -l -c "cd /home/gitlab/gitlab > /dev/null 2>&1 && ./resque.sh" run resque as gitlab user
ps aux |grep -i resque
sudo kill -QUIT RESQUE_PID
sudo rm /home/gitlab/gitlab/tmp/pids/resque_worker.pid
sudo find /home/gitlab/ -! -uid `id -u gitlab` -print0 |xargs -0r chown gitlab:gitlab
sudo -u gitlab sh -l -c "cd /home/gitlab/gitlab > /dev/null 2>&1 && ./resque.sh"
I went well. Thank you.
Hi. I got it working. The problem was with the permissions of the resque_worker.pid. Thanks a lot guys :)
Added this to the Trouble Shooting Guide.
Thanks to @Shuro for the checklist. :)
@shuro the checklist helped me too!
I tried the command @Shuro mentioned, but it doesn't work.
While it works with the following commands:
sudo -u gitlab sh -l -c "cd /home/gitlab/gitlab && ./resque.sh > /dev/null 2>&1 "
Dunno, it's the same command, only that the output of the second command (resque.sh) get to /dev/null, you could also use
sudo -u gitlab sh -l -c "cd /home/gitlab/gitlab && ./resque.sh"