Vincent
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
So I think my issue here was that prisma didn't warn when the SSL version was misconfigured at all.
But I'll be able to verify if fixing the binaryTarget is the sole solution to my issue
14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
So then I found this in the docs:
https://www.prisma.io/docs/orm/reference/prisma-schema-reference#binarytargets-options
Which definitely was misconfigured in my schema.
14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
@Nurul (Prisma) after further diagnosis of this issue, I am fairly certain this has something to do with SSL. Although libraryStarted is true for me, I don’t see the logs I would expect to see, and just as the user describes in this issue I am experiencing a completely silent and hung transaction. The process emits no logs from the point after the Prisma promise object is awaited from the transaction.
https://github.com/prisma/prisma/issues/15678
this leads me to believe there existed kind of incompatibility between Prisma, OpenSSL and the version of Alpine I was using.
14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
Here is a spreadsheet with the logs broken up by prisma operation into separate sheets if it helps. I don't see anything obviously wrong in the logs at a glance (except for that timestamp perhaps?). I had to obfuscated some of the operations, but that's the full dump otherwise.
https://docs.google.com/spreadsheets/d/1W-DkbxLKtitGTEw8UMuescXt1IeuokkvrwFIZD82lpk/edit?usp=sharing
14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
@Nurul are all logs printed by prisma to stderr when in debug mode indicative of a problem?
I see prisma printing to stderr when I test with DEBUG set, but don't see any hints as to what is actually wrong in the logs. There are over 50k lines of logs to go through when the issue occurs, so I am wondering if I can assume the stderr messages are telling us those queries are failing or not.
The very first stderr message that prisma printed was this:
Which looks like the very first call it made took 18 minutes?
14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
Another thing I forgot to mention above. This issue was not reproducible locally on macOS in a dev environment. We only saw prisma exhibit this behavior when running on linux in a docker container. Regardless, I will heed your advice and see what happens.
14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
I will configure
DEBUG="prisma*" for additional logging and see what I learn. That's a great idea, and the team may have already tried this, but regardless I will give it another shot, as we use this for debugging all the time.14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
I would share the entire project if it wasn't closed source, I can share more details of the technical stack and what not if you are curious.
14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
Everything is fine and dandy for many months on 6.0.1 with this in place, it's only the newer versions that I can't use, which is unfortunate, as 6.1.0 fixes so many tracing related bugs (basically all of them).
14 replies
PPrisma
•Created by Vincent on 2/12/2025 in #help-and-questions
Silent and Stalled transaction
@Nurul apologies no, that was just a typo as I copy pasted it, its been fixed 👍
14 replies