' /var/www/discourse/lib/distributed_mutex.rb:53:in `block in synchronize' /var/www/discourse/lib/distributed_mutex.rb:49:in `synchronize' /var/www/discourse/lib/distributed_mutex.rb:49:in `synchronize' /var/www/discourse/lib/distributed_mutex.rb:34:in `synchronize' /var/www/discourse/lib/tasks/db.rake:242:in `block in

' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.0/exe/rake:27:in `' /usr/local/bin/bundle:25:in `load' /usr/local/bin/bundle:25:in `

' Caused by: PG::NotNullViolation: ERROR: null value in column "answer_post_id" of relation "discourse_solved_solved_topics" violates not-null constraint (PG::NotNullViolation) DETAIL: Failing row contains (3735, 35506, null, -1, null, 2021-05-12 18:38:58.11516, 2021-05-12 18:38:58.11516). /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/db/pg/alias_method.rb:109:in `exec' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/db/pg/alias_method.rb:109:in `async_exec' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/postgres/connection.rb:217:in `run' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `block in run' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `block in with_lock' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/concurrency/null_lock.rb:9:in `synchronize' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `with_lock' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `run' /var/www/discourse/lib/mini_sql_multisite_connection.rb:109:in `run' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/postgres/connection.rb:196:in `exec' /var/www/discourse/plugins/discourse-solved/db/migrate/20250318024953_copy_solved_topic_custom_field_to_discourse_solved_solved_topics.rb:17:in `up' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:994:in `public_send' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:994:in `exec_migration' /var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in `block in exec_migration' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/benchmark-0.4.1/lib/benchmark.rb:305:in `measure' /var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in `exec_migration' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:975:in `block (2 levels) in migrate' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/benchmark.rb:17:in `realtime' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:974:in `block in migrate' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:412:in `with_connection' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:973:in `migrate' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1187:in `migrate' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1535:in `block in execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1588:in `ddl_transaction' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1534:in `execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1509:in `each' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1509:in `migrate_without_lock' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1454:in `block in migrate' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1606:in `with_advisory_lock' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1454:in `migrate' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1261:in `up' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1236:in `migrate' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/tasks/database_tasks.rb:270:in `migrate' /var/www/discourse/lib/tasks/db.rake:267:in `block (2 levels) in

' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.0/exe/rake:27:in `' /usr/local/bin/bundle:25:in `load' /usr/local/bin/bundle:25:in `

' Tasks: TOP => db:migrate (See full trace by running task with --trace) I, [2025-12-20T03:48:21.794538 #1] INFO -- : gem install geocoder -v 1.8.3 -i /var/www/discourse/plugins/discourse-locations/gems/3.3.8 --no-document --ignore-dependencies --no-user-install Successfully installed geocoder-1.8.3 1 gem installed == 20250318024953 CopySolvedTopicCustomFieldToDiscourseSolvedSolvedTopics: migrating I, [2025-12-20T03:48:21.795736 #1] INFO -- : Terminating async processes I, [2025-12-20T03:48:21.795838 #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/15/bin/postmaster -D /etc/postgresql/15/main pid: 45 I, [2025-12-20T03:48:21.795934 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 112 112:signal-handler (1766202501) Received SIGTERM scheduling shutdown... 2025-12-20 03:48:21.796 UTC [45] LOG: received fast shutdown request 2025-12-20 03:48:21.800 UTC [45] LOG: aborting any active transactions 2025-12-20 03:48:21.808 UTC [45] LOG: background worker "logical replication launcher" (PID 59) exited with exit code 1 2025-12-20 03:48:21.809 UTC [54] LOG: shutting down 2025-12-20 03:48:21.811 UTC [54] LOG: checkpoint starting: shutdown immediate 2025-12-20 03:48:21.861 UTC [54] LOG: checkpoint complete: wrote 18 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.039 s, sync=0.006 s, total=0.052 s; sync files=10, longest=0.003 s, average=0.001 s; distance=161 kB, estimate=161 kB 112:M 20 Dec 2025 03:48:21.892 # User requested shutdown... 112:M 20 Dec 2025 03:48:21.892 * Saving the final RDB snapshot before exiting. 2025-12-20 03:48:21.918 UTC [45] LOG: database system is shut down 112:M 20 Dec 2025 03:48:22.621 * DB saved on disk 112:M 20 Dec 2025 03:48:22.621 # 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 # Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.3.0/lib/pups/exec_command.rb:131:in `spawn' exec failed with the params {"cd"=>"$home", "tag"=>"migrate", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]} bootstrap failed with exit code 1 **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. ``` 我通过从 app.yml 中删除 solved 插件（使用 `- rm -rf discourse-solved` 命令）成功完成了重建，论坛的所有者或许可以不用这个插件，但我仍然希望修复这个问题。我认为问题并不出在插件本身，可能是论坛的操作不当导致的。但在探索数据库时，我发现至少有 20-30 条 `\N` 的 value 记录。以下是部分数据示例： | id | topic\_id | name | value | created at | updated at | | --- | --- | --- | --- | --- | --- | | 1579 | 35497 | accepted\_answer\_post\_id | 301435 | 2021-05-10 20:18:57.780444 | 2021-05-10 20:18:57.780444 | | 1583 | **35506** | accepted\_answer\_post\_id | \N | 2021-05-12 18:38:58.11516 | 2021-05-12 18:38:58.11516 | | 423 | 21211 | accepted\_answer\_post\_id | 153039 | 2019-09-04 21:01:37.811417 | 2019-09-04 21:01:37.811417 | | 424 | 21685 | accepted\_answer\_post\_id | 156850 | 2019-09-09 04:39:28.388591 | 2019-09-09 04:39:28.388591 | | 425 | 21711 | accepted\_answer\_post\_id | 157323 | 2019-09-11 11:51:14.375185 | 2019-09-11 11:51:14.375185 | | 428 | 20982 | accepted\_answer\_post\_id | 157807 | 2019-09-14 08:53:16.079032 | 2019-09-14 08:53:16.079032 | | 429 | 4949 | accepted\_answer\_post\_id | 157515 | 2019-09-16 07:57:00.862694 | 2019-09-16 07:57:00.862694 | | 430 | 15439 | accepted\_answer\_post\_id | 158645 | 2019-09-19 00:56:20.112603 | 2019-09-19 00:56:20.112603 | | 1603 | 35710 | accepted\_answer\_post\_id | \N | 2021-05-19 20:58:06.598697 | 2021-05-19 20:58:06.598697 | | 701 | 25377 | accepted\_answer\_post\_id | 195459 | 2020-03-26 20:42:14.168898 | 2020-03-26 20:42:14.168898 | | 434 | 21868 | accepted\_answer\_post\_id | 159024 | 2019-09-22 10:09:09.671605 | 2019-09-22 10:09:09.671605 | 我需要说明的是，我不擅长 SQL 查询，尤其是通过命令行执行。我不太敢直接通过终端删除这些记录。不过，您建议我采取什么步骤来修复这个问题？是执行某种查询（具体是什么类型的查询）？编写脚本，还是可以在论坛界面直接操作？ --- _[View the full topic](https://meta.discourse.org/t/discourse-solved-solved-topics-violates-not-null-constraint-during-rebuild/391813)._