timvisee / timvisee/send-docker-compose

Upload Hangs at 92% and Results in "ENOENT" Error

Open
#12 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
170
Forks
21
PR merge metrics
No merged PRs in 30d

Description

Setup

  • Docker image: registry.gitlab.com/timvisee/send:latest
  • Environment: Docker on Ubuntu 22.04.3 LTS

Describe the bug

Hey everyone,

I'm encountering an issue while using the Send Docker Container with the following details:

Problem:

When attempting to upload a file, the process hangs at 92%, and after approximately 2 minutes, an error message is displayed in the web browser.

Steps To Reproduce
  1. Start the Send Docker Container.
  2. Attempt to upload a file using the web interface.
  3. Observe the upload process hanging at 92% (Screenshot 1).
  4. After about 2 minutes, an error message is displayed in the web browser (Screenshot 2).
Screenshots of the Web-interface

Screenshot 1: Screenshot
Screenshot 2: Screenshot

Expected Behavior

I expected the file upload process to complete successfully without any hanging or errors.

Logs

2023-08-17T09:13:49.971023955Z [ 'https://send.example.com', 'wss://send.example.com' ]
2023-08-17T09:13:50.004664598Z | Timestamp=1692263630004000000 Logger=FirefoxSend Type=uncaughtException Severity=0 Pid=1 EnvVersion=2.0 Fields={"error":"Error: ENOENT: no such file or directory, unlink '/uploads/1-8da133c379fb97d3'","stack":"\n at Object.unlinkSync (node:fs:1718:3)\n at WriteStream. (/app/server/storage/fs.js:34:12)\n at WriteStream.emit (node:events:402:35)\n at WriteStream.emit (node:domain:475:12)\n at emitErrorNT (node:internal/streams/destroy:157:8)\n at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n at processTicksAndRejections (node:internal/process/task_queues:83:21)"}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the upload with the Docker image on Ubuntu 22.04.3, then inspect /app/server/storage/fs.js around the WriteStream handler and its unlink call. Use the provided ENOENT log and the 92% progress point to trace the failure; done means uploads complete without the missing-file error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, node.js
Domain
backend, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.