#after migrating to v2 db, server fails to start

27 messages · Page 1 of 1 (latest)

frozen basinBOT
#

Project ID: fc19d5fd-89b2-4873-ab73-2e5289f4f140

wary dawnBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

sturdy spoke
#

fc19d5fd-89b2-4873-ab73-2e5289f4f140

uncut delta
#

i see hello world?

sturdy spoke
#

i just added the timeout to the env variable

#

found in another answer

uncut delta
#

awsome!

sturdy spoke
#

hmm

#

but i'm still getting cors errors

#

and a 503 error POST https://saasathon-production.up.railway.app/operations/get-projects net::ERR_FAILED 503 (Service Unavailable)

#

and it's crashed again

uncut delta
#

any errors in the servers logs?

sturdy spoke
#

i can't see logs as its crashed

uncut delta
#

why would that prevent you from opeing the deploy logs?

sturdy spoke
#

i don't see an option for opening the deployment logs in the UI

#

is there a way to do that from the CLI?

uncut delta
#

open the logs via the ui please

#

open the deployment, and click on deploy logs

sturdy spoke
#

i restarted the server and then the deploy logs become avaialale.

#

they're open Server listening on port 6093

#

when the client trys to access the server, it restarts

uncut delta
#

are there errors in the logs?

sturdy spoke
# 
Server listening on port 6093

> [email protected] start-production

> npm run db-migrate-prod && NODE_ENV=production npm run start

> [email protected] db-migrate-prod

> prisma migrate deploy --schema=../db/schema.prisma
sturdy spoke
uncut delta
#

not much to debug without errors, please add verbose logging to your app so we can pinpoint the cause of the crash