If you chowned directories in the Omnibus install I would recommend reinstalling GitLab completely.
Best regards, Sytse Sijbrandij CEO GitLab B.V. On Fri, Nov 14, 2014 at 2:10 AM, Rob Brown <[email protected]> wrote: > I had set up the omnibus install, and had it working, but then needed to > change the uid of the gitlab-www user due to a conflict. > I chown'd the appropriate directories (or so I thought), and saw an error in > nginx regarding not being able to access: > /var/opt/gitlab/gitlab-rails/sockets/gitlab.socket > so based on some posts i read here, removed it, then did a gitlab-ctl > reconfigure and restart, but the socket did not get re-created. > How does that socket get (re)created if need be? > > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/43c1d15d-9ac7-485b-ab6e-28f83f7477ec%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CAJTzhG-3W0SEaDToNggUSdczDq4NjZFKyEnkK9Ayd4_aZQkCYw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
