Twenty•3mo ago

Can't host Twenty - twenty-db-1 is unhealthy

Hey, I've been following this guide here via Option 2. https://twenty.com/developers/section/self-hosting/docker-compose I use Portainer to host it. In the end I run into the following error: Pull complete server Pulled worker Pulled Network twenty_default Creating Network twenty_default Created Container twenty-change-vol-ownership-1 Creating Container twenty-db-1 Creating Container twenty-change-vol-ownership-1 Created Container twenty-db-1 Created Container twenty-server-1 Creating Container twenty-server-1 Created Container twenty-worker-1 Creating Container twenty-worker-1 Created Container twenty-change-vol-ownership-1 Starting Container twenty-db-1 Starting Container twenty-change-vol-ownership-1 Started Container twenty-db-1 Started Container twenty-db-1 Waiting Container twenty-change-vol-ownership-1 Waiting Container twenty-change-vol-ownership-1 Exited Container twenty-db-1 Error dependency failed to start: container twenty-db-1 is unhealthy It's the same compose and env file as in the example and changed the strings as asked.

35 Replies

Freebios•3mo ago

Hi there, do you have any error log on the database container ? If not, another lead could be that by default the health check expect the database to be healthy in about 50s, depending on your setup it might be a bit too short.

DultusOP•3mo ago

I can't get it deployed so there's no container yet. :/ I set it up to 150 seconds. Still no success though. Still the same error. Tried removing the health check to see any error logs:

postgresql 09:41:44.99 ERROR ==> The POSTGRESQL_PASSWORD environment variable is empty or not set. Set the environment variable ALLOW_EMPTY_PASSWORD=yes to allow the container to be started with blank passwords. This is recommended only for development.

Tried setting the password on the stack and container. In both cases the environment for the container doesn't take it it seems.

DultusOP•3mo ago

DultusOP•3mo ago

It just nulls the password and/or the ALLOW_EMPTY_PASSWORD flag.

DultusOP•3mo ago

The logs of the server:

[Nest] 1 - 09/13/2024, 9:44:47 AM ERROR [TypeOrmModule] Unable to connect to the database (metadata). Retrying (9)... Error: getaddrinfo ENOTFOUND db at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26) [Nest] 1 - 09/13/2024, 9:44:47 AM ERROR [ExceptionHandler] getaddrinfo ENOTFOUND db Error: getaddrinfo ENOTFOUND db at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26)

As URL I tried it with http://localhost:3000 and http://server.local:3000 (how I'll actually access it in the end)

Freebios•3mo ago

It seems to try to resolve the database address using 'db'. I’m not familiar with portainer, but I would say that the right domain in your case would be twenty-db-1 You could try to update the PG_DATABASE_HOST env?

DultusOP•3mo ago

[Nest] 1 - 09/13/2024, 11:02:20 AM ERROR [ExceptionHandler] getaddrinfo ENOTFOUND twenty-db-1 Error: getaddrinfo ENOTFOUND twenty-db-1 at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26)

Basically the same error. Though that's probably because the db can't run?

postgresql 11:02:54.76 INFO ==> Starting PostgreSQL setup postgresql 11:02:54.78 INFO ==> Validating settings in POSTGRESQL_* env vars.. postgresql 11:02:54.78 ERROR ==> The POSTGRESQL_PASSWORD environment variable is empty or not set. Set the environment variable ALLOW_EMPTY_PASSWORD=yes to allow the container to be started with blank passwords. This is recommended only for development. postgresql 11:02:54.78 ERROR ==> The POSTGRESQL_PASSWORD environment variable is empty or not set. Set the environment variable ALLOW_EMPTY_PASSWORD=yes to allow the container to be started with blank passwords. This is recommended only for development.

The network settings say that they're all in the same network but the database doesn't seem to get any address.

DultusOP•3mo ago

Portainer in generell is just an interface that basically does the commands via UI. So there shouldn't be any difference. It's a regular Docker compose.

Freebios•3mo ago

Then ok the domain isn’t the issue 😅 On your screen I see the db as running, but you don’t have any meaningful log? It’s not hanging either?

DultusOP•3mo ago

The DB error is the POSTGRESQL_PASSWORD issue And the DB can't draw a network address either. The server and worker can.

Freebios•3mo ago

Oh I see, have you tried to set the POSTGRES_ADMIN_PASSWORD env?

DultusOP•3mo ago

