Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5079

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Gitlab 6.0 : activity feed not updated with commits

Closed

Gitlab 6.0 : activity feed not updated with commits

Created by: gallart

Hi Gitlab,

Since upgrading to Gitlab 6.0, newsfeed is not getting updated with commits. It's updated with issues and comments, but commits are now showing up event if visible on the "commits" page of the project.

I've executed all the upgrade rake commands.

Thanks for your help,

Gaëtan

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: Razer6

      Is sidekiq running? What do the checks say?

      By Administrator on 2013-09-13T16:33:59 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: gallart

      System information System: Ubuntu 12.04 Current User: git Using RVM: no Ruby Version: 1.9.3p392 Gem Version: 1.8.23 Bundler Version:1.3.5 Rake Version: 10.1.0

      GitLab information Version: 6.0.2 Revision: 87ee4030 Directory: /var/git/gitlab DB Adapter: mysql2 URL: http://git.nexylan.net HTTP Clone URL: http://git.nexylan.net/some-project.git SSH Clone URL: git@git.nexylan.net:some-project.git Using LDAP: no Using Omniauth: no

      GitLab Shell Version: 1.7.0 Repositories: /var/git/repositories/ Hooks: /var/git/gitlab-shell/hooks/ Git: /usr/bin/git

      By Administrator on 2013-09-13T16:46:35 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: gallart

      sidekiq running

      By Administrator on 2013-09-13T16:46:45 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: gallart

      Uhm... Check is suggestion the following :

      *** /*** ... missing
        Try fixing it:
        sudo -u git ln -sf /var/git/gitlab-shell/hooks/post-receive /var/git/repositories/*****/puppetyaml.git/hooks/post-receive
        For more information see:
        /var/git/gitlab-shell/support/rewrite-hooks.sh
        Please fix the error above and rerun the checks.

      By Administrator on 2013-09-13T16:52:28 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: gallart

      Check is now 100% clear but still no news on feed (even after restart + redis clear).

      Gaëtan

      By Administrator on 2013-09-13T17:32:00 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: gallart

      Check output :

      Checking Environment ...
      
      Git configured for git user? ... yes
      Has python2? ... yes
      python2 is supported version? ... yes
      
      Checking Environment ... Finished
      
      Checking GitLab Shell ...
      
      GitLab Shell version >= 1.7.0 ? ... OK (1.7.0)
      Repo base directory exists? ... yes
      Repo base directory is a symlink? ... no
      Repo base owned by git:git? ... yes
      Repo base access is drwxrws---? ... yes
      post-receive hook up-to-date? ... yes
      post-receive hooks in repos are links: ... 
      
      
      ...OK
      
      Checking GitLab Shell ... Finished
      
      Checking Sidekiq ...
      
      Running? ... yes
      
      Checking Sidekiq ... Finished
      
      Checking GitLab ...
      
      Database config exists? ... yes
      Database is SQLite ... no
      All migrations up? ... yes
      GitLab config exists? ... yes
      GitLab config outdated? ... no
      Log directory writable? ... yes
      Tmp directory writable? ... yes
      Init script exists? ... yes
      Init script up-to-date? ... no
        Try fixing it:
        Redownload the init script
        For more information see:
        doc/install/installation.md in section "Install Init Script"
        Please fix the error above and rerun the checks.
      Projects have satellites? ... 
      
      ... OK
      
      Redis version >= 2.0.0? ... yes
      Your git bin path is "/usr/bin/git"
      Git version >= 1.7.10 ? ... yes (1.8.4)
      
      Checking GitLab ... Finished
      

      By Administrator on 2013-09-13T17:44:15 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: gallart

      The init script might be failing because of the "path" change to /var/ instead of /home.

      By Administrator on 2013-09-13T17:44:57 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: axilleas

      Maybe a cache:clear as described here will fix this problem?

      Unrelated with your issue, but the rake task checks the path of the rails app, init script is not hardcoded.

      By Administrator on 2013-09-14T06:03:04 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: gallart

      cache:clear does not fix the issue.

      By Administrator on 2013-09-16T07:50:42 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: gallart

      Curiously, new commits are now appearing. So, i would say : problem solved... But don't know what changed has fixed that...

      By Administrator on 2013-09-16T10:50:39 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: pacolotero

      Same problem

      By Administrator on 2014-09-04T10:55:16 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference: