خطأ في إعادة البناء بسبب إضافة الوسوم القديمة

Hi just wanted to ask if atm for others aswell the rebuild fails?

I get the following error:
(whole Error Log: Discourse Error - Pastebin.com)

I, [2021-05-21T01:17:33.651053 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake plugin:pull_compatible_all'
I, [2021-05-21T01:17:36.304377 #1]  INFO -- : discourse-solved is already at latest compatible version
discourse-checklist is already at latest compatible version
discourse-voting is already at latest compatible version
discourse-canned-replies is already at latest compatible version
discourse-tagging is already at latest compatible version
docker_manager is already at latest compatible version
retort is already at latest compatible version
discourse-staff-notes is already at latest compatible version

I, [2021-05-21T00:49:56.625424 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
rake aborted!
NoMethodError: undefined method `client_setting' for #<Class:0x00005646c55170b8>
Did you mean?  client_settings
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/dynamic_matchers.rb:22:in `method_missing'
/var/www/discourse/plugins/discourse-tagging/plugin.rb:13:in `block in activate!'
/var/www/discourse/lib/plugin/instance.rb:430:in `block in notify_after_initialize'
/var/www/discourse/lib/plugin/instance.rb:428:in `each'
/var/www/discourse/lib/plugin/instance.rb:428:in `notify_after_initialize'
/var/www/discourse/config/application.rb:350:in `each'
/var/www/discourse/config/application.rb:350:in `block (2 levels) in <class:Application>'
/var/www/discourse/lib/plugin_initialization_guard.rb:5:in `plugin_initialization_guard'
/var/www/discourse/config/application.rb:349:in `block in <class:Application>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.3.2/lib/active_support/lazy_load_hooks.rb:68:in `block in execute_hook'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.3.2/lib/active_support/lazy_load_hooks.rb:61:in `with_execution_control'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.3.2/lib/active_support/lazy_load_hooks.rb:66:in `execute_hook'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.3.2/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.3.2/lib/active_support/lazy_load_hooks.rb:51:in `each'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.3.2/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/application/finisher.rb:140:in `block in <module:Finisher>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/initializable.rb:32:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/initializable.rb:32:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/initializable.rb:61:in `block in run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/initializable.rb:60:in `run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/application.rb:384:in `initialize!'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/railtie.rb:207:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/railtie.rb:207:in `method_missing'
/var/www/discourse/config/environment.rb:7:in `<main>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.5/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.7.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.3.2/lib/active_support/dependencies.rb:332:in `block in require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.3.2/lib/active_support/dependencies.rb:299:in `load_dependency'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.3.2/lib/active_support/dependencies.rb:332:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/application.rb:360:in `require_environment!'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-6.1.3.2/lib/rails/application.rb:526:in `block in run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.3/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
Tasks: TOP => db:migrate => db:load_config => environment
(See full trace by running task with --trace)
I, [2021-05-21T00:50:07.253788 #1]  INFO -- :
I, [2021-05-21T00:50:07.254105 #1]  INFO -- : Terminating async processes
I, [2021-05-21T00:50:07.254128 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 54
I, [2021-05-21T00:50:07.254170 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 171
2021-05-21 00:50:07.254 UTC [54] LOG:  received fast shutdown request
2021-05-21 00:50:07.256 UTC [54] LOG:  aborting any active transactions
171:signal-handler (1621558207) Received SIGTERM scheduling shutdown...
2021-05-21 00:50:07.265 UTC [54] LOG:  background worker "logical replication launcher" (PID 63) exited with exit code 1
2021-05-21 00:50:07.267 UTC [58] LOG:  shutting down
171:M 21 May 2021 00:50:07.325 # User requested shutdown...
171:M 21 May 2021 00:50:07.325 * Saving the final RDB snapshot before exiting.
171:M 21 May 2021 00:50:07.348 * DB saved on disk
171:M 21 May 2021 00:50:07.348 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 819 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'"]}
2021-05-21 00:50:07.559 UTC [54] LOG:  database system is shut down
ff769b60a9ad4c18fcae80af6f5ac4ecf82c60c5ddf3b24578fdd338f6b2605b
** 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.
root@main:/var/discourse#

Where I want to draw special attention to:

NoMethodError: undefined method `client_setting' for #<Class:0x00005646c55170b8>
Did you mean?  client_settings

I have never seen that error before and performing that procedure like here:

did not help this time.

Any assumptions what could cause that error? Is this caused by a TYPO?
client_settingclient_settings

EDIT:

yes the installation is setup as recommended :slight_smile:

EDIT 2:

Installed Plugins

https://github.com/discourse/docker_manager.git
https://github.com/discourse/discourse-solved.git
https://github.com/discourse/discourse-tagging.git
https://github.com/discourse/discourse-voting.git
https://github.com/discourse/discourse-checklist.git
https://github.com/discourse/discourse-canned-replies.git
https://github.com/gdpelican/retort.git
https://github.com/discourse/discourse-staff-notes.git
إعجاب واحد (1)

Please remove the Discourse tagging plugin as it was merged in core back in 2016.

By the way, how that plugin ended up in your app.yml file?

5 إعجابات

Thanks for the hint! Will change that and try again.

The original installation was I think from 2013 or 2014. This is from a FOSS Project which got maintained over this time and since 2019 I maintain this project and do regular updates and stuff like that. So it seems back then the Plugin was implemented and has never been removed :sweat_smile:

That did the trick! Your my hero for today :v:

EDIT:

sorry cant mark it as solution somehow

إعجابَين (2)

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