Commits not showing on project home page. Error in sidekiq log
Created by: jimothyGator
When I push changes to a repo, the project's home page is not updated with the commit(s).
$ sudo service gitlab status
gitlab service / Unicorn with PID 2908 is running.
Gitlab service / Sidekiq with PID 2970 is running.$ sudo cat /home/git/repositories/project.git/hooks/post-receive
#!/usr/bin/env bash
# Version 4.1
# This file was placed here by GitLab. It makes sure that your pushed commits
# will be processed properly.
while read oldrev newrev ref
do
# For every branch or tag that was pushed, create a Resque job in redis.
repo_path=`pwd`
env -i redis-cli rpush "resque:gitlab:queue:post_receive" "{\"class\":\"PostReceive\",\"args\":[\"$repo_path\",\"$oldrev\",\"$newrev\",\"$ref\",\"$GL_USER\"]}" > /dev/null 2>&1
donesidekiq.log:
2013-01-25T14:28:55Z 2970 TID-1ep2ee WARN: 211
2013-01-25T14:28:55Z 2970 TID-1ep2ee WARN: can't convert String into Integer
2013-01-25T14:28:55Z 2970 TID-1ep2ee WARN: /home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/sidekiq-2.6.4/lib/sidekiq/processor.rb:39:in `[]'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/sidekiq-2.6.4/lib/sidekiq/processor.rb:39:in `block in process'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/celluloid-0.12.4/lib/celluloid/calls.rb:23:in `call'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/celluloid-0.12.4/lib/celluloid/calls.rb:23:in `public_send'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/celluloid-0.12.4/lib/celluloid/calls.rb:23:in `dispatch'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/celluloid-0.12.4/lib/celluloid/future.rb:18:in `block in initialize'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/celluloid-0.12.4/lib/celluloid/internal_pool.rb:48:in `call'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/celluloid-0.12.4/lib/celluloid/internal_pool.rb:48:in `block in create'redis-cli monitor:
1359124135.482939 [0 127.0.0.1:46823] "rpush" "resque:gitlab:queue:post_receive" "211"
1359124135.485072 [0 127.0.0.1:46768] "brpop" "resque:gitlab:queue:post_receive" "resque:gitlab:queue:mailer" "resque:gitlab:queue:system_hook" "resque:gitlab:queue:common" "resque:gitlab:queue:default" "1"Activity
Created by: jimothyGator
Why is "211" getting pushed to resque:gitlab:queue:post_receive? Looking at the post-receive hook, it looks like it should be a much large message, in a Json format.
Is an old post-receive hook getting fired somehow?
By Administrator on 2013-01-25T14:41:16 (imported from GitLab project)
By Administrator on 2013-01-25T14:41:16 (imported from GitLab)
Created by: jimothyGator
Might be relevant: I had upgraded from 4.0 to 4.1 (and before that, a long line of upgrades going back to 2.6). Perhaps with a new installation, I would not have this problem. I will test this as time permits.
By Administrator on 2013-01-29T19:25:59 (imported from GitLab project)
By Administrator on 2013-01-29T19:25:59 (imported from GitLab)
Created by: cspurk
@jimothygator I have stopped GitLab, made the change in
/home/git/.gitolite/hooks/common/post-receive(which is symlinked from our Git repositories) and started GitLab again. Then I pushed a new branch with some dummy commits. Unfortunately, the problem remains: the push activity is not shown on GitLab’s dashboard.By Administrator on 2013-02-13T09:23:54 (imported from GitLab project)
By Administrator on 2013-02-13T09:23:54 (imported from GitLab)
Created by: jimothyGator
@cspurk Which version of Redis are you running? To upgrade to Gitlab 4.1, I also had to upgrade to Redis 2.x (I am on 2.6 now). The first time I installed Gitlab (2.x?), I would up with Redis 1.x (presumably because that's what has a Debian package).
Until I both upgraded Redis (using these install instructions) and modified the
post-receivehook, I also not see activity on the dashboard.Check the Redis server version via:
redis-cli info | grep versionBy Administrator on 2013-02-14T21:57:42 (imported from GitLab project)
By Administrator on 2013-02-14T21:57:42 (imported from GitLab)
Created by: cspurk
@jimothygator We’re on Redis 2.2.12 (as packaged with Ubuntu 12.04). We have not used any other version before. So you’d suggest to install and try a newer Redis version in order to get rid of the dashboard problem?
By Administrator on 2013-02-18T17:48:40 (imported from GitLab project)
By Administrator on 2013-02-18T17:48:40 (imported from GitLab)
Created by: jimothyGator
@cspurk To be honest, I'm somewhat guessing. I know I had to upgrade to a more recent version of Redis than I was using with Resque (on Debian, incidentally). Glancing around the Sidekiq source code, it looks like it may be using some Redis 2.4 features. But I couldn't find documentation stating which version of Redis is required. So, it's worth a try.
By Administrator on 2013-02-18T21:57:13 (imported from GitLab project)
By Administrator on 2013-02-18T21:57:13 (imported from GitLab)
Created by: laradji
We have the same issue here, we use gitlab from 4.1 and we are having this problem from the start. Ubuntu 12.04.
I have this log and only this : ==> sidekiq.log <== 2013-02-22T16:20:42Z 12193 TID-d9q84 PostReceive JID- INFO: start 2013-02-22T16:20:42Z 12193 TID-d9q84 PostReceive JID- INFO: done: 0.005 sec
By Administrator on 2013-02-22T16:21:07 (imported from GitLab project)
By Administrator on 2013-02-22T16:21:07 (imported from GitLab)
Created by: jvanbaarsen
Related to #3391 (closed) ?
By Administrator on 2013-03-28T22:10:40 (imported from GitLab project)
By Administrator on 2013-03-28T22:10:40 (imported from GitLab)
Created by: supernova32
Turns out it has nothing to do with sidekiq. There is something wrong with the way gitlab-shell invokes the redis update. After removing the -i option form this line: https://github.com/gitlabhq/gitlab-shell/blob/master/lib/gitlab_update.rb#L52 it worked as expected.
By Administrator on 2013-03-30T17:01:18 (imported from GitLab project)
By Administrator on 2013-03-30T17:01:18 (imported from GitLab)
Created by: dsp84
we've exactly the same problem ... the dasboard is still not updating, but all tasks are working/running well without any errors. we can't fix it by removing the "-i", any ideas?
By Administrator on 2013-04-04T14:40:10 (imported from GitLab project)
By Administrator on 2013-04-04T14:40:10 (imported from GitLab)
Created by: supernova32
the latest commits on gitlab-shell have removed the -i option. The funny thing is, that I only see the push events on some of my projects and not all of them.
By Administrator on 2013-04-10T14:22:08 (imported from GitLab project)
By Administrator on 2013-04-10T14:22:08 (imported from GitLab)
Created by: tvb
Applied https://github.com/gitlabhq/gitlab-shell/blob/master/lib/gitlab_update.rb but no updates are showing on my dashboard. Any ideas?
By Administrator on 2013-04-24T15:59:23 (imported from GitLab project)
By Administrator on 2013-04-24T15:59:23 (imported from GitLab)
Created by: tvb
As a last option, it might. hoping @randx or @Riyad has a solution for it tho!
By Administrator on 2013-04-24T19:02:48 (imported from GitLab project)
By Administrator on 2013-04-24T19:02:48 (imported from GitLab)
Created by: Philzen
After removing the -i option form this line: https://github.com/gitlabhq/gitlab-shell/blob/master/lib/gitlab_update.rb#L52 it worked as expected.
@randx - Thanks heaps for c110d110a0078f3e22594a7c447aa0e727b88d78! This will make many people using unix-like systems very happy (see #2310)
@supernova32 - Check whether the symbolic links for the post-receive hooks are all pointing to the same directory.
By Administrator on 2013-04-25T19:12:25 (imported from GitLab project)
By Administrator on 2013-04-25T19:12:25 (imported from GitLab)
Created by: Razer6
I'm closing this now. Hopefully it's fixed. There are a couple of such issues - Happily resolved :). Report back in case of the error still exist.
By Administrator on 2013-06-30T16:59:34 (imported from GitLab project)
By Administrator on 2013-06-30T16:59:34 (imported from GitLab)
Created by: sreechok
I am using Gitlab 5.4.0.rc1 (f1fc1ae6) on Ubuntu 12.04 LTS and this issue of commits not showing on the project homepage still exists.
I read this thread and noticed that in 5.4.0 version of gitlab_update.rb file that env -i isn't there anymore.
this is the line i see in the
command = "#{config.redis_command} rpush '#{config.redis_namespace}:queue:post_receive' '{"class":"PostReceive","args":["#{@repo_path}","#{@oldrev}","#{@newrev}","#{@refname}","#{@key_id}"]}' > /dev/null 2>&1"
is the env -i shifted to some other file?
By Administrator on 2013-10-04T17:12:03 (imported from GitLab project)
By Administrator on 2013-10-04T17:12:03 (imported from GitLab)
Created by: sreechok
I could find that "env -i redis-cli" in the gitlab-shell/lib/gitlab_config.rb file in the redis_command function (line no: 51). I removed the -i from the "env" command and then restarted the gitlab. I committed a change and pushed but I still can't see the commit I just did on the gitlab ui. Since I changed a file under the gitlab-shell, is starting a gitlab server would have taken affect the change I did to gitlab_config file?
I believe Gitlab 5.4.0 is using gitlab-shell v 1.5.0 as per the instruction from https://github.com/gitlabhq/gitlabhq/blob/5-4-stable/doc/install/installation.md
Any help on this would be appreciated.
By Administrator on 2013-10-07T09:20:17 (imported from GitLab project)
By Administrator on 2013-10-07T09:20:17 (imported from GitLab)
Created by: sreechok
I ran the following command "sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production" and gitlab shell version reported as 1.7.0; everything seems to be fine.
By Administrator on 2013-10-07T09:23:40 (imported from GitLab project)
By Administrator on 2013-10-07T09:23:40 (imported from GitLab)
Created by: sreechok
I take my word back as I can see the commits on the dashboard for the project I was working on. No changes are required to the any of the files from Gitlab 5.4.0.
For some reason, the update symbolic link was missing from the project's hooks dir on the gitlab server so it never call the update. I had to create a symbolic link to
ln -s /home/git/gitlab-shell/hooks/update update sudo chown -R git:git update sudo /etc/init.d/gitlab restart
By Administrator on 2013-10-07T17:02:11 (imported from GitLab project)
By Administrator on 2013-10-07T17:02:11 (imported from GitLab)
Created by: gibletto
I had this problem for a different reason, commits didn't appear to show up, but then I realised they were there, but lower down the page. The time on the server was wrong by a few days!
By Administrator on 2014-02-26T10:12:52 (imported from GitLab project)
By Administrator on 2014-02-26T10:12:52 (imported from GitLab)
