[Bug] relation "xxx" does not exist 服务器端数据库版本使用时报错无relation

[BertramRay]

📦 部署环境

Vercel

📌 软件版本

v1.17.7

💻 系统环境

Ubuntu

🌐 浏览器

Chrome

🐛 问题描述

Sorry, the server seems to be experiencing some difficulties and is temporarily unable to complete your request. Please try again later. Error Details text relation "user_installed_plugins" does not exist Request Failed Sorry, the server seems to be experiencing some difficulties and is temporarily unable to complete your request. Please try again later.
relation "topics" does not exist

📷 复现步骤

1. 使用 vercel 创建pg （Neon）
   
2. 配置环境变量
   
3. 在vercel上部署main分支，部署正常无报错
   
4. 登录使用时出现缺少relation的报错提示

🚦 期望结果

不清楚为什么会没有relations，是需要对pg执行什么脚本吗？没有在官方文档中看到

📝 补充信息

No response

[lobehubbot]

👀 @BertramRay

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

@BertramRay Hello there! I'm a bot named Dosu, here to help you with bug fixes, questions, and contributions. Let's tackle this issue together!

You are encountering "relation does not exist" errors because the necessary database migrations have not been executed. To resolve this, you need to run the database migration scripts on your PostgreSQL instance. This will create the required tables and relations in your database.

Here are the steps to fix this:

1. Ensure Environment Variables are Set: Make sure all required environment variables are correctly set in Vercel. Missing variables can cause database migration issues.

   # Example environment variables
   DATABASE_URL=postgres://username:password@host:port/database
   NEXT_PUBLIC_SERVICE_MODE=server
   DATABASE_DRIVER=node  # if using Node Postgres

2. Run Database Migrations: Execute the migration scripts to apply the necessary database schema. You can use a common migration tool like knex or the provided scripts in the package.json.

   For example, using knex:

   npx knex migrate:latest

   Or using the provided scripts in package.json:

   npm run db:migrate

   This will apply all pending migrations and create the necessary database schema.

3. Verify Tables and Relations: Ensure that the following tables and relations exist in your PostgreSQL database:

   • agents
   • agentsFiles
   • agentsKnowledgeBases
   • asyncTasks
   • agentsTags
   • plugins
   • pluginsTags
   • tags
   • files
   • knowledgeBases
   • messages
   • messagesFiles
   • unstructuredChunks
   • sessionGroups
   • sessions
   • topics
   • agentsToSessions
   • filesToSessions
   • users
   • user_settings
   • user_subscriptions
   • user_budgets
   • user_installed_plugins
   • message_plugins
   • message_tts
   • message_translates
   • message_queries
   • message_query_chunks
   • message_chunks

By setting the environment variables and running the migration scripts, you should be able to resolve the "relation does not exist" errors ^[1][2][3].

To continue talking to Dosu, mention @dosu.

[dosubot[bot]]

The error "relation 'xxx' does not exist" when using the server-side database on Vercel with PostgreSQL is likely due to database migration issues. To resolve this, you need to ensure that all environment variables required for the server-side database are filled in before deployment. This includes the DATABASE_URL and other necessary variables.

Here are the steps to resolve this issue:

1. Ensure all environment variables are correctly set:

   • DATABASE_URL
   • NEXT_PUBLIC_SERVICE_MODE=server
   • If using Node Postgres, also set DATABASE_DRIVER=node

2. Redeploy the latest commit after setting the environment variables to ensure the database migrations are applied correctly.

Here is an example of setting the environment variables for Serverless Postgres:

# Serverless Postgres DB Url
DATABASE_URL=postgres://username:password@host:port/database

# Specify service mode as server, otherwise it will not enter the server-side database
NEXT_PUBLIC_SERVICE_MODE=server

For Node Postgres:

# Node Postgres DB Url
DATABASE_URL=postgres://username:password@host:port/database

# Specify Postgres database driver as node
DATABASE_DRIVER=node

# Specify service mode as server, otherwise it will not enter the server-side database
NEXT_PUBLIC_SERVICE_MODE=server

After setting these variables, redeploy the latest commit to apply the changes ^[1].

To continue talking to Dosu, mention @dosu.

[BertramRay]

已解决

vercel build command 需要使用命令 NODE_OPTIONS=--max-old-space-size=6144 npm run build 而不是 NODE_OPTIONS=--max-old-space-size=6144 next build, 后者才会触发 postbuild 指令，db 迁移指令在 postbuild 指令中

[Fitmavincent]

请问是 NODE_OPTIONS=--max-old-space-size=6144 npm run build 命令才能触发postbuild对吗？

[arvinxx]

对

[Fitmavincent]

我想问问你是直接改 vercel.json里的build command吗？我尝试从 Build & Development Settings里面override Build Command, 但是new deployment 依然遵从旧的 next build 命令

[Fitmavincent]

Need to change the buildCommand in vercel.json then push to deploy. The build log should see postbuild and postgres data migration

[lobehubbot]

✅ @BertramRay

This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题，可以留言并回复。