Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not all the database tables are created using CentOS install guide #110

Closed
bmaslakov opened this issue Jul 30, 2013 · 3 comments
Closed

Comments

@bmaslakov
Copy link

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:

mysql> SHOW TABLES;
+-------------------------------+
| Tables_in_gitlabhq_production |
+-------------------------------+
| deploy_keys_projects          |
| events                        |
| forked_project_links          |
| issues                        |
| keys                          |
| merge_requests                |
| milestones                    |
| namespaces                    |
| notes                         |
| projects                      |
| protected_branches            |
| services                      |
| snippets                      |
| taggings                      |
+-------------------------------+
14 rows in set (0.00 sec)

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.

@axilleas
Copy link
Contributor

@bmaslakov
Copy link
Author

Sorry. Please, excuse my carelessness.

@axilleas
Copy link
Contributor

No worries :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants