RocketChat / RocketChat/Rocket.Chat
Error: ENOENT: no such file or directory
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
After updating to 6.2.8, an error appears in the log every 2 minutes
Error: ENOENT: no such file or directory, stat '/tmp/zipFiles/87e62a59-9fc8-452e-9f97-2ea84821861b.zip'
=> awaited here:
at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)
at server/lib/dataExport/uploadZipFile.ts:11:16
at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40
=> awaited here:
at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)
at server/lib/dataExport/processDataDownloads.ts:226:25
at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40 {
errno: -2,
code: 'ENOENT',
syscall: 'stat',
path: '/tmp/zipFiles/87e62a59-9fc8-452e-9f97-2ea84821861b.zip'
}
Server Setup Information
Version of Rocket.Chat Server: 6.2.9
Operating System: synology
Deployment Method: docker
Number of Running Instances: 1
DB Replicaset Oplog: Enabled
NodeJS Version: 14.21.3
MongoDB Version: 6.0.7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with server/lib/dataExport/uploadZipFile.ts and the caller in server/lib/dataExport/processDataDownloads.ts, then trace why the referenced file under /tmp/zipFiles is missing when stat runs. Reproduce the recurring data-download error in the reported Docker setup and confirm that missing ZIP files no longer produce an unhandled ENOENT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100