Railway•14mo ago

Database becomes constantly unreachable or times out due to pg adivisory lock

I'm using prisma, and before starting the application, I run the prisma migrations. It periodically crashes when I do a new deploy. The workaround seems to be redeploy the database service. Am I doing something wrong here?

2 Replies

Percy•14mo ago

Project ID: ab0d96a2-9d19-48de-a430-8e750636e3b8

Ryan The TempOP•14mo ago

ab0d96a2-9d19-48de-a430-8e750636e3b8 It gets stuck in a loop here, until it crashes:

Error: P1002

The database server at `viaduct.proxy.rlwy.net`:`58398` was reached but timed out.

Please try again.

Please make sure your database server is running at `viaduct.proxy.rlwy.net`:`58398`.

Context: Timed out trying to acquire a postgres advisory lock (SELECT pg_advisory_lock(727073

Error: P1002

The database server at `viaduct.proxy.rlwy.net`:`58398` was reached but timed out.

Please try again.

Please make sure your database server is running at `viaduct.proxy.rlwy.net`:`58398`.

Context: Timed out trying to acquire a postgres advisory lock (SELECT pg_advisory_lock(727073

Gaming

Programming

Database becomes constantly unreachable or times out due to pg adivisory lock