我在升级最新的discourse时遇到错误

升级最新版 Discourse 时遇到错误:

Get:13 https://dl.yarnpkg.com/debian stable/main all Packages [10.9 kB]
Get:14 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages [8,669 B]
Err:15 http://apt.postgresql.org/pub/repos/apt -pgdg Release
  404  未找到 [IP: 147.75.85.69 80]
Get:16 https://dl.yarnpkg.com/debian stable/main amd64 Packages [10.9 kB]
Get:17 http://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 Packages [318 kB]
Reading package lists...

I, [2024-05-19T08:52:40.856728 #1]  INFO -- : Terminating async processes
I, [2024-05-19T08:52:40.856789 #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: 34
I, [2024-05-19T08:52:40.856844 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 96
96:signal-handler (1716108760) Received SIGTERM scheduling shutdown...
2024-05-19 08:52:40.862 UTC [34] LOG:  received fast shutdown request
2024-05-19 08:52:40.865 UTC [34] LOG:  aborting any active transactions
2024-05-19 08:52:40.875 UTC [34] LOG:  background worker "logical replication launcher" (PID 49) exited with exit code 1
2024-05-19 08:52:40.879 UTC [44] LOG:  shutting down
96:M 19 May 2024 08:52:40.909 # User requested shutdown...
96:M 19 May 2024 08:52:40.909 * Saving the final RDB snapshot before exiting.
2024-05-19 08:52:40.957 UTC [34] LOG:  database system is shut down
96:M 19 May 2024 08:52:40.988 * DB saved on disk
96:M 19 May 2024 08:52:40.988 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && apt-get update failed with return #<Process::Status: pid 500 exit 100>
Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=>"$home", "cmd"=>["apt-get update"]}
bootstrap failed with exit code 100
** 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.
369a74ec6c3081026b2553dacc13d62c6d27881d8b5797fbec26c4d257afdc70

我再次编辑了 file.yml 文件,用于:

我认为 @merefield 编辑了他的插件以删除此内容:

# 配置 GPT
#    - exec:
#        cd: $home
#        cmd:
#          - sudo apt-get install wget ca-certificates
#    - exec:
#        cd: $home
#        cmd:
#          - wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add -
#    - exec:
#        cd: $home
#        cmd:
#          - sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt/ `lsb_release -cs`-pgdg main" >> /et'
#    - exec:
#        cd: $home
#        cmd:
#          - apt-get update
#    - exec:
#        cd: $home
#        cmd:
#          - apt-get -y install -y postgresql-server-dev-${PG_MAJOR}
#    - exec:
#        cd: $home/tmp
#        cmd:
#          - git clone https://github.com/neondatabase/pg_embedding.git
#    - exec:
#        cd: $home/tmp/pg_embedding
#        cmd:
#          - make PG_CONFIG=/usr/lib/postgresql/${PG_MAJOR}/bin/pg_config
#    - exec:
#        cd: $home/tmp/pg_embedding
#        cmd:
#          - make PG_CONFIG=/usr/lib/postgresql/${PG_MAJOR}/bin/pg_config install
#    - exec:
#        cd: $home
#        cmd:
#          - su postgres -c 'psql discourse -c "create extension if not exists embedding;"'
#    - exec:
#        cd: $home
#        cmd:
#          - su postgres -c 'psql discourse -c "DROP INDEX IF EXISTS hnsw_index_on_chatbot_post_embeddings;"'
#    - exec:
#        cd: $home
#        cmd:
#          - su postgres -c 'psql discourse -c "DROP EXTENSION IF EXISTS embedding;"'
#    - exec:
#        cd: $home
#        cmd:
#          - su postgres -c 'psql discourse -c "ALTER EXTENSION vector UPDATE;"'
# 结束配置 GPT

但我不太确定我之前的索引是否仍然存在?

我很抱歉,我无法无限期地为几个月前的更改提供免费支持。

这些行早已不必要了。

这项技术一直处于尖端且快速变化的状态,因此在提供免费服务的同时,无法避免地会产生破坏性更改。

我已经免费私下帮助了许多用户解决此更改带来的问题。但是,我不再有时间和资源可以独自免费进行此类工作。

此更改在当时已得到清晰沟通。不幸的是,应 CDCK 的礼貌要求,主题中的通信每月都会被清除。

如果您需要我进行更深入的研究,我可以按合同进行。

1 个赞

您是否也将信息添加到了第一个帖子?这样的话,它仍然可以在编辑历史记录中找到,就像这些说明一样

2 个赞