following the install guide, I get no status and no app starting
Closed
following the install guide, I get no status and no app starting
Created by: pvencill
I get to here: sudo -u gitlab bundle exec rake gitlab:app:status RAILS_ENV=production in the install guide, but the app status returns nothing. I get no system output at all. I also can't start the app (again, with no errors). THe commands just return.
ANy advice?
Created by: pvencill
Sorry about that. OS is red hat 6.2, and I pulled the last stable branch of gitlab. On Sep 7, 2012 4:18 AM, "chopmann" notifications@github.com wrote:
It would be great if you could provide some Info about OS, wich version you are trying to install..that sort of stuff
— Reply to this email directly or view it on GitHubhttps://github.com/gitlabhq/gitlabhq/issues/1395#issuecomment-8359135.
By Administrator on 2012-09-07T13:21:01 (imported from GitLab project)
Created by: chopmann
maybe this guide can help you out http://howto.basjes.nl/linux/installing-gitlab-on-centos-6
I got my Gitlab 2.8 on Centos 6.3 with gitolite3 running with the help of that guide.
if capybara gives you errors...missing something:
rpm -i http://dl.atrpms.net/el6-x86_64/atrpms/stable/atrpms-repo-6-5.el6.x86_64.rpm yum install --enablerepo=atrpms-testing qt47-webkit-devel export QMAKE=/usr/bin/qmake-qt47
Install charlock_holmes version 0.6.8 - the most recent is not fully working gem install charlock_holmes --version '0.6.8' Copy the post-receive hooks to your gitolite-user( in the guide obove the user is called 'git')
sudo cp GITLAB_USER_HOME/GITLAB_DIR/lib/hooks/post-receive GITOLITE_USER_HOME/.gitolite/hooks/common/post-receive sudo chown GITOLITE_USER:GITOLITE_USER GITOLITE_USER_HOME/.gitolite/hooks/common/post-receive
if the gitolite user is asking you for a password in the following step :
Link both accounts su - gitlab ssh git@localhost exit # Back to the root account
you may need to edit your /etc/ssh/sshd Match User YOUR_GITOLITE_USER PasswordAuthentication no
If you want to try using gitolite3 make sure selinux is up to date
wget http://people.redhat.com/dwalsh/SELinux/RHEL6/noarch/selinux-policy-3.7.19-159.el6.noarch.rpm wget http://people.redhat.com/dwalsh/SELinux/RHEL6/noarch/selinux-policy-targeted-3.7.19-159.el6.noarch.rpm yum localinstall selinux-policy-3.7.19-159.el6.noarch.rpm selinux-policy-targeted-3.7.19-159.el6.noarch.rpm
Double Check Permissions and the lovely Selinux :D
By Administrator on 2012-09-07T13:48:28 (imported from GitLab project)
Created by: pvencill
Yeah, I mean that's all stuff I'd already done. What ended up working (for whatever reason) was to not start the commands w/ an inline sudo to the gitlab user like the instructions show, but to instead explicitly su to the gitlab user and then run the server startup command. No idea why, nothing in the logs or console indicating a failure. In any case, it's working for me now so thanks anyway.
By Administrator on 2012-09-11T12:17:31 (imported from GitLab project)
Created by: chopmann
I think i got the same problem trying to start gitlab at boot... Gitlab script: sudo -u gitlab sh -l -c "$CD_TO_APP_DIR && $START_DAEMON_PROCESS && $START_RESQUE_PROCESS" Had to change it to: su gitlab -l -c "$CD_TO_APP_DIR > /dev/null 2>&1 && $START_DAEMON_PROCESS && $START_RESQUE_PROCESS"
By Administrator on 2012-09-11T13:37:09 (imported from GitLab project)
Created by: Razer6
This is fixed.Please use the Support Forum for questions regarding setup troubles. :) @riyad Please close
By Administrator on 2012-12-10T22:51:38 (imported from GitLab project)
