Is there any way to upgrade the database scheme manually so I get my sites up again?
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [14 Dicembre 2016, 3:23pm UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/2 "2016-12-14T15:23:18Z")
Did you run the migrations on your data container before rebuilding the web container?
---
### Author:  [@fuerst](https://meta.discourse.org/u/fuerst)
#### Post date: [14 Dicembre 2016, 3:25pm UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/3 "2016-12-14T15:25:40Z")
No because I thought that is taken care of in the web containers YAML file by this hook:
```plaintext
after_bundle_exec:
- exec: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate
```
If not: how am I supposed to migrate the data container?
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [14 Dicembre 2016, 3:30pm UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/4 "2016-12-14T15:30:35Z")
Does rebuilding again fail as well?
Otherwise, we’re need to check if the migrations ran by running the following query in Postgres
`SELECT * FROM schema_migration_details WHERE name = 'AddUploadsToCategories';`
---
### Author:  [@fuerst](https://meta.discourse.org/u/fuerst)
#### Post date: [14 Dicembre 2016, 3:36pm UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/5 "2016-12-14T15:36:59Z")
Rebuilding again fails as well. Did it 4 times.
The SELECT statement yields 0 records:
```plaintext
discourse_kulturladen=# SELECT * FROM schema_migration_details WHERE name = 'AddUploadsToCategories';
id | version | name | hostname | git_version | rails_version | duration | direction | created_at
----+---------+------+----------+-------------+---------------+----------+-----------+------------
(0 rows)
```
---
### Author:  [@fuerst](https://meta.discourse.org/u/fuerst)
#### Post date: [14 Dicembre 2016, 3:38pm UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/6 "2016-12-14T15:38:13Z")
BTW: At the default multi site the migration did run:
```plaintext
discourse=# SELECT * FROM schema_migration_details WHERE name = 'AddUploadsToCategories';
id | version | name | hostname | git_version | rails_version | duration | direction | created_at
-----+----------------+------------------------+--------------+------------------------------------------+---------------+----------+-----------+----------------------------
695 | 20161202034856 | AddUploadsToCategories | d1bcdd8eb4d7+| 20f9aad539bc4929f9149ddf989fc8abb69329d3 | 4.2.7.1 | 129 | up | 2016-12-14 14:10:12.342404
| | | | | | | |
(1 row)
```
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [14 Dicembre 2016, 4:10pm UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/7 "2016-12-14T16:10:03Z")
Try running multisite:migrate manually.
---
### Author:  [@fuerst](https://meta.discourse.org/u/fuerst)
#### Post date: [14 Dicembre 2016, 4:30pm UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/8 "2016-12-14T16:30:01Z")
I tried from within the data container. It’s code stays at 9th of Dec though (02b21a26ddfe48536251276c235c6c9ac9a7227a).
I probably need to run it from the web container which I can not access because the rebuild failed.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [15 Dicembre 2016, 2:30am UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/9 "2016-12-15T02:30:40Z")
Hmm ok I think I see where the problem is.
>
You’re only running `multisite:migrate` after the `bundle exec` hook but during the hook, assets are already being precompiled when the multisite DB hasn’t been migrated yet. To work around the problem, can you change your template to something like
```plaintext
before_bundle_exec:
- exec: su discourse -c 'bundle install --deployment --verbose --without test --without development'
- exec: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate
```
---
### Author:  [@fuerst](https://meta.discourse.org/u/fuerst)
#### Post date: [15 Dicembre 2016, 9:14am UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/10 "2016-12-15T09:14:14Z")
You are right - precompiling assets started before database migration. Adding your code above to the `before_bundle_exec` hook worked. Thanks a lot for your help!
I had to modify it slightly to get it executed properly. My hook for multi site looks like this now:
```plaintext
before_bundle_exec:
- file:
path: $home/config/multisite.yml
contents: |
# (your multisite.yml config here)
- exec: cd /var/www/discourse && sudo -E -u discourse bundle install --deployment --verbose --without test --without development
- exec: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate
```
Should I consider this as a one time workaround or can this two `exec` stay forever in my template file?
---
### Author:  [@Sander78](https://meta.discourse.org/u/Sander78)
#### Post date: [10 Gennaio 2017, 3:28pm UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/11 "2017-01-10T15:28:12Z")
I’m glad I found this topic. Had the same problem. But even now I have an error:
```plaintext
INFO -- : Running `bundle install --deployment --verbose --without "development"` with bundler 1.13.7
The --deployment flag requires a Gemfile.lock. Please make sure you have checked
your Gemfile.lock into version control before deploying.
```
So it seems it’s missing that `Gemfile.lock` file.
In the end I fixed it by running the older version of Discourse I had, then:
- enter it with `launcher enter app`
- `cd db/migrations`
- paste the contents of the migration file above into a new file
- `cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate`
Now you can upgrade as usual with `launcher rebuild app`.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [13 Settembre 2017, 5:40pm UTC](https://meta.discourse.org/t/multisite-upgrade-failed-due-to-missing-database-columns/54239/12 "2017-09-13T17:40:44Z")