You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was installing Gitlab on my CentOS 6.4 server, following the manual. All the setups went well, and the bundle exec rake gitlab:check RAILS_ENV=production produced everything's ok output. But, for some reason, when I first tried visit my server, I got Error 500. I checked the production.log and that's what I saw:
Connecting to database specified by database.yml
Started GET "/" for 195.160.253.4 at 2013-07-30 10:13:50 +0400
Processing by DashboardController#show as HTML
Completed 401 Unauthorized in 1ms
Started GET "/users/sign_in" for 195.160.253.4 at 2013-07-30 10:13:51 +0400
Processing by Devise::SessionsController#new as HTML
Completed 500 Internal Server Error in 21ms
ActiveRecord::StatementInvalid (Mysql2::Error: Table 'gitlabhq_production.users' doesn't exist: SHOW FULL FIELDS FROM `users`):
config/initializers/connection_fix.rb:22:in `execute'
Looks like not the all tables were created. I ckecked my guess:
I was installing Gitlab on my CentOS 6.4 server, following the manual. All the setups went well, and the
bundle exec rake gitlab:check RAILS_ENV=production
produced everything's ok output. But, for some reason, when I first tried visit my server, I got Error 500. I checked theproduction.log
and that's what I saw:Looks like not the all tables were created. I ckecked my guess:
After some investigation I ran
bundle exec rake db:migrate RAILS_ENV=production
, and the error is gone.I don't know whether it is a missed step in the installation guide or a Gitlab bug, so I am informing you.
EDIT
Yep, it is a missed step in install guide.
The text was updated successfully, but these errors were encountered: