supabase_rest container constantly crashes

[empz]

I'm using latest Supabase CLI 2.22.12 on Windows 11 with Docker Desktop v4.40.0 and Node.js 20.18.2

Whenever I refresh my Next.js app during development which triggers a simple profile fetch on the database, the query seems to fail and the supabase_rest container restarts.

Assertion failed: *(&once->n) != 4 (threads.c: k5_once: 564)
09/May/2025:10:47:42 +0000: Starting PostgREST 12.1...
09/May/2025:10:47:42 +0000: Attempting to connect to the database...09/May/2025:10:47:42 +0000: Admin server listening on port 3001
09/May/2025:10:47:42 +0000: Listening on port 3000
Assertion failed: *(&once->n) != 4 (threads.c: k5_once: 564)
09/May/2025:10:47:43 +0000: Starting PostgREST 12.1...
09/May/2025:10:47:43 +0000: Admin server listening on port 3001
09/May/2025:10:47:43 +0000: Attempting to connect to the database...
09/May/2025:10:47:43 +0000: Listening on port 3000
09/May/2025:10:47:43 +0000: Listening for notifications on the "pgrst" channel
09/May/2025:10:47:43 +0000: Successfully connected to PostgreSQL 15.1 (Ubuntu 15.1-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
09/May/2025:10:47:43 +0000: Config reloaded
09/May/2025:10:47:43 +0000: Schema cache queried in 4.9 milliseconds
09/May/2025:10:47:43 +0000: Schema cache loaded 12 Relations, 13 Relationships, 3 Functions, 0 Domain Representations, 4 Media Type Handlers
09/May/2025:10:51:56 +0000: Starting PostgREST 12.1...
09/May/2025:10:51:56 +0000: Admin server listening on port 3001
09/May/2025:10:51:56 +0000: Attempting to connect to the database...
09/May/2025:10:51:56 +0000: Listening on port 3000
09/May/2025:10:51:56 +0000: Listening for notifications on the "pgrst" channel
09/May/2025:10:51:56 +0000: Successfully connected to PostgreSQL 15.1 (Ubuntu 15.1-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
09/May/2025:10:51:56 +0000: Config reloaded
09/May/2025:10:51:56 +0000: Schema cache queried in 7.0 milliseconds
09/May/2025:10:51:56 +0000: Schema cache loaded 12 Relations, 13 Relationships, 3 Functions, 0 Domain Representations, 4 Media Type Handlers
09/May/2025:10:53:56 +0000: Starting PostgREST 12.1...
09/May/2025:10:53:56 +0000: Admin server listening on port 3001
09/May/2025:10:53:56 +0000: Listening on port 3000
09/May/2025:10:53:56 +0000: Attempting to connect to the database...
Assertion failed: *(&once->n) != 4 (threads.c: k5_once: 564)
09/May/2025:10:53:58 +0000: Starting PostgREST 12.1...
09/May/2025:10:53:58 +0000: Admin server listening on port 3001
09/May/2025:10:53:58 +0000: Listening on port 3000
09/May/2025:10:53:58 +0000: Attempting to connect to the database...
09/May/2025:10:53:58 +0000: Successfully connected to PostgreSQL 15.1 (Ubuntu 15.1-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
09/May/2025:10:53:58 +0000: Listening for notifications on the "pgrst" channel
09/May/2025:10:53:58 +0000: Config reloaded
09/May/2025:10:53:58 +0000: Schema cache queried in 3.8 milliseconds
09/May/2025:10:53:58 +0000: Schema cache loaded 12 Relations, 13 Relationships, 3 Functions, 0 Domain Representations, 4 Media Type Handlers
09/May/2025:10:57:06 +0000: Starting PostgREST 12.1...
09/May/2025:10:57:06 +0000: Admin server listening on port 3001
09/May/2025:10:57:06 +0000: Attempting to connect to the database...
09/May/2025:10:57:06 +0000: Listening on port 3000
09/May/2025:10:57:06 +0000: Listening for notifications on the "pgrst" channel
09/May/2025:10:57:06 +0000: Successfully connected to PostgreSQL 15.1 (Ubuntu 15.1-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit
09/May/2025:10:57:06 +0000: Config reloaded
09/May/2025:10:57:06 +0000: Schema cache queried in 4.4 milliseconds

Not sure if that failed assertion are causing this or what.

[empz]

This is becoming extremely frustrating to the point I can't even use it. I've tried everything. Destroying the containers and re-pulling all images, restarted computer, upgraded everything to latest version.

This thing keeps crashing, constantly, and I need to work!

Assertion failed: destructors_set[keynum] == 0 (threads.c: krb5int_key_register: 353)

[Hallidayo]

Hi, I've moved this issue over from the supabase repo

[empz]

Not sure what else I can provide to help you replicate the issue. It's definitely a weird one...

[empz]

09/May/2025:16:35:44 +0000: Listening on port 3000


Assertion failed: *(&once->n) != 4 (threads.c: k5_once: 564)


09/May/2025:16:35:47 +0000: Starting PostgREST 12.1...


09/May/2025:16:35:47 +0000: Admin server listening on port 3001


09/May/2025:16:35:47 +0000: Attempting to connect to the database...


09/May/2025:16:35:47 +0000: Listening on port 3000


Assertion failed: *(&once->n) != 4 (threads.c: k5_once: 564)


09/May/2025:16:35:48 +0000: Starting PostgREST 12.1...


09/May/2025:16:35:48 +0000: Admin server listening on port 3001


09/May/2025:16:35:48 +0000: Attempting to connect to the database...


09/May/2025:16:35:48 +0000: Listening on port 3000


Assertion failed: *(&once->n) != 4 (threads.c: k5_once: 564)


09/May/2025:16:35:50 +0000: Starting PostgREST 12.1...


09/May/2025:16:35:50 +0000: Admin server listening on port 3001


09/May/2025:16:35:50 +0000: Attempting to connect to the database...


09/May/2025:16:35:50 +0000: Listening on port 3000


Assertion failed: *(&once->n) != 4 (threads.c: k5_once: 564)


09/May/2025:16:35:54 +0000: Starting PostgREST 12.1...


09/May/2025:16:35:54 +0000: Admin server listening on port 3001


09/May/2025:16:35:54 +0000: Attempting to connect to the database...


09/May/2025:16:35:54 +0000: Listening on port 3000


Assertion failed: *(&once->n) != 4 (threads.c: k5_once: 564)


09/May/2025:16:35:59 +0000: Starting PostgREST 12.1...


09/May/2025:16:35:59 +0000: Admin server listening on port 3001


09/May/2025:16:35:59 +0000: Attempting to connect to the database...


09/May/2025:16:35:59 +0000: Listening on port 3000


Assertion failed: (*mecherror_cmp)(r, pair->r) != 0 (errmap.h: mecherrmap_add: 197)

[sweatybridge]

It looks like our latest version is on 12.2.12 and there's already work to move it to 13.0.

I suspect you are running with an old version of PostgREST version locally. Could you try rm supabase/.temp/rest-version before running supabase start again?

[empz]

It looks like our latest version is on 12.2.12 and there's already work to move it to 13.0.

I suspect you are running with an old version of PostgREST version locally. Could you try rm supabase/.temp/rest-version before running supabase start again?

Yes, I figured that out a few minutes ago. I though updating Supabase CLI and removing all containers should use the right versions, but I guess that's not the case. Maybe add a warning on the CLI if the versions stored in .temp do not match the ones that the CLI should be using?

Thanks

[sweatybridge]

Maybe add a warning on the CLI if the versions stored in .temp do not match the ones that the CLI should be using?

Well, the purpose of temp version is to sync up your local versions to match your remote project. So they are actually expected to be different from cli defaults after running supabase link command.

What you can do is to update your remote project (by restarting) so it's running the latest version of postgrest.

[empz]

Got it, thanks!

…

On Mon, May 12, 2025 at 6:28 PM Han Qiao ***@***.***> wrote: *sweatybridge* left a comment (supabase/cli#3550) <#3550 (comment)> Maybe add a warning on the CLI if the versions stored in .temp do not match the ones that the CLI should be using? Well, the purpose of temp version is to sync up your local versions to match your remote project. So they are actually expected to be different from cli defaults after running supabase link command. What you can do is to update your remote project (by restarting) so it's running the latest version of postgrest. — Reply to this email directly, view it on GitHub <#3550 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADEWSI35EUANXZ2WIISTBL26DD35AVCNFSM6AAAAAB4ZNOTY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZTGIZDKNZSGI> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>