Ah, yeah. Now it's running. Just asked ChatGPT as well and gave me that info haha. Might want to add that to the startup guide. Okay, now the three are running - the "twenty-change-vol-ownership-1" exits itself. How do I access the twenty interface now? http://server.local:3000/ refuses the connection.

Freebios•3mo ago

localhost:3000 doesn’t do the trick? (Or server.local is binded to localhost?)

DultusOP•3mo ago

Ah, the server gives me an error again:

[Nest] 1 - 09/13/2024, 11:20:06 AM ERROR [ExceptionHandler] JwtStrategy requires a secret or key TypeError: JwtStrategy requires a secret or key at new JwtStrategy (/app/node_modules/passport-jwt/lib/strategy.js:45:15) at new MixinStrategy (/app/node_modules/@nestjs/passport/dist/passport/passport.strategy.js:32:13) at new JwtAuthStrategy (/app/packages/twenty-server/dist/src/engine/core-modules/auth/strategies/jwt.auth.strategy.js:86:9) at Injector.instantiateClass (/app/node_modules/@nestjs/core/injector/injector.js:351:19) at callback (/app/node_modules/@nestjs/core/injector/injector.js:56:45) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Injector.resolveConstructorParams (/app/node_modules/@nestjs/core/injector/injector.js:136:24) at async Injector.loadInstance (/app/node_modules/@nestjs/core/injector/injector.js:61:13) at async Injector.loadProvider (/app/node_modules/@nestjs/core/injector/injector.js:88:9) at async /app/node_modules/@nestjs/core/injector/instance-loader.js:56:13

Ah, whoops, I know that one I think. Yup. I added by local env.env with the tokens but they were still commented out so they weren't there. :facepalm: Okay, runs now. Thank you very much!

Freebios•3mo ago

🤩

DultusOP•3mo ago

Okay, next issue though. As per documentation I wasn't able to login so I ran

docker exec -it twenty-server-1 yarn

➤ YN0000: ┌ Link step
➤ YN0007: │ esbuild@npm:0.18.20 must be built because it never has been before o                                           r the last one failed
➤ YN0007: │ @swc/core@npm:1.7.6 [40dfc] must be built because it never has been                                            before or the last one failed
➤ YN0008: │ bcrypt@npm:5.1.1 must be rebuilt because its dependency tree changed
➤ YN0007: │ better-sqlite3@npm:9.6.0 must be built because it never has been bef                                           ore or the last one failed
➤ YN0007: │ core-js@npm:3.38.0 must be built because it never has been before or                                            the last one failed
➤ YN0007: │ esbuild@npm:0.19.12 must be built because it never has been before o                                           r the last one failed
➤ YN0007: │ esbuild@npm:0.23.0 must be built because it never has been before or                                            the last one failed
➤ YN0008: │ sharp@npm:0.32.6 must be rebuilt because its dependency tree changed
➤ YN0007: │ @nestjs/core@npm:9.4.3 [0915e] must be built because it never has be                                           en before or the last one failed
➤ YN0007: │ @sentry/profiling-node@npm:1.3.5 [0915e] must be built because it ne                                           ver has been before or the last one failed
➤ YN0007: │ @swc/core@npm:1.3.107 [0915e] must be built because it never has bee                                           n before or the last one failed
➤ YN0007: │ msw@npm:2.3.5 [0915e] must be built because it never has been before                                            or the last one failed
➤ YN0007: │ esbuild@npm:0.21.5 must be built because it never has been before or                                            the last one failed
➤ YN0007: │ iframe-resizer@npm:4.4.5 must be built because it never has been bef                                           ore or the last one failed
➤ YN0008: │ msgpackr-extract@npm:3.0.3 must be rebuilt because its dependency tr                                           ee changed
➤ YN0007: │ core-js@npm:2.6.12 must be built because it never has been before or                                            the last one failed
➤ YN0007: │ @apollo/protobufjs@npm:1.2.7 must be built because it never has been                                            before or the last one failed
➤ YN0007: │ core-js-pure@npm:3.38.0 must be built because it never has been befo                                           re or the last one failed
➤ YN0007: │ nice-napi@npm:1.0.2 must be built because it never has been before o                                           r the last one failed
➤ YN0007: │ @apollo/protobufjs@npm:1.2.6 must be built because it never has been                                            before or the last one failed
➤ YN0007: │ es5-ext@npm:0.10.64 must be built because it never has been before o                                           r the last one failed
➤ YN0009: │ nice-napi@npm:1.0.2 couldn't be built successfully (exit code 1, log                                           s can be found here: /tmp/xfs-75907939/build.log)
➤ YN0007: │ nx@npm:18.3.3 [0915e] must be built because it never has been before                                            or the last one failed
➤ YN0009: │ nx@npm:18.3.3 [0915e] couldn't be built successfully (exit code 129,                                            logs can be found here: /tmp/xfs-99b731bb/build.log)
➤ YN0000: └ Completed in 2m 54s

