# Nova instalação falha na migração

**URL:** https://meta.discourse.org/t/new-installation-fails-on-migration/147425
**Category:** Bug
**Created:** [9 Abril , 2020 15:41 UTC](https://meta.discourse.org/t/new-installation-fails-on-migration/147425 "2020-04-09T15:41:20Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![renchap](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/renchap/32/176343_2.png) [@renchap](https://meta.discourse.org/u/renchap)
#### Post date: [9 Abril , 2020 15:41 UTC](https://meta.discourse.org/t/new-installation-fails-on-migration/147425/1 "2020-04-09T15:41:20Z")

</div>

Estou tentando instalar uma nova instância do Discourse usando `discourse_docker`, mas as migrações estão falhando:

```plaintext
== 20180916195601 MigrateS3BackupSiteSettings: migrating ======================
-- execute("UPDATE site_settings\nSET name = 'backup_location',\n data_type = 7,\n value = 's3'\nWHERE name = 'enable_s3_backups' AND value = 't';\n")
   -> 0.0005s
-- execute("DELETE\nFROM site_settings\nWHERE name = 'enable_s3_backups';\n")
   -> 0.0004s
== 20180916195601 MigrateS3BackupSiteSettings: migrated (0.0018s) =============

== 20180917024729 RemoveSuperfluousColumns: migrating =========================

WARNING
-------------------------------------------------------------------------------------
An attempt was made to drop or rename a column in a migration
SQL used was: 'ALTER TABLE user_profiles DROP COLUMN IF EXISTS card_image_badge_id'

Please generate a post deployment migration using `rails g post_migration` to drop
or rename columns.

Note, to minimize disruption use self.ignored_columns = ["column name"] on your
ActiveRecord model, this can be removed 6 months or so later.

This protection is in place to protect us against dropping columns that are currently
in use by live applications.

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 12775 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
59a086818934d9ab5ac6095987a41a5d4f317615dab7d86710afc36b0b40cf5e
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.

```

Funciona normalmente quando forço a versão para `v2.5.0.beta2` em vez de `test_passed`, e vejo commits recentes relacionados ao `SafeMigration`; parece haver uma correlação.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [9 Abril , 2020 15:44 UTC](https://meta.discourse.org/t/new-installation-fails-on-migration/147425/2 "2020-04-09T15:44:58Z")

</div>

Talvez seja

> <https://github.com/discourse/discourse/commit/6b192d29fa095e91cb40b71e76dfc811f4aa205c>
>
> SafeMigrate outputs text when we detect attempts to unsafely drop tables
> and col…umns
> 
> It is unfortunately not thread safe
> 
> This is not needed in production as we would have already caught it by then
> in our test suite.

---

<div class="post-metadata">

### Author: ![Mezbah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mezbah/32/114613_2.png) [@Mezbah](https://meta.discourse.org/u/Mezbah)
#### Post date: [9 Abril , 2020 17:57 UTC](https://meta.discourse.org/t/new-installation-fails-on-migration/147425/3 "2020-04-09T17:57:44Z")

</div>

@renchap  
você conseguiu alguma solução?

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [9 Abril , 2020 18:20 UTC](https://meta.discourse.org/t/new-installation-fails-on-migration/147425/4 "2020-04-09T18:20:22Z")

</div>

Reverti os commits de desempenho para as migrações, para que @sam tenha a chance de revisar esse erro e corrigi-lo após o feriado prolongado:

> <https://github.com/discourse/discourse/commit/8b46f14744d4bab9339d075825914d86da6bd5eb>
>
> these series of commits.
> 
> See:
> https://meta.discourse.org/t/new-installation-fai…ls-on-migration/147425
> 
> This reverts commit 80e832662b719425872e7ac3736fb9fc56d85aca.
> This reverts commit de5f2d33087c8e9c12f83d573015d275098bd68f.
> This reverts commit 6b192d29fa095e91cb40b71e76dfc811f4aa205c.
> This reverts commit a5b582f686c0a8427aad3f6caf9f3a8105e66ee9.
> This reverts commit 708dd97dfd0380c703678a0ee070dc62880e57f1.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [14 Abril , 2020 01:39 UTC](https://meta.discourse.org/t/new-installation-fails-on-migration/147425/5 "2020-04-14T01:39:39Z")

</div>

Corrigido conforme:

> [@New installation fails (fresh install)](https://meta.discourse.org/t/new-installation-fails-fresh-install/147461/7?u=sam):
>
> Fixed this per: Zeitwerk was autoloading this cause we had some migrations that would run overrides on SafeMigrate. I disabled this in the class.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [14 Abril , 2020 01:39 UTC](https://meta.discourse.org/t/new-installation-fails-on-migration/147425/6 "2020-04-14T01:39:42Z")

</div>