Redmine

Hi,
When you ran db:migrate there were no errors? because at that moment all tables are created.
Try creating new database and run bundle exec rake db:migrate

Hi,

So based on your advice I created a new DB following these instructions:
mysql --user=root --password=root_password_mysql
create database redmine_db character set utf8;
create user 'redmine_admin''localhost' identified by 'my_password';
grant all privileges on redmine_db.* to 'redmine_admin''localhost';

Changed my database.yml file:
production:
adapter: mysql2
database: redmine_db
host: localhost
username: redmine_admin
password: my_password
encoding: utf8

This is the output. Even though there are no errors, I still think it is missing some tables like "enabled_modules" and "user_preferences":

[root@c0007776 redmine]# RAILS_ENV=production bundle exec rake db:migrate
1 Setup: migrating =======================================================
-- create_table("attachments", {:force=>true})
> 0.0062s
- create_table("auth_sources", {:force=>true})
> 0.0050s
- create_table("custom_fields", {:force=>true})
> 0.0127s
- create_table("custom_fields_projects", {:id=>false, :force=>true})
> 0.0091s
- create_table("custom_fields_trackers", {:id=>false, :force=>true})
> 0.0094s
- create_table("custom_values", {:force=>true})
> 0.0093s
- create_table("documents", {:force=>true})
> 0.0056s
- add_index("documents", ["project_id"], {:name=>"documents_project_id"})
> 0.0189s
- create_table("enumerations", {:force=>true})
> 0.0059s
- create_table("issue_categories", {:force=>true})
> 0.0063s
- add_index("issue_categories", ["project_id"], {:name=>"issue_categories_project_id"})
> 0.0137s
- create_table("issue_histories", {:force=>true})
> 0.0061s
- add_index("issue_histories", ["issue_id"], {:name=>"issue_histories_issue_id"})
> 0.0107s
- create_table("issue_statuses", {:force=>true})
> 0.0078s
- create_table("issues", {:force=>true})
> 0.0144s
- add_index("issues", ["project_id"], {:name=>"issues_project_id"})
> 0.0134s
- create_table("members", {:force=>true})
> 0.0066s
- create_table("news", {:force=>true})
> 0.0053s
- add_index("news", ["project_id"], {:name=>"news_project_id"})
> 0.0207s
- create_table("permissions", {:force=>true})
> 0.0057s
- create_table("permissions_roles", {:id=>false, :force=>true})
> 0.0078s
- add_index("permissions_roles", ["role_id"], {:name=>"permissions_roles_role_id"})
> 0.0112s
- create_table("projects", {:force=>true})
> 0.0179s
- create_table("roles", {:force=>true})
> 0.0177s
- create_table("tokens", {:force=>true})
> 0.0088s
- create_table("trackers", {:force=>true})
> 0.0076s
- create_table("users", {:force=>true})
> 0.0055s
- create_table("versions", {:force=>true})
> 0.0058s
- add_index("versions", ["project_id"], {:name=>"versions_project_id"})
> 0.0115s
- create_table("workflows", {:force=>true})
-> 0.0140s
1 Setup: migrated (0.5236s) ==============================================

Hi,
is that all the output of db:migrate?
if yes then it seems to be incomplete. there must be a problem with db:migrate

Yes, this is all the output. I also believe this is incomplete but I am not sure why.

Others I work with have encountered the same issues. It seems that the "schema.rb" file in <redmine path>/db (in my case /var/www/redmine/db/schema.rb) only lists those tables that you see in the above output.
If I go down another folder (/var/www/redmine/db/migrate) I see a whole bunch of .rb files but I don't know how to use them or even if I should. If these are supposed to be automatically included in the db:migrate then it is not working.

I am attaching my schema.rb file. Perhaps someone can compare with theirs to see if this file is missing anything.

Hi,
Try running
RAILS_ENV=production bundle exec rake db:migrate:reset

I uploaded my schema.rb for comparison.

Thanks, this started me on the right path. The command above did not work by itself; it simply reset my database to the tables that are in the schema.rb file which only contained the default ~24 tables.

So basically my schema.rb file never got updated with the additional rb file/classes in /var/www/redmine/db/migrate. There are some couple hundred or so classes that need to get loaded. My work around was this:

I dropped the tables to get a fresh start
/opt/apps/www/redmine/bin/rake db:drop

Created:
/opt/apps/www/redmine/bin/rake db:create

Migrated:
/opt/apps/www/redmine/bin/rake db:migrate

Then in order to get all of the new modifications, I performed this command for each rb file in the migrate path mentioned above.
/opt/apps/www/redmine/bin/rake db:migrate:up VERSION=001 --trace
/opt/apps/www/redmine/bin/rake db:migrate:up VERSION=002 --trace
/opt/apps/www/redmine/bin/rake db:migrate:up VERSION=003 --trace
etc... until the last ones...
/opt/apps/www/redmine/bin/rake db:migrate:up VERSION=20150113213955 --trace
/opt/apps/www/redmine/bin/rake db:migrate:up VERSION=20150208105930 --trace

This finally updated my schema.rb file and the database. My redmine is working now but I am not sure why it didn't work in the first place and required this work around.

Thanks for the help!

One last note in case this is confusing to anyone - You may notice two different paths:
/var/www/redmine
/opt/apps/www/redmine

These are pointing to the same location as they are sym-linked.