➤ YN0000: ┌ Link step
➤ YN0007: │ esbuild@npm:0.18.20 must be built because it never has been before o                                           r the last one failed
➤ YN0007: │ @swc/core@npm:1.7.6 [40dfc] must be built because it never has been                                            before or the last one failed
➤ YN0008: │ bcrypt@npm:5.1.1 must be rebuilt because its dependency tree changed
➤ YN0007: │ better-sqlite3@npm:9.6.0 must be built because it never has been bef                                           ore or the last one failed
➤ YN0007: │ core-js@npm:3.38.0 must be built because it never has been before or                                            the last one failed
➤ YN0007: │ esbuild@npm:0.19.12 must be built because it never has been before o                                           r the last one failed
➤ YN0007: │ esbuild@npm:0.23.0 must be built because it never has been before or                                            the last one failed
➤ YN0008: │ sharp@npm:0.32.6 must be rebuilt because its dependency tree changed
➤ YN0007: │ @nestjs/core@npm:9.4.3 [0915e] must be built because it never has be                                           en before or the last one failed
➤ YN0007: │ @sentry/profiling-node@npm:1.3.5 [0915e] must be built because it ne                                           ver has been before or the last one failed
➤ YN0007: │ @swc/core@npm:1.3.107 [0915e] must be built because it never has bee                                           n before or the last one failed
➤ YN0007: │ msw@npm:2.3.5 [0915e] must be built because it never has been before                                            or the last one failed
➤ YN0007: │ esbuild@npm:0.21.5 must be built because it never has been before or                                            the last one failed
➤ YN0007: │ iframe-resizer@npm:4.4.5 must be built because it never has been bef                                           ore or the last one failed
➤ YN0008: │ msgpackr-extract@npm:3.0.3 must be rebuilt because its dependency tr                                           ee changed
➤ YN0007: │ core-js@npm:2.6.12 must be built because it never has been before or                                            the last one failed
➤ YN0007: │ @apollo/protobufjs@npm:1.2.7 must be built because it never has been                                            before or the last one failed
➤ YN0007: │ core-js-pure@npm:3.38.0 must be built because it never has been befo                                           re or the last one failed
➤ YN0007: │ nice-napi@npm:1.0.2 must be built because it never has been before o                                           r the last one failed
➤ YN0007: │ @apollo/protobufjs@npm:1.2.6 must be built because it never has been                                            before or the last one failed
➤ YN0007: │ es5-ext@npm:0.10.64 must be built because it never has been before o                                           r the last one failed
➤ YN0009: │ nice-napi@npm:1.0.2 couldn't be built successfully (exit code 1, log                                           s can be found here: /tmp/xfs-75907939/build.log)
➤ YN0007: │ nx@npm:18.3.3 [0915e] must be built because it never has been before                                            or the last one failed
➤ YN0009: │ nx@npm:18.3.3 [0915e] couldn't be built successfully (exit code 129,                                            logs can be found here: /tmp/xfs-99b731bb/build.log)
➤ YN0000: └ Completed in 2m 54s

Before that:

➤ YN0002: │ twenty-front@workspace:packages/twenty-front doesn't provide react (pd36df), requested by @xyflow/react.
➤ YN0002: │ twenty-front@workspace:packages/twenty-front doesn't provide react-dom (p66e11), requested by @xyflow/react.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide @apollo/gateway (pc2c97), requested by @ptc-org/nestjs-query-graphql.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide @types/inquirer (pb95bf), requested by nest-commander.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide ts-morph (pc2108), requested by @nestjs/graphql and other dependencies.

➤ YN0002: │ twenty-front@workspace:packages/twenty-front doesn't provide react (pd36df), requested by @xyflow/react.
➤ YN0002: │ twenty-front@workspace:packages/twenty-front doesn't provide react-dom (p66e11), requested by @xyflow/react.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide @apollo/gateway (pc2c97), requested by @ptc-org/nestjs-query-graphql.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide @types/inquirer (pb95bf), requested by nest-commander.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide ts-morph (pc2108), requested by @nestjs/graphql and other dependencies.

