[STARTED] ‘user1’ has started the restore! Marking restore as running… Making sure /workspace/discourse/tmp/restores/default/2026-04-29-211652 exists… Copying archive to tmp directory… Extracting dump file… Validating metadata… Current version: 20260420014648 Restored version: 20260420014648 Enabling readonly mode… Pausing sidekiq… Waiting up to 60 seconds for Sidekiq to finish running jobs… I, [2026-04-29T21:16:58.919008 #394429] INFO – : Detected dead worker 394502, restarting… I, [2026-04-29T21:16:59.708195 #396907] INFO – : Loading Sidekiq in process id 396907 E, [2026-04-29T21:16:59.731189 #396907] ERROR – : Error encountered while starting Sidekiq: [Discourse::Utils::CommandError] renice -n 5 -p 396907 renice: failed to set priority for 396907 (process ID): Permission denied /workspace/discourse/lib/discourse.rb:177:in ‘Discourse::Utils::CommandRunner#execute_command’ /workspace/discourse/lib/discourse.rb:143:in ‘Discourse::Utils::CommandRunner#exec’ /workspace/discourse/lib/discourse.rb:33:in ‘Discourse::Utils.execute_command’ /workspace/discourse/lib/demon/sidekiq.rb:133:in ‘Demon::Sidekiq#after_fork’ /workspace/discourse/lib/demon/base.rb:188:in ‘block in Demon::Base#run’ /workspace/discourse/lib/demon/base.rb:184:in ‘Kernel#fork’ /workspace/discourse/lib/demon/base.rb:184:in ‘Demon::Base#run’ /workspace/discourse/lib/demon/base.rb:177:in ‘Demon::Base#start’ /workspace/discourse/lib/demon/base.rb:163:in ‘Demon::Base#ensure_running’ /workspace/discourse/lib/demon/base.rb:44:in ‘block in Demon::Base.ensure_running’ /workspace/discourse/lib/demon/base.rb:44:in ‘Array#each’ /workspace/discourse/lib/demon/base.rb:44:in ‘Demon::Base.ensure_running’ /workspace/discourse/config/pitchfork.conf.rb:136:in ‘block (2 levels) in Pitchfork::Configurator#load’ Creating missing functions in the discourse_functions schema… Restoring dump file… (this may take a while) SET SET SET SET SET set_config (1 row) SET SET SET SET ERROR: type “ai_moderation_setting_type” already exists EXCEPTION: psql failed: ERROR: type “ai_moderation_setting_type” already exists /workspace/discourse/lib/backup_restore/database_restorer.rb:95:in ‘BackupRestore::DatabaseRestorer#restore_dump’ /workspace/discourse/lib/backup_restore/database_restorer.rb:26:in ‘BackupRestore::DatabaseRestorer#restore’ /workspace/discourse/lib/backup_restore/restorer.rb:61:in ‘BackupRestore::Restorer#run’ /workspace/discourse/script/spawn_backup_restore.rb:20:in ‘Object#restore’ /workspace/discourse/script/spawn_backup_restore.rb:33:in ‘block in ’ /workspace/discourse/script/spawn_backup_restore.rb:4:in ‘Kernel#fork’ /workspace/discourse/script/spawn_backup_restore.rb:4:in ‘’ Trying to rollback… There was no need to rollback Cleaning stuff up… Dropping functions from the discourse_functions schema… Removing tmp ‘/workspace/discourse/tmp/restores/default/2026-04-29-211652’ directory… Unpausing sidekiq… Marking restore as finished… Notifying ‘user1’ of the end of the restore… I, [2026-04-29T21:17:01.099411 #397017] INFO – : Loading Sidekiq in process id 397017 E, [2026-04-29T21:17:01.108527 #397017] ERROR – : Error encountered while starting Sidekiq: [Discourse::Utils::CommandError] renice -n 5 -p 397017 renice: failed to set priority for 397017 (process ID): Permission denied /workspace/discourse/lib/discourse.rb:177:in ‘Discourse::Utils::CommandRunner#execute_command’ /workspace/discourse/lib/discourse.rb:143:in ‘Discourse::Utils::CommandRunner#exec’ /workspace/discourse/lib/discourse.rb:33:in ‘Discourse::Utils.execute_command’ /workspace/discourse/lib/demon/sidekiq.rb:133:in ‘Demon::Sidekiq#after_fork’ /workspace/discourse/lib/demon/base.rb:188:in ‘block in Demon::Base#run’ /workspace/discourse/lib/demon/base.rb:184:in ‘Kernel#fork’ /workspace/discourse/lib/demon/base.rb:184:in ‘Demon::Base#run’ /workspace/discourse/lib/demon/base.rb:177:in ‘Demon::Base#start’ /workspace/discourse/lib/demon/base.rb:95:in ‘Demon::Base#restart’ /workspace/discourse/lib/demon/sidekiq.rb:40:in ‘block in Demon::Sidekiq.heartbeat_check’ /workspace/discourse/lib/demon/sidekiq.rb:31:in ‘Array#each’ /workspace/discourse/lib/demon/sidekiq.rb:31:in ‘Demon::Sidekiq.heartbeat_check’ /workspace/discourse/config/pitchfork.conf.rb:137:in ‘block (2 levels) in Pitchfork::Configurator#load’ Finished! [FAILED] I, [2026-04-29T21:17:08.359107 #393481] INFO – : reaped unknown subprocess # I cannot really figure this out? Any help?

hi @ziln :wave: welcome to discourse meta :slight_smile: [image] ziln: ERROR: type “ai_moderation_setting_type” already exists EXCEPTION: psql failed: ERROR: type “ai_moderation_setting_type” already exists i think it looks like your target instance isn’t clean or has data already, and you’re getting an object collision. assuming this is a standard install, try dropping and creating a clean new database, then doing the migration. looks like pfaffman had a similar issue here: [image]Restore failed `entity2char already exists' RDS Postgres 13.7 The solution was to drop, create, and migrate the database before doing the restore. I should have tried skipping the migrate step.

I don’t know. That guy doesn’t sound like he knows much. :wink:

thanks for your input :slight_smile: Yes, I’ve tried droping and creating new db but I got the same error. I was only able to restore backup via SQL manually.

Backup Restoration Issue

Product Support Self-hosting

supermathie (Michael Brown) June 9, 2026, 11:26am 5

What’s the postgres role setup you have in your situation?

Topic		Replies	Views
Can't restore saved backup Self-hosting	3	1367	March 7, 2017
Error when restore DB backup Self-hosting	25	2215	August 23, 2018
Problem with restore Discourse from backup (3.4, quite large DB) Product Support	17	585	January 14, 2025
Trouble restoring from backup Product Support	10	1435	January 31, 2018
Restore has failed. when i backup and restore to a new discourse Product Support	13	1837	September 16, 2019

Backup Restoration Issue

Related topics