I, [2025-02-24T17:35:41.516926 #1] INFO -- : Terminating async processes
I, [2025-02-24T17:35:41.516987 #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: 38
105:signal-handler (1740418541) Received SIGTERM scheduling shutdown...
I, [2025-02-24T17:35:41.517067 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 105
2025-02-24 17:35:41.517 UTC [38] LOG: received fast shutdown request
2025-02-24 17:35:41.518 UTC [38] LOG: aborting any active transactions
2025-02-24 17:35:41.521 UTC [38] LOG: background worker "logical replication launcher" (PID 52) exited with exit code 1
105:M 24 Feb 2025 17:35:41.523 # User requested shutdown...
105:M 24 Feb 2025 17:35:41.523 * Saving the final RDB snapshot before exiting.
2025-02-24 17:35:41.525 UTC [47] LOG: shutting down
2025-02-24 17:35:41.538 UTC [47] LOG: checkpoint starting: shutdown immediate
2025-02-24 17:35:41.550 UTC [47] LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.005 s, sync=0.001 s, total=0.025 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=1122 kB
2025-02-24 17:35:41.581 UTC [38] LOG: database system is shut down
105:M 24 Feb 2025 17:35:41.657 * DB saved on disk
105:M 24 Feb 2025 17:35:41.657 # Redis is now ready to exit, bye bye...
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && sudo -E -u discourse bundle exec rake s3:upload_assets failed with return #<Process::Status: pid 2845 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=>"$home", "cmd"=>["sudo -E -u discourse bundle exec rake s3:upload_assets", "sudo -E -u discourse bundle exec rake s3:expire_missing_assets"]}
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.
c08b2ad74e9f1171f7677979af4e41a46be92877a0783350b2f020359895a431
yes, I guess that’s the issue Aws::S3::Errors::InvalidArgument: Unsupported header 'x-amz-checksum-crc32' received for this API call. (Aws::S3::Errors::InvalidArgument)
are there any way to downgrade aws-sdk-s3 gem manually?
rake aborted!
Aws::S3::Errors::InvalidArgument: Unsupported header 'x-amz-checksum-crc32' received for this API call. (Aws::S3::Errors::InvalidArgument)
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && sudo -E -u discourse bundle exec rake s3:expire_missing_assets failed with return #<Process::Status: pid 2900 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=>"$home", "cmd"=>["sudo -E -u discourse bundle exec rake s3:upload_assets", "sudo -E -u discourse bundle exec rake s3:expire_missing_assets"]}
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.
