How do I fix this db error
how do i fix this error
[ Server!] error: database "OpenSaaS-cd8dfa8fd6" does not exist
[ Server!] at /Users/haarismian/Development/Wisement/wisement/app/node_modules/pg-pool/index.js:45:11
[ Server!] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
x.js:103:5)
[ Server!] at startPgBoss (/Users/haarismian/Development/Wisement/wisement/app/.wasp/out/sdk/wasp/server/jobs/core/pgBoss/pgBoss.ts:63:5)
[ Server!] at startServer (/Users/haarismian/Development/Wisement/wisement/app/.wasp/out/server/src/server.ts:14:3) {
[ Server!] length: 105,
[ Server!] severity: 'FATAL',
[ Server!] code: '3D000',
[ Server!] detail: undefined,
[ Server!] hint: undefined,
[ Server!] position: undefined,
[ Server!] internalPosition: undefined,
[ Server!] internalQuery: undefined,
[ Server!] where: undefined,
[ Server!] schema: undefined,
[ Server!] table: undefined,
[ Server!] column: undefined,
[ Server!] dataType: undefined,
[ Server!] constraint: undefined,
[ Server!] file: 'postinit.c',
[ Server!] line: '1019',
[ Server!] routine: 'InitPostgres'
[ Server!] }
[ Server ] Server listening on port 3001
[ Server!] node:internal/process/promises:289
[ Server!] triggerUncaughtException(err, true /* fromPromise */);
[ Server!] ^
[ Server!]
[ Server!] [UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#<PgBoss>".] {
[ Server!] code: 'ERR_UNHANDLED_REJECTION'
[ Server!] }
2 Replies
Hi @haarismian. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
The error message you're seeing indicates that the PostgreSQL database "OpenSaaS-cd8dfa8fd6" does not exist. This could be due to a number of reasons, such as the database not being properly initialized or a connection issue.
Here are a few steps you can take to troubleshoot this issue:
1. Check your database URL: Ensure that the database URL in your Wasp project is correct. The URL should point to the correct location of your PostgreSQL database.
2. Initialize the database: If the database has not been initialized, you can do so by running the
wasp db migrate-dev command. This command will create the database and apply any pending migrations.
3. Check Docker permissions: If you're using Docker to run your PostgreSQL database, ensure that you have the necessary permissions to connect to the Docker daemon. You might need to adjust your Docker permissions or install Docker Desktop if you haven't already. You can refer to these instructions (https://discord.com/channels/686873244791210014/1193138068195119104) from a similar issue.
4. Check for existing .wasp folder: If there's an existing .wasp folder, try deleting it, running the database, and then doing wasp db migrate-dev again. This was suggested in a similar issue (https://discord.com/channels/686873244791210014/1193138068195119104).
If none of these steps resolve your issue, it would be helpful to have more information about your setup. Are you using Docker to run your database? What operating system are you using? Have you made any recent changes to your Wasp project that might have caused this issue?
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @haarismian, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Did you check what the bot asked? 🙂