| Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now! |      |
Has anyone experienced this error when attempt a git push on a new instance of gitlab? Everything else appears to be functional:
$ git push origin testing
Total 0 (delta 0), reused 0 (delta 0)
remote: GitLab: An unexpected error occurred (redis-cli returned 1).
To git@gns-gitlab.cloudapp.net:gnsase/test-project-1.git
* [new branch] testing -> testing
-
created
Oct 8, '14 -
last post
Oct 27, '14 - 11
posts
- 619
views
- 4
users
- 2
likes
Hello @00000zerosignal00000.
What Gitlab version are you using? We were able to reproduce this issue on Gitlab 7.3.2 Cloud Image and we are going to take a look into this.
We will update this post with any information about this issue.
Best regards.
David.
Hello,
Yes it was the latest image. Do you know of a previous safe image I can attempt to use for the time being?
Regards
I have reverted to a previous build image (7.2.1.1) and have found a difference in your default redis configuration for gitlab-shell.
This is the old config:
Redis settings used for pushing commit notices to gitlab
redis: bin: /opt/bitnami/redis/bin/redis-cli host: 127.0.0.1 port: 6379 # socket: /tmp/redis.socket # Only define this if you want to use sockets namespace: resque:gitlab In your new build, you have host and port commented out, with socket uncommented. This is the only main difference within configuration I have been able to find thus far.
Hi @00000zerosignal00000.
Could you please try with this configuration?
Best regards.
David.
Hello @asce
Being pressed for time I have had to rollback to an older version, so I no longer have this configuration setup any longer. I will see about maybe spinning up another copy with this image, but I am unsure when I will have the time. Sorry about that...
Hello @00000zerosignal00000.
Thank you very much, you do not have to worry about that.
We will reproduce the issue on our side and let you know about the fix.
Best regards.
David.
I had that exact same problem.
I tried the old redis setup from config.yml, supposed by @00000zerosignal00000
redis:
bin: /opt/bitnami/redis/bin/redis-cli
host: 127.0.0.1
port: 6379
# socket: /tmp/redis.socket # Only define this if you want to use sockets
namespace: resque:gitlab
Thanks for this fix @mvagusta_ago , let's see if it helps @00000zerosignal00000
I no longer had this issue since I had reverted my version back to a previous build. I believe this was a regression within this build though, as it seemed to help @mvagusta_ago
Thanks for your other fix.
If you find more issues, don't hesitate to ask us about them.
评论区