rhuynh
rhuynh
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
Looks like it's all working now. Thanks Greg. Just had to change to Nixpacks and redploy 🙌
25 replies
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
Ah I see, that would make sense. Sure let me try that and if it still doesn't work I'll start a new help thread. Thanks Greg 🙏
25 replies
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
Service id for the server is 45bdfe3c-df2c-4cc2-aff6-806004775564
25 replies
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
Hmm strange... I tried redploying and in the server logs I get this now
Segmentation fault (core dumped)

error Command failed with exit code 139.
Segmentation fault (core dumped)

error Command failed with exit code 139.
No other db errors showing int he logs. However when I try my local server on my machine and connecting to the postgres db on railway it seems to work just fine. Could it be an issue with server connection on railway?
25 replies
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
Invalid `prisma.user.findFirst()` invocation:

Can't reach database server at `monorail.proxy.rlwy.net`:`15279`

Please make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.

err: {

"type": "PrismaClientInitializationError",

"message": "\nInvalid `prisma.user.findFirst()` invocation:\n\n\n Can't reach database server at `monorail.proxy.rlwy.net`:`15279`\n\nPlease make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.",

"stack":

Error:

Invalid `prisma.user.findFirst()` invocation:





Can't reach database server at `monorail.proxy.rlwy.net`:`15279`



Please make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.

at Object.request (/workspace/node_modules/@prisma/client/runtime/index.js:45411:15)

at async PrismaClient._request (/workspace/node_modules/@prisma/client/runtime/index.js:46301:18)

"clientVersion": "3.14.0"

}

Segmentation fault (core dumped)

error Command failed with exit code 139.
Invalid `prisma.user.findFirst()` invocation:

Can't reach database server at `monorail.proxy.rlwy.net`:`15279`

Please make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.

err: {

"type": "PrismaClientInitializationError",

"message": "\nInvalid `prisma.user.findFirst()` invocation:\n\n\n Can't reach database server at `monorail.proxy.rlwy.net`:`15279`\n\nPlease make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.",

"stack":

Error:

Invalid `prisma.user.findFirst()` invocation:





Can't reach database server at `monorail.proxy.rlwy.net`:`15279`



Please make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.

at Object.request (/workspace/node_modules/@prisma/client/runtime/index.js:45411:15)

at async PrismaClient._request (/workspace/node_modules/@prisma/client/runtime/index.js:46301:18)

"clientVersion": "3.14.0"

}

Segmentation fault (core dumped)

error Command failed with exit code 139.
25 replies
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
Here's the logs
25 replies
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
Yes I'm still having issues. My server is unable to connect to the database. I've set the environment variable for my server for the database as ${{Postgres.Database_URL}}
25 replies
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
Yes still having issues. It's giving me a different error now then before but essentially my prisma client can't seem to connect to the postgres database. I set the environment variables for my server as as ${{Postgres.DATABASE_URL}}
[19:45:54.237] ERROR (35):

Invalid `prisma.user.findFirst()` invocation:

Can't reach database server at `monorail.proxy.rlwy.net`:`15279`

Please make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.

err: {

"type": "PrismaClientInitializationError",

"message": "\nInvalid `prisma.user.findFirst()` invocation:\n\n\n Can't reach database server at `monorail.proxy.rlwy.net`:`15279`\n\nPlease make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.",

"stack":

Error:

Invalid `prisma.user.findFirst()` invocation:





Can't reach database server at `monorail.proxy.rlwy.net`:`15279`



Please make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.

at Object.request (/workspace/node_modules/@prisma/client/runtime/index.js:45411:15)

at async PrismaClient._request (/workspace/node_modules/@prisma/client/runtime/index.js:46301:18)

"clientVersion": "3.14.0"

}
[19:45:54.237] ERROR (35):

Invalid `prisma.user.findFirst()` invocation:

Can't reach database server at `monorail.proxy.rlwy.net`:`15279`

Please make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.

err: {

"type": "PrismaClientInitializationError",

"message": "\nInvalid `prisma.user.findFirst()` invocation:\n\n\n Can't reach database server at `monorail.proxy.rlwy.net`:`15279`\n\nPlease make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.",

"stack":

Error:

Invalid `prisma.user.findFirst()` invocation:





Can't reach database server at `monorail.proxy.rlwy.net`:`15279`



Please make sure your database server is running at `monorail.proxy.rlwy.net`:`15279`.

at Object.request (/workspace/node_modules/@prisma/client/runtime/index.js:45411:15)

at async PrismaClient._request (/workspace/node_modules/@prisma/client/runtime/index.js:46301:18)

"clientVersion": "3.14.0"

}
25 replies
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
@Brody any updates on this?
25 replies
RRailway
Created by rhuynh on 11/29/2023 in #✋|help
Postgres Migration Connection Issue
Yeah my log trace is the same as @Raigato
25 replies