Yet another bug with the Bitnami GitLab appliance.

As I’ve been moving code/content over to the GitLab instance, I’ve been encountering two annoyances # No commits are showing on the activity feed # Every time I try to push a change to the repo, I get the following error: “remote: GitLab: An unexpected error occurred (redis-cli returned 1).”

This isn’t critical functionality (the code safely gets committed), but its annoying nevertheless.

It turns out that Bitnami is shipping a broken redis/gitlab-shell config in the appliance. By broken, I mean “not in agreement”. As configured in the appliance, the gitlab-shell config expects to talk to a unix socket, but the redis server is not configured to use a unix socket.

The fix I went with, is to change the gitlab-shell config (/opt/bitnami/apps/gitlab/gitlab-shell/config.yml)

Before:

# Redis settings used for pushing commit notices to gitlab
redis:
  bin: /opt/bitnami/redis/bin/redis-cli
  # host: 127.0.0.1
  # port: 6379
  # pass: redispass # Allows you to specify the password for Redis
  database: 0
  socket: /var/run/redis/redis.sock # Comment out this line if you want to use TCP
  namespace: resque:gitlab

After:

# Redis settings used for pushing commit notices to gitlab
redis:
  bin: /opt/bitnami/redis/bin/redis-cli
  host: 127.0.0.1
  port: 6379
  # pass: redispass # Allows you to specify the password for Redis
  database: 0
  # socket: /var/run/redis/redis.sock # Comment out this line if you want to use TCP
  namespace: resque:gitlab