➤ YN0060: │ @envelop/core is listed by your project with version 4.0.3 (p1c83a),                                                      which doesn't satisfy what @envelop/on-resolve requests (^5.0.0).
➤ YN0060: │ @nestjs/common is listed by your project with version 9.4.3 (p60764)                                                     , which doesn't satisfy what @graphql-yoga/nestjs and other dependencies request                                                      (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/common is listed by your project with version 9.4.3 (p65958)                                                     , which doesn't satisfy what @golevelup/nestjs-discovery (via nest-commander) an                                                     d other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/core is listed by your project with version 9.4.3 (p66425),                                                      which doesn't satisfy what @golevelup/nestjs-discovery (via nest-commander) and                                                      other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/core is listed by your project with version 9.4.3 (p7a89f)

➤ YN0060: │ @envelop/core is listed by your project with version 4.0.3 (p1c83a),                                                      which doesn't satisfy what @envelop/on-resolve requests (^5.0.0).
➤ YN0060: │ @nestjs/common is listed by your project with version 9.4.3 (p60764)                                                     , which doesn't satisfy what @graphql-yoga/nestjs and other dependencies request                                                      (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/common is listed by your project with version 9.4.3 (p65958)                                                     , which doesn't satisfy what @golevelup/nestjs-discovery (via nest-commander) an                                                     d other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/core is listed by your project with version 9.4.3 (p66425),                                                      which doesn't satisfy what @golevelup/nestjs-discovery (via nest-commander) and                                                      other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/core is listed by your project with version 9.4.3 (p7a89f)

And so on.

Freebios•3mo ago

Try

docker exec -it twenty-server-1 yarn install

DultusOP•3mo ago

Yeah, that returned me this:

➤ YN0000: · Yarn 4.4.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 1s 391ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ @envelop/core is listed by your project with version 4.0.3 (p1c83a), which doesn't satisfy what @envelop/on-resolve requests (^5.0.0).
➤ YN0060: │ @nestjs/common is listed by your project with version 9.4.3 (p60764), which doesn't satisfy what @graphql-yoga/nestjs and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/common is listed by your project with version 9.4.3 (p65958), which doesn't satisfy what @golevelup/nestjs-discovery (via nest-commander) and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/core is listed by your project with version 9.4.3 (p66425), which doesn't satisfy what @golevelup/nestjs-discovery (via nest-commander) and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/core is listed by your project with version 9.4.3 (p7a89f), which doesn't satisfy what @graphql-yoga/nestjs and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @ptc-org/nestjs-query-core is listed by your project with version 4.4.0 (p1c853), which doesn't satisfy what @ptc-org/nestjs-query-typeorm requests (4.2.0).
➤ YN0060: │ @ptc-org/nestjs-query-core is listed by your project with version 4.4.0 (p64638), which doesn't satisfy what @ptc-org/nestjs-query-typeorm requests (4.2.0).
➤ YN0060: │ @swc/core is listed by your project with version 1.3.107 (p2dbb7), which doesn't satisfy what @swc-node/core (via @swc-node/register) and other dependencies request (^1.4.13).
➤ YN0060: │ esbuild is listed by your project with version 0.23.0 (pdd602), which doesn't satisfy what esbuild-plugin-svgr and other dependencies request (~0.19.1).

➤ YN0000: · Yarn 4.4.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 1s 391ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ @envelop/core is listed by your project with version 4.0.3 (p1c83a), which doesn't satisfy what @envelop/on-resolve requests (^5.0.0).
➤ YN0060: │ @nestjs/common is listed by your project with version 9.4.3 (p60764), which doesn't satisfy what @graphql-yoga/nestjs and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/common is listed by your project with version 9.4.3 (p65958), which doesn't satisfy what @golevelup/nestjs-discovery (via nest-commander) and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/core is listed by your project with version 9.4.3 (p66425), which doesn't satisfy what @golevelup/nestjs-discovery (via nest-commander) and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @nestjs/core is listed by your project with version 9.4.3 (p7a89f), which doesn't satisfy what @graphql-yoga/nestjs and other dependencies request (but they have non-overlapping ranges!).
➤ YN0060: │ @ptc-org/nestjs-query-core is listed by your project with version 4.4.0 (p1c853), which doesn't satisfy what @ptc-org/nestjs-query-typeorm requests (4.2.0).
➤ YN0060: │ @ptc-org/nestjs-query-core is listed by your project with version 4.4.0 (p64638), which doesn't satisfy what @ptc-org/nestjs-query-typeorm requests (4.2.0).
➤ YN0060: │ @swc/core is listed by your project with version 1.3.107 (p2dbb7), which doesn't satisfy what @swc-node/core (via @swc-node/register) and other dependencies request (^1.4.13).
➤ YN0060: │ esbuild is listed by your project with version 0.23.0 (pdd602), which doesn't satisfy what esbuild-plugin-svgr and other dependencies request (~0.19.1).

