PANIC: timer has gone away

[Joao-Neto-DH]

Hi Prisma Team! My Prisma Client just crashed. I was try to migrate my nodejs app to cpanel and error happend. This is the report:

Versions

+Name++++++++++++	+Version++++++++++++
+Node++++++++++++	+v18.20.2+++++++++++
+OS++++++++++++++	+debian-openssl-1.0.x
+Prisma+Client+++	+5.13.0+++++++++++++
+Query+Engine++++	+b9a39a7ee606c28e3455d0fd60e78c3ba82b1a2b
+Database++++++++	+mysql++++++++++++++

Logs

prisma:tryLoadEnv+Environment+variables+not+found+at+null
prisma:tryLoadEnv+Environment+variables+loaded+from+/home/dunorteo/back.dunorte.online/.env
prisma:client+checkPlatformCaching:postinstall+false
prisma:client+checkPlatformCaching:ciName+
prisma:tryLoadEnv+Environment+variables+not+found+at+null
prisma:tryLoadEnv+Environment+variables+loaded+from+/home/dunorteo/back.dunorte.online/.env
prisma:client+dirname+/home/dunorteo/nodevenv/back.dunorte.online/18/lib/node_modules/.prisma/client
prisma:client+relativePath+../../../../../../../back.dunorte.online/prisma
prisma:client+cwd+/home/dunorteo/back.dunorte.online/prisma
prisma:client+clientVersion+5.13.0
prisma:client:libraryEngine+internalSetup
prisma:get-platform+Don't+know+any+platform-specific+paths+for+"undefined"+on+x64+(x86_64)
prisma:get-platform+Falling+back+to+"ldconfig"+and+other+generic+paths
prisma:get-platform+Command+"ldconfig+-p+|+sed+"s/.=>s//"+|+sed+"s|.*/||"+|+grep+libssl+|+sort+|+grep+-v+"libssl.so.0""+successfully+returned+"libssl3.so
libssl.so
libssl.so.10
libssl.so.1.1
"
prisma:get-platform+Found+libssl.so+file+using+"ldconfig"+or+other+generic+paths:+libssl3.so
libssl.so
libssl.so.10
libssl.so.1.1

prisma:get-platform+The+parsed+libssl+version+is:+1.0.x
prisma:get-platform+Distro+is+"undefined".+Falling+back+to+Prisma+engines+built+for+"debian".
prisma:client:engines:resolveEnginePath+enginePath+/home/dunorteo/nodevenv/back.dunorte.online/18/lib/node_modules/.prisma/client/libquery_engine-debian-openssl-1.0.x.so.node
prisma:client:libraryEngine+sending+request,+this.libraryStarted:+false
prisma:client:libraryEngine+library+starting

[Druue]

Hey @Joao-Neto-DH,

Could you explain more about what you were doing and what your setup is? I'm not aware of what cpanel is either, it seems like a hosting provider? Is this only happening with them? or also locally.

Thanks!

[aqrln]

Sorry for the misclick, will write a comment below.

[aqrln]

PANIC: timer has gone away can happen if the system ran out of the limit of processes/threads (which are pretty much the same thing from the point of view of Linux). From what I can infer from https://support.cpanel.net/hc/en-us/articles/1500004501082-How-to-modify-Ulimit-values, it's not unusual for cpanel to have limits which are geared towards a very different kind of web applications and are unrealistically low for higher performance multi-threaded applications like Node.js with Prisma. Just starting Node.js by itself already "eats" 15 processes from the limit (checked just now with Node.js v22 on Linux by running the repl with the node command). Prisma Query Engine then also spawns a similar number of threads.

I suggest you check if it is indeed the cause of this error happening to you (if you have access to the shell, you can run ulimit -u), and raise a support ticket with your hosting provider to raise the limit for you if it's less than maybe 40–50 or so.