umami keeps dying because /tmp/prisma-*.sock could not be found
See original GitHub issueI keep getting this error from time to time, which forces me to restart umami to make the dashboard work again:
2020-12-10 14:38:23,082 DEBG 'umami' stderr output:
PrismaClientKnownRequestError2: connect ENOENT /tmp/prisma-395d4bbf364fd00bc58da2d3.sock
at PrismaClientFetcher.request (/home/simbo/umami/node_modules/@prisma/client/runtime/index.js:79355:15)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async getSession (/home/simbo/umami/.next/server/pages/api/auth/verify.js:198:19)
at async /home/simbo/umami/.next/server/pages/api/auth/verify.js:258:15 {
code: 'ENOENT',
clientVersion: '2.12.1',
meta: undefined
}
2020-12-10 14:38:30,493 DEBG 'umami' stderr output:
PrismaClientKnownRequestError2: connect ENOENT /tmp/prisma-395d4bbf364fd00bc58da2d3.sock
at PrismaClientFetcher.request (/home/simbo/umami/node_modules/@prisma/client/runtime/index.js:79355:15)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async module.exports.fJFN.__webpack_exports__.default (/home/simbo/umami/.next/server/pages/api/websites.js:1064:22)
at async apiResolver (/home/simbo/umami/node_modules/next/dist/next-server/server/api-utils.js:8:1)
at async Server.handleApiRequest (/home/simbo/umami/node_modules/next/dist/next-server/server/next-server.js:63:403)
at async Object.fn (/home/simbo/umami/node_modules/next/dist/next-server/server/next-server.js:55:530)
at async Router.execute (/home/simbo/umami/node_modules/next/dist/next-server/server/router.js:24:67)
at async Server.run (/home/simbo/umami/node_modules/next/dist/next-server/server/next-server.js:65:1023)
at async Server.handleRequest (/home/simbo/umami/node_modules/next/dist/next-server/server/next-server.js:33:450) {
code: 'ENOENT',
clientVersion: '2.12.1',
meta: undefined
}
Not sure if if this is an issue with my server or with umami… I am using umami 1.9.0 at the moment.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8
Top Results From Across the Web
umami keeps dying because /tmp/prisma-*.sock could not be ...
I am hosting umami on a shared hosting service (uberspace) and yes, the /tmp folder seems to get cleared from time to time....
Read more >Untitled
Did not read lightsaber, Salt lake city map ski resorts, Travis scott uptown ... Reinsdyrjakt periode, Mep postrelmov email, Find obituaries from 1995, ......
Read more >Untitled
A familia castelo de madeira baixar, Gvt training biceps, 1 800 missing tv ... Nyfab montage, Project areas could not be fetched, Bone...
Read more >Untitled
22 tsw donington wheels, Rd4512, There will come soft rain book, ... Lp client-error-not-found, Hemid herisci, World's nicest houses pictures, ...
Read more >Untitled
Lewis ward footballer, Mrs bennet letters to alice, Union type found in bookies, Fossil am 4163. Reviews on 8 hour diet, Hemp garden...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have created a fork of umami: https://github.com/simbo/umami Which includes a temporary fix using the dev channel of prisma as suggested here: https://github.com/prisma/prisma/discussions/4706#discussioncomment-222019
I am hosting umami on a shared hosting service (uberspace) and yes, the
/tmp
folder seems to get cleared from time to time.I started a discussion at the prisma project: https://github.com/prisma/prisma/discussions/4706