# Erreur aujourd'hui lors de la mise à niveau de 2.5.1 à 2.5.2, discourse-assign

**URL:** https://meta.discourse.org/t/today-error-when-upgrade-from-2-5-1-to-2-5-2-discourse-assign/166494
**Category:** Self-hosting
**Created:** [Octobre 7, 2020, 6:48 UTC](https://meta.discourse.org/t/today-error-when-upgrade-from-2-5-1-to-2-5-2-discourse-assign/166494 "2020-10-07T06:48:05Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![nahimov](https://avatars.discourse-cdn.com/v4/letter/n/aca169/32.png) [@nahimov](https://meta.discourse.org/u/nahimov)
#### Post date: [Octobre 7, 2020, 6:48 UTC](https://meta.discourse.org/t/today-error-when-upgrade-from-2-5-1-to-2-5-2-discourse-assign/166494/1 "2020-10-07T06:48:06Z")

</div>

Aujourd’hui, avant de mettre à jour le forum de production, j’ai essayé de mettre à jour le forum de test avec la version 2.5.1 **stable** et j’ai obtenu l’erreur suivante :

```plaintext
I, [2020-10-07T06:39:44.735617 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
	88: from /usr/local/bin/bundle:23:in `<main>'
	87: from /usr/local/bin/bundle:23:in `load'
	86: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/exe/bundle:34:in `<top (required)>'
	85: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/friendly_errors.rb:123:in `with_friendly_errors'
	84: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/exe/bundle:46:in `block in <top (required)>'
	83: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli.rb:24:in `start'
	82: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/base.rb:476:in `start'
	81: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli.rb:30:in `dispatch'
	80: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor.rb:399:in `dispatch'
	79: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	78: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	77: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli.rb:476:in `exec'
	76: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:28:in `run'
	75: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `kernel_load'
	74: from /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `load'
	73: from /var/www/discourse/vendor/bundle/ruby/2.6.0/bin/rake:23:in `<top (required)>'
	72: from /var/www/discourse/vendor/bundle/ruby/2.6.0/bin/rake:23:in `load'
	71: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
	70: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:80:in `run'
	69: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:186:in `standard_exception_handling'
	68: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:83:in `block in run'
	67: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:110:in `top_level'
	66: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:125:in `run_with_threads'
	65: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block in top_level'
	64: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `each'
	63: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block (2 levels) in top_level'
	62: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:160:in `invoke_task'
	61: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:188:in `invoke'
	60: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
	59: from /usr/local/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
	58: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:218:in `block in invoke_with_call_chain'
	57: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:241:in `invoke_prerequisites'
	56: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:241:in `each'
	55: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:243:in `block in invoke_prerequisites'
	54: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
	53: from /usr/local/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
	52: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:218:in `block in invoke_with_call_chain'
	51: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:241:in `invoke_prerequisites'
	50: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:241:in `each'
	49: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:243:in `block in invoke_prerequisites'
	48: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
	47: from /usr/local/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
	46: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
	45: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `execute'
	44: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `each'
	43: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `block in execute'
	42: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/application.rb:523:in `block in run_tasks_blocks'
	41: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/application.rb:339:in `require_environment!'
	40: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in `require'
	39: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:291:in `load_dependency'
	38: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in `block in require'
	37: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in `require'
	36: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	35: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	34: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	33: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	32: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	31: from /var/www/discourse/config/environment.rb:7:in `<main>'
	30: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/railtie.rb:190:in `method_missing'
	29: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/railtie.rb:190:in `public_send'
	28: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/application.rb:363:in `initialize!'
	27: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/initializable.rb:60:in `run_initializers'
	26: from /usr/local/lib/ruby/2.6.0/tsort.rb:205:in `tsort_each'
	25: from /usr/local/lib/ruby/2.6.0/tsort.rb:226:in `tsort_each'
	24: from /usr/local/lib/ruby/2.6.0/tsort.rb:347:in `each_strongly_connected_component'
	23: from /usr/local/lib/ruby/2.6.0/tsort.rb:347:in `call'
	22: from /usr/local/lib/ruby/2.6.0/tsort.rb:347:in `each'
	21: from /usr/local/lib/ruby/2.6.0/tsort.rb:349:in `block in each_strongly_connected_component'
	20: from /usr/local/lib/ruby/2.6.0/tsort.rb:431:in `each_strongly_connected_component_from'
	19: from /usr/local/lib/ruby/2.6.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
	18: from /usr/local/lib/ruby/2.6.0/tsort.rb:228:in `block in tsort_each'
	17: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/initializable.rb:61:in `block in run_initializers'
	16: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/initializable.rb:32:in `run'
	15: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/initializable.rb:32:in `instance_exec'
	14: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.3.1/lib/rails/application/finisher.rb:129:in `block in <module:Finisher>'
	13: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'
	12: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/lazy_load_hooks.rb:51:in `each'
	11: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'
	10: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/lazy_load_hooks.rb:66:in `execute_hook'
	9: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/lazy_load_hooks.rb:61:in `with_execution_control'
	8: from /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.1/lib/active_support/lazy_load_hooks.rb:68:in `block in execute_hook'
	7: from /var/www/discourse/config/application.rb:335:in `block in <class:Application>'
	6: from /var/www/discourse/lib/plugin_initialization_guard.rb:5:in `plugin_initialization_guard'
	5: from /var/www/discourse/config/application.rb:336:in `block (2 levels) in <class:Application>'
	4: from /var/www/discourse/config/application.rb:336:in `each'
	3: from /var/www/discourse/lib/plugin/instance.rb:363:in `notify_after_initialize'
	2: from /var/www/discourse/lib/plugin/instance.rb:363:in `each'
	1: from /var/www/discourse/lib/plugin/instance.rb:365:in `block in notify_after_initialize'
/var/www/discourse/plugins/discourse-assign/plugin.rb:495:in `block in activate!': undefined method `register_search_advanced_filter' for #<Plugin::Instance:0x00005560719c7648>
Did you mean? register_seed_data (NoMethodError)

**PLUGIN INCOMPATIBLE**

Vous ne pouvez pas compiler Discourse en raison d'erreurs dans le plugin situé à
/var/www/discourse/plugins/discourse-assign

```

Que faire dans ce cas ?

---

<div class="post-metadata">

### Author: ![IAmGav](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iamgav/32/235598_2.png) [@IAmGav](https://meta.discourse.org/u/IAmGav)
#### Post date: [Octobre 7, 2020, 7:30 UTC](https://meta.discourse.org/t/today-error-when-upgrade-from-2-5-1-to-2-5-2-discourse-assign/166494/2 "2020-10-07T07:30:27Z")

</div>

Vous voudrez peut-être également mettre à jour le logiciel système et vous assurer que vous utilisez la bonne version de PostgreSQL.

> apt-get update  
> apt-get upgrade

Ensuite, assurez-vous d’utiliser PostgreSQL 12

> [@PostgreSQL 12 update](https://meta.discourse.org/t/postgresql-12-update/151236):
>
> warning WARNING! If your database is very large, you will need a lot of extra disk space (2x database size) and should be very careful with this upgrade! We just landed the long waited PostgreSQL major version upgrade. Any site admins rebuilding Discourse from the command line will be upgraded to PostgreSQL 12 from the old PostgreSQL 10. We are running this new version for a while on Meta, and everything is working fine. PostgreSQL 12 brings lots of improvements that will be automatical…

---

<div class="post-metadata">

### Author: ![nahimov](https://avatars.discourse-cdn.com/v4/letter/n/aca169/32.png) [@nahimov](https://meta.discourse.org/u/nahimov)
#### Post date: [Octobre 7, 2020, 11:19 UTC](https://meta.discourse.org/t/today-error-when-upgrade-from-2-5-1-to-2-5-2-discourse-assign/166494/3 "2020-10-07T11:19:37Z")

</div>

J’ai mis à niveau un conteneur PostgreSQL sur un autre serveur vers la version 12 :

```plaintext
└─# docker exec -it 5a6c70035b87 psql --version
psql (PostgreSQL) 12.4 (Debian 12.4-1.pgdg100+1)

```

Et cela n’a pas aidé ! Le forum refusait toujours de se compiler avec le plugin `discourse-assign`…  
J’ai mis à jour les logiciels système sur le serveur où Discourse est installé :

```plaintext
root@cuba-test-forum-ru:/var/discourse# apt update
Hit:1 https://download.docker.com/linux/ubuntu bionic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Fetched 252 kB in 1s (201 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

```

Et cela a aidé ! Le forum s’est compilé et a démarré normalement avec le plugin `discourse-assign`.  
Par simple curiosité — pourquoi est-ce le cas ?

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [Octobre 7, 2020, 11:52 UTC](https://meta.discourse.org/t/today-error-when-upgrade-from-2-5-1-to-2-5-2-discourse-assign/166494/4 "2020-10-07T11:52:33Z")

</div>

Cette fonctionnalité a été ajoutée il y a 27 jours :

[https://github.com/discourse/discourse-assign/commit/303274eae3c6012ee6178c347d834aed40fe3906](https://github.com/discourse/discourse-assign/commit/303274eae3c6012ee6178c347d834aed40fe3906)

Cela s’est produit parce que, pour vous, le plugin et le noyau Discourse devaient être mis à jour simultanément. Une reconstruction en ligne de commande permet de réaliser cela.

---

<div class="post-metadata">

### Author: ![nahimov](https://avatars.discourse-cdn.com/v4/letter/n/aca169/32.png) [@nahimov](https://meta.discourse.org/u/nahimov)
#### Post date: [Octobre 7, 2020, 12:15 UTC](https://meta.discourse.org/t/today-error-when-upgrade-from-2-5-1-to-2-5-2-discourse-assign/166494/5 "2020-10-07T12:15:36Z")

</div>

J’ai utilisé la ligne de commande : `launcher rebuild app`  
Dès le début.  
Mais jusqu’à ce que je mette à jour le logiciel système sur le serveur, Discourse affichait une erreur lors de la reconstruction avec le plugin `discourse-assign`.  
Je me demande pourquoi c’est le cas. Auparavant, il n’était pas nécessaire de mettre à jour le logiciel système.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [Novembre 6, 2020, 12:17 UTC](https://meta.discourse.org/t/today-error-when-upgrade-from-2-5-1-to-2-5-2-discourse-assign/166494/6 "2020-11-06T12:17:36Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
