SSH Port changed but cached somewhere
Created by: alessandroorru
I configured my ssh port to 12205 recently, and it appeared correctly on all gitlab pages. Then I changed it to 22005. Now when I reload the repository page (where I see its address) sometimes I see 12205, sometimes I see 22005. The strange thing is that this happens also on newly created project on repository address and repository setup instructions, so I think that there is a worker thread that has cached the port, but I can't find a way to reset it.
I'm using Gitlab 6.0 with unicorn
Activity
Created by: alessandroorru
I didn't notice that unicorn process was still alive after stopping both nginx and gitlab. I killed it with -QUIT signal and restarted and now it works fine, thank you.
Anyway I think that this should be managed a lot better. It's a gitlab.conf setting, so it should be managed somehow by restarting gitlab with init script (i'm using ubuntu 12.04 server).
By Administrator on 2013-08-29T15:21:15 (imported from GitLab project)
By Administrator on 2013-08-29T15:21:15 (imported from GitLab)
Created by: Razer6
@alessandroorru Can you reproduce this bahavior with restarting it again? There is a port configuration in `gitlab.conf``
By Administrator on 2013-09-01T18:15:42 (imported from GitLab project)
By Administrator on 2013-09-01T18:15:42 (imported from GitLab)
Created by: Razer6
It's been at least 2 weeks (and a new release) since we heard from you. I'm closing this issue but if you still experience this problem, please open a new issue (but also reference the old issue(s)). Make sure to also include the necessary debugging information conforming to the issue tracker guidelines found in our contributing guidelines.
By Administrator on 2013-10-13T11:25:16 (imported from GitLab project)
By Administrator on 2013-10-13T11:25:16 (imported from GitLab)
