Ok, but the official installation is broken:
I, [2022-04-02T15:13:26.316835 #1] INFO -- : File > /etc/cron.d/anacron chmod: chown:
I, [2022-04-02T15:13:26.323689 #1] INFO -- : File > /etc/runit/1.d/copy-env chmod: +x chown:
I, [2022-04-02T15:13:26.330548 #1] INFO -- : File > /etc/service/unicorn/run chmod: +x chown:
I, [2022-04-02T15:13:26.337595 #1] INFO -- : File > /etc/service/nginx/run chmod: +x chown:
I, [2022-04-02T15:13:26.344711 #1] INFO -- : File > /etc/runit/3.d/01-nginx chmod: +x chown:
I, [2022-04-02T15:13:26.351608 #1] INFO -- : File > /etc/runit/3.d/02-unicorn chmod: +x chown:
I, [2022-04-02T15:13:26.351736 #1] INFO -- : Replacing # postgres with sv start postgres || exit 1 in /etc/service/unicorn/run
I, [2022-04-02T15:13:26.352214 #1] INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2022-04-02T15:13:26.354936 #1] INFO -- : > cd /var/www/discourse && git reset --hard
130:C 02 Apr 2022 15:13:26.361 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
130:C 02 Apr 2022 15:13:26.361 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=130, just started
130:C 02 Apr 2022 15:13:26.361 # Configuration loaded
130:M 02 Apr 2022 15:13:26.362 * monotonic clock: POSIX clock_gettime
fatal: Unable to create '/var/www/discourse/.git/index.lock': Disk quota exceeded
130:M 02 Apr 2022 15:13:26.362 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
130:M 02 Apr 2022 15:13:26.362 # Failed listening on port 6379 (TCP), aborting.
I, [2022-04-02T15:13:26.363767 #1] INFO -- :
I, [2022-04-02T15:13:26.364354 #1] INFO -- : Terminating async processes
I, [2022-04-02T15:13:26.364466 #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: 42
I, [2022-04-02T15:13:26.364546 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
2022-04-02 15:13:26.364 UTC [42] LOG: received fast shutdown request
103:signal-handler (1648912406) Received SIGTERM scheduling shutdown...
2022-04-02 15:13:26.366 UTC [42] LOG: aborting any active transactions
2022-04-02 15:13:26.368 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1
2022-04-02 15:13:26.369 UTC [46] LOG: shutting down
2022-04-02 15:13:26.383 UTC [42] LOG: database system is shut down
103:M 02 Apr 2022 15:13:26.414 # User requested shutdown...
103:M 02 Apr 2022 15:13:26.414 * Saving the final RDB snapshot before exiting.
103:M 02 Apr 2022 15:13:26.415 * DB saved on disk
103:M 02 Apr 2022 15:13:26.415 # Redis is now ready to exit, bye bye...
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && git reset --hard failed with return #<Process::Status: pid 132 exit 128>
Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"code", "cmd"=>["git reset --hard", "git clean -f", "git remote set-branches --add origin main", "git remote set-branches origin $version", "git fetch --depth 1 origin $version", "git checkout $version", "mkdir -p tmp", "chown discourse:www-data tmp", "mkdir -p tmp/pids", "mkdir -p tmp/sockets", "touch tmp/.gitkeep", "mkdir -p /shared/log/rails", "bash -c \"touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log\"", "bash -c \"ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log $home/log\"", "bash -c \"mkdir -p /shared/{uploads,backups}\"", "bash -c \"ln -s /shared/{uploads,backups} $home/public\"", "bash -c \"mkdir -p /shared/tmp/{backups,restores}\"", "bash -c \"ln -s /shared/tmp/{backups,restores} $home/tmp\"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp", "find public/plugins/ -maxdepth 1 -xtype l -delete"]}
bootstrap failed with exit code 128
** 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.
8a2a9754c5d0f9d252a6a6ebd22dac970389c2a21a58ca39a25e867b30e17396