(...)

➤ YN0002: │ twenty-front@workspace:packages/twenty-front doesn't provide react (pd36df), requested by @xyflow/react.
➤ YN0002: │ twenty-front@workspace:packages/twenty-front doesn't provide react-dom (p66e11), requested by @xyflow/react.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide @apollo/gateway (pc2c97), requested by @ptc-org/nestjs-query-graphql.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide @types/inquirer (pb95bf), requested by nest-commander.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide ts-morph (pc2108), requested by @nestjs/graphql and other dependencies.
➤ YN0002: │ twenty@workspace:. doesn't provide @envelop/core (p26b5b), requested by @envelop/on-resolve.
➤ YN0002: │ twenty@workspace:. doesn't provide @graphiql/react (pe7fb2), requested by @graphiql/plugin-explorer.
➤ YN0002: │ twenty@workspace:. doesn't provide @nestjs/graphql (p41b76), requested by @nestjs/apollo.
➤ YN0002: │ twenty@workspace:. doesn't provide @storybook/components (p63b67), requested by storybook-addon-cookie and other dependencies.

➤ YN0002: │ twenty-front@workspace:packages/twenty-front doesn't provide react (pd36df), requested by @xyflow/react.
➤ YN0002: │ twenty-front@workspace:packages/twenty-front doesn't provide react-dom (p66e11), requested by @xyflow/react.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide @apollo/gateway (pc2c97), requested by @ptc-org/nestjs-query-graphql.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide @types/inquirer (pb95bf), requested by nest-commander.
➤ YN0002: │ twenty-server@workspace:packages/twenty-server doesn't provide ts-morph (pc2108), requested by @nestjs/graphql and other dependencies.
➤ YN0002: │ twenty@workspace:. doesn't provide @envelop/core (p26b5b), requested by @envelop/on-resolve.
➤ YN0002: │ twenty@workspace:. doesn't provide @graphiql/react (pe7fb2), requested by @graphiql/plugin-explorer.
➤ YN0002: │ twenty@workspace:. doesn't provide @nestjs/graphql (p41b76), requested by @nestjs/apollo.
➤ YN0002: │ twenty@workspace:. doesn't provide @storybook/components (p63b67), requested by storybook-addon-cookie and other dependencies.

If you need the entire log, let me know but I think you probably know what the issue might be seeing this.

Freebios•3mo ago

Actually it’s getting a bit out of my scope 😅

DultusOP•3mo ago

I'd appreciate if you'd have someone who's scope involves this. 🙂 But thank you so far nevertheless! At least I was able to run the application once. x)

Freebios•3mo ago

The team is quite busy at this time, I’ll try to repro locally

DultusOP•3mo ago

Much appreciated

Freebios•3mo ago

Actually it doesn't seem to be a blocking issue, did you try to run the next command in the guide ?

docker exec -it twenty-server-1 npx nx database:reset

docker exec -it twenty-server-1 npx nx database:reset

I got the same error but was able to reset db

DultusOP•3mo ago

Yeah, I did but the application doesn't start afterwards:

2024-09-14 14:55:08.696 GMT [85] LOG:  database system was shut down at 2024-09-14 14:55:06 GMT
2024-09-14 14:55:08.710 GMT [1] LOG:  database system is ready to accept connections
2024-09-14 14:55:13.535 GMT [89] ERROR:  no schema has been selected to create in
2024-09-14 14:55:13.535 GMT [89] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:13.558 GMT [90] ERROR:  no schema has been selected to create in
2024-09-14 14:55:13.558 GMT [90] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:13.734 GMT [91] ERROR:  no schema has been selected to create in
2024-09-14 14:55:13.734 GMT [91] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:13.762 GMT [92] ERROR:  no schema has been selected to create in
2024-09-14 14:55:13.762 GMT [92] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:14.286 GMT [98] ERROR:  no schema has been selected to create in
2024-09-14 14:55:14.286 GMT [98] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:14.300 GMT [97] ERROR:  no schema has been selected to create in
2024-09-14 14:55:14.300 GMT [97] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:14.368 GMT [99] ERROR:  no schema has been selected to create in
2024-09-14 14:55:14.368 GMT [99] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:14.494 GMT [104] ERROR:  no schema has been selected to create in
2024-09-14 14:55:14.494 GMT [104] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"

