Just for the history, my redis configuration in gitlab-shell/config.yml was 
wrong. After using correct ip and port everything works fine. 

On Friday, February 28, 2014 10:49:07 PM UTC+2, Radoslav Asenov wrote:
>
> I almost got the same problem after upgrade to 6.6 and when I try to push 
> I receive:
> GitLab: An unexpected error occurred (redis-cli returned 1).
>
> except that got error code 1
>
> any suggestions here :)
>
>
>
> On Thursday, February 27, 2014 3:09:58 PM UTC+2, Sergey Zhukov wrote:
>>
>> I resolved the issue. The problem was in wrong path to redis-cli binary 
>> in gitlab-shell config.yml.
>> Code 127 was the bash error "command not found" 
>> http://tldp.org/LDP/abs/html/exitcodes.html
>>
>> четверг, 27 февраля 2014 г., 16:40:15 UTC+7 пользователь Sergey Zhukov 
>> написал:
>>>
>>> I installed GitLab v6.6 and tried to push commit to remote repo. But 
>>> I've got an error
>>>
>>> remote: GitLab: An unexpected error occurred (redis-cli returned 127)
>>> remote: error: hook declined to update refs/heads/master
>>>
>>> What does that mean, how can it be fixed? Also, I can't find any 
>>> additional gitlab logs related to this issue. gitlab/logs directory and 
>>> /var/log/redis6379.log seem to look fine. Where can I see additional info 
>>> about the error?
>>>
>>> And one more thing: I would like to change redis database from 0 to 
>>> another one, is it possible to change it?  
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to