Activity Views not updating after server move

Yesterday, I moved my Gitlab to a new server, including changing from Manual Install (former best practice for a production server) to Omnibus, from MySQL to PostgreSQL, updating from 7.7.1 to 7.12.0, and from Ubuntu 14.04 to 15.04 (yes, I know that’s not an LTS). Here’s what I did:

  1. Update the old server to 7.12.0 (and confirm that it worked properly), then do a backup using sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production.
  2. Follow the instructions here to migrate that backup to PostgreSQL.
  3. SCP the backup file to the new server.
  4. Install 7.12.0 on the new server using the Omnibus package from the repository.
  5. Restore the backup onto the new server using sudo gitlab-rake gitlab:backup:restore BACKUP=MY_TIMESTAMP.

Everything seems to be working perfectly, except for one thing: Activity views don’t seem to be updating anymore. For instance, one of our developers pushed commits to two repositories, and neither the overall activity view on the home page, nor the group activity view, nor the project activity views show these commits. However, when I go into the list of commits for the projects, I see the commits that were made.

What could be causing this? How can I fix it?

This may be related to

but it isn’t exactly the same.

Most likely an issue with hooks. Have you checked the update documenation in omnibus-gitlab?

@marin, Thanks for the link.

I had seen that page, but had been confused by the order of the documentation there, which implies that those instructions are only used for an upgrade from … (emphasis mine)

… non-Omnibus PostgreSQL to an Omnibus

I did not realize that they apply to a “non-Omnibus MySQL to Omnibus PostgreSQL” update as well.

Perhaps I would have realized if I had read the section anyway, but I originally skipped that section because I believed that it did not apply to me. Maybe we can make it a little clearer.