Dashboard dead after upgraded to 4.1

Created by: mkrauser

After upgrading to 4.1, the global dashboard, as well as the namespace-specific dashboards do not show any entries. Only the project's dashboard's are working as expected.

My ruby-version is ruby 1.9.3p374

the log does not show any error:

Started GET "/" for 127.0.0.1 at 2013-01-23 09:42:06 +0100
Processing by DashboardController#index as HTML
  Rendered events/_event_last_push.html.haml (7.7ms)
  Rendered dashboard/_activities.html.haml (13.3ms)
  Rendered dashboard/_groups.html.haml (16.2ms)
  Rendered dashboard/_projects.html.haml (104.3ms)
  Rendered dashboard/_sidebar.html.haml (121.6ms)
  Rendered dashboard/index.html.haml within layouts/application (135.3ms)
  Rendered layouts/_head.html.haml (0.9ms)
  Rendered layouts/_flash.html.haml (0.1ms)
  Rendered layouts/_search.html.haml (24.9ms)
  Rendered layouts/_init_auto_complete.html.haml (5.6ms)
  Rendered layouts/_head_panel.html.haml (33.6ms)
Completed 200 OK in 193ms (Views: 171.1ms | ActiveRecord: 5.0ms)

The check-task only complains about the gitolite-version, althoug I'm using the branch gl-v320 of gitolite (like suggested in gitlab doc's).

Created by: drybjed

I'm not sure if this is the fix for your version, but check if sidekiq is running. If not, you might need to install Ruby inotify bindings (apt-get install ruby-rb-inotify).

By Administrator on 2013-01-23T21:21:03 (imported from GitLab)

Created by: mkrauser

sidekiq is running. When I remember correctly, I've had problems with sidekiq on ruby 1.9.2. Then I upgraded to 1.9.3, but that did not solve the problem with the dashboard:

31422 ?        Sl     0:12 unicorn_rails master -c /home/gitlab/gitlab/config/un
31568 ?        Sl     0:09  \_ unicorn_rails worker[0] -c /home/gitlab/gitlab/co
31731 ?        S      0:00  |   \_ python2 /home/gitlab/gitlab/vendor/bundle/rub
31570 ?        Sl     0:09  \_ unicorn_rails worker[1] -c /home/gitlab/gitlab/co
11701 ?        S      0:00      \_ python2 /home/gitlab/gitlab/vendor/bundle/rub
31504 ?        Sl     0:55 sidekiq 2.6.4 gitlab [0 of 25 busy]

I also checked the sidekiq.log, it does not show any unusual entries.

By Administrator on 2013-01-24T07:48:32 (imported from GitLab)

Created by: campbellr

I'm seeing the same issue after upgrading from 4.0 to 4.1. As far as I can tell, everything seems healthy...

By Administrator on 2013-01-29T06:55:07 (imported from GitLab)

Created by: donnykurnia

Might be related with issue #2788 (closed)

By Administrator on 2013-01-29T07:36:01 (imported from GitLab)

Created by: dzaporozhets

dashboard loaded via ajax now. Check for js errors on the page.

By Administrator on 2013-01-29T09:42:32 (imported from GitLab)

Created by: donnykurnia

Here what I do to fix the dashboard problems:

• In server, run RAILS_ENV=production bundle exec rake assets:clean
• Then compile the new assets: RAILS_ENV=production bundle exec rake assets:precompile
• Since I use cloudflare, I put my site on development mode to disable caching, wait for a moment, then shift-reload.
• Now the dashboard display the events.

By Administrator on 2013-01-29T10:39:47 (imported from GitLab)

Created by: campbellr

Yep, that fixed it for me as well. Thanks!

By Administrator on 2013-01-30T02:12:48 (imported from GitLab)

Created by: mkrauser

Thanks @donnykurnia, these two commands fixed the problem:

sudo -u gitlab -H bundle exec rake assets:clean RAILS_ENV=production
sudo -u gitlab -H bundle exec rake assets:precompile RAILS_ENV=production

Maybe there should be a hint in the upgrade-page in the wiki. This can easily be overlooked!

By Administrator on 2013-01-30T08:52:29 (imported from GitLab)

Created by: Silthus

Can you please add these two lines to the upgrade notes?

I searched for this for at least 2 hours...

By Administrator on 2013-02-04T17:25:49 (imported from GitLab)

Created by: kitingChris

For me these commands unfortunatelly did not solve the problem.

screen3 shows commits that are neither displayed on the group Dashboard nor on the global Dashboard older commits are shown correctly.

By Administrator on 2013-02-13T14:53:48 (imported from GitLab)

Created by: supernova32

I have the exact same problem with a fresh 5.0 install. I have no idea where the problem is. I hope someone can shed some light on it because its driving me crazy!

By Administrator on 2013-03-27T15:49:33 (imported from GitLab)