BitNami GitLab堆栈5.1.0-2重写gitlab.yml重新启动后 [英] BitNami GitLab Stack 5.1.0-2 rewrites gitlab.yml after reboot

问题描述

我正在尝试配置 BitNami GitLab Stack 5.1.0- 2 with LDAP

然后遇到问题

 无法从Ldap授权您，因为服务器192.168.133.100拒绝端口389上的连接。 
  

其中192.168.133.100实际上是gitlab服务器本身。

我更改 /opt/bitnami/apps/gitlab/htdocs/config/gitlab.yml 具有

  ldap：
 enabled：true 
 host：'192.168.1.14'
  

，但在 reboot 或GitLab重新启动后，它将返回到192.168.133.100。这是bug！

如何使BitNami GitLab Stack不这样做？

如何重新启动GitLab以使更改的gitlab.yml生效？ - >

  sudo /opt/bitnami/ctlscript.sh restart gitlab_sidekiq 
  pre> 
 
 
  https://github.com / gitlabhq / gitlabhq / issues / 3934  
 
 
 
 UPDATE重命名 / opt / bitnami / apps / gitlab / updateip 不能解决问题。
 
 
 
 UPDATE 2：问题仍然存在于5.4.0-0 
 
 
 
  sudo chmod -x /etc/init.d/bnconfig-gitlab 有帮助。
解决方案
 
您是否尝试过以下操作来禁用bncofnig-gitlab服务，而不是重命名文件？ 
  sudo chmod -x /etc/init.d/bnconfig-gitlab 
  
或
  sudo update-rc.d -f bnconfig-gitlab disable 
  
 
I am trying configure BitNami GitLab Stack 5.1.0-2 with LDAP

Then ran into problem
Could not authorize you from Ldap because "Server 192.168.133.100 refused connection on port 389".
where 192.168.133.100 is actually gitlab server itself.

I change /opt/bitnami/apps/gitlab/htdocs/config/gitlab.yml to have 
ldap:
enabled: true
host: '192.168.1.14'
, but after reboot or GitLab restart, it is back to 192.168.133.100. That is bug!

How to make BitNami GitLab Stack not to do that?

How to restart GitLab for changed gitlab.yml to take effect? -> 
sudo /opt/bitnami/ctlscript.sh restart gitlab_sidekiq
https://github.com/gitlabhq/gitlabhq/issues/3934

UPDATE Renaming /opt/bitnami/apps/gitlab/updateip doesn't solve the problem.

UPDATE 2: Problem still exists on 5.4.0-0

sudo chmod -x /etc/init.d/bnconfig-gitlab helps.
解决方案
Have you tried the following to disable the bncofnig-gitlab service instead of renaming files? 
sudo chmod -x /etc/init.d/bnconfig-gitlab
or 
sudo update-rc.d -f bnconfig-gitlab disable


                        
这篇关于BitNami GitLab堆栈5.1.0-2重写gitlab.yml重新启动后的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！