2024-09-14 14:55:08.696 GMT [85] LOG:  database system was shut down at 2024-09-14 14:55:06 GMT
2024-09-14 14:55:08.710 GMT [1] LOG:  database system is ready to accept connections
2024-09-14 14:55:13.535 GMT [89] ERROR:  no schema has been selected to create in
2024-09-14 14:55:13.535 GMT [89] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:13.558 GMT [90] ERROR:  no schema has been selected to create in
2024-09-14 14:55:13.558 GMT [90] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:13.734 GMT [91] ERROR:  no schema has been selected to create in
2024-09-14 14:55:13.734 GMT [91] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:13.762 GMT [92] ERROR:  no schema has been selected to create in
2024-09-14 14:55:13.762 GMT [92] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:14.286 GMT [98] ERROR:  no schema has been selected to create in
2024-09-14 14:55:14.286 GMT [98] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:14.300 GMT [97] ERROR:  no schema has been selected to create in
2024-09-14 14:55:14.300 GMT [97] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:14.368 GMT [99] ERROR:  no schema has been selected to create in
2024-09-14 14:55:14.368 GMT [99] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
2024-09-14 14:55:14.494 GMT [104] ERROR:  no schema has been selected to create in
2024-09-14 14:55:14.494 GMT [104] STATEMENT:  CREATE EXTENSION IF NOT EXISTS "uuid-ossp"

And can't access the application from web anymore either. Okay, I deleted the volumes and just literally restart the entire thing and now it works. Weird. But yeah, I'm able to use and enter data now. I guess some sort of hickup. x)

Freebios•3mo ago

I'm wondering if the database:reset job resets everything and requires to run migration again, it seems from the log that the database was in poor state 😄 Well I'm glad you got to start the app !

    "database:reset": {
      "executor": "nx:run-commands",
      "dependsOn": ["build"],
      "options": {
        "cwd": "packages/twenty-server",
        "commands": [
          "nx ts-node-no-deps -- ./scripts/truncate-db.ts",
          "nx ts-node-no-deps -- ./scripts/setup-db.ts",
          "nx database:migrate",
          "nx command-no-deps -- workspace:seed:dev"
        ],
        "parallel": false
      }
    }

    "database:reset": {
      "executor": "nx:run-commands",
      "dependsOn": ["build"],
      "options": {
        "cwd": "packages/twenty-server",
        "commands": [
          "nx ts-node-no-deps -- ./scripts/truncate-db.ts",
          "nx ts-node-no-deps -- ./scripts/setup-db.ts",
          "nx database:migrate",
          "nx command-no-deps -- workspace:seed:dev"
        ],
        "parallel": false
      }
    }

should have been good so hard to say then

charles•3mo ago

@Quentin G @Dultus we should actually not do yarn in production. Everything is built as it should be in the container. Could we remove this from the doc? Same for the database reset, we should NEVER do that on production. There is yarn database:init:prod command to be run the first time, which is already part of the setup script So @Dultus don't do the yarn and the reset, could you restart your setup without doing it, and from there if you stil have the login issue, could you share with us the error you have in your network tab (browser developer console)

Freebios•3mo ago

Yeah it requires installing a lot of dependencies, I’ll check if we can run migration without doing a yarn install

DultusOP•3mo ago

I mean it does work now! 😄 I don't know why the login worked though. After all I didn't change anything and deleted the volumes.

charles•3mo ago

so it's all good on your side @Dultus ? @Quentin G we should not have to do a yarn install? Why do we need it?

DultusOP•3mo ago

Yup!

Freebios•3mo ago

I don’t know to be honest, it’s legacy stuff that was here before me in the doc 😅

charles•3mo ago

ok! I think we should remove them and we should be all good! If someone faces an issue again we should fix the root cause but not recommending to run yarn as everythin is pre-bundled @Dultus great! closing the thread

Gaming

Programming

Can't host Twenty - twenty-db-1 is unhealthy