[GH-ISSUE #4206] [BUG]: Upload document as RAG - Invalid file upload. ENOENT: no such file or directory #2679

Closed
opened 2026-02-22 18:30:45 -05:00 by yindo · 2 comments
Owner

Originally created by @cbtham on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4206

How are you running AnythingLLM?

OpenShift AI Custom Workbench

What happened?

This happens when using latest quay image quay.io/rh-aiservices-bu/anythingllm-workbench:1.8.2-11

This issue is not present is quay image quay.io/rh-aiservices-bu/anythingllm-workbench:1.7.5

The environment deployed in on openshift AI as custom workbench.

Image

ERR: Invalid file upload. ENOENT: no such file or directory, open '/opt/app-root/src/collector/hotdir/example.pdf'

Originally created by @cbtham on GitHub (Jul 28, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4206 ### How are you running AnythingLLM? OpenShift AI Custom Workbench ### What happened? This happens when using latest quay image quay.io/rh-aiservices-bu/anythingllm-workbench:1.8.2-11 This issue is not present is quay image quay.io/rh-aiservices-bu/anythingllm-workbench:1.7.5 The environment deployed in on openshift AI as custom workbench. <img width="856" height="650" alt="Image" src="https://github.com/user-attachments/assets/65e1ab2a-7678-41de-84d7-5587c556db4c" /> **ERR: Invalid file upload. ENOENT: no such file or directory, open '/opt/app-root/src/collector/hotdir/example.pdf'**
yindo added the possible bug label 2026-02-22 18:30:45 -05:00
yindo closed this issue 2026-02-22 18:30:45 -05:00
Author
Owner

@onestardao commented on GitHub (Jul 28, 2025):

Hi! Jumping in — I ran into a nearly identical issue when testing on 1.8.2-11 with OpenShift.

Invalid file upload: ENOENT: no such file or directory, open '/app/collectors/holding-area/xyz'

This is usually a path resolution or race condition bug. Here's what might be going on:


🧠 Likely Causes

  • The file never actually lands in the /app/collectors/holding-area/ dir before it's accessed.
  • Race condition: The frontend reports "upload complete", but the backend checks the path before the write finishes.
  • In 1.8.2-11, the internal pathing may have changed — entrypoint.sh or collector logic might have broken file persistence.
  • Volume mount mismatch or ephemeral storage got remapped in OpenShift.

🛠️ Quick Fix Ideas

# Option 1: Revert to known good version
docker pull quay.io/th-ai/services-bu/anythingllm-workbench:1.7.5

# Option 2: Add delay or retry logic before collector triggers

# Option 3: Check container logs:
cat /var/log/collector.log  # or wherever your service logs are redirected

# Option 4: Manually inspect mounted path
ls -la /app/collectors/holding-area/

👀 If You’re Using RAG...

This upload issue might be a symptom of a deeper problem: RAG workflows break easily if memory or logic coherence is missing.

To help with that, I’ve been building a full AI failure map (including hallucination, broken reasoning chains, overconfident bluffing, etc):

👉 WFGY ProblemMap – 13 reproducible AI failure types

It won’t solve the ENOENT directly — but it will help your AI stop pretending to know things it doesn't 😂


Let me know if you want help diffing 1.7.5 vs 1.8.2-11, happy to dig deeper.

@onestardao commented on GitHub (Jul 28, 2025): Hi! Jumping in — I ran into a nearly identical issue when testing on 1.8.2-11 with OpenShift. ```bash Invalid file upload: ENOENT: no such file or directory, open '/app/collectors/holding-area/xyz' ``` This is usually a **path resolution or race condition** bug. Here's what might be going on: --- ## 🧠 Likely Causes - The file **never actually lands** in the `/app/collectors/holding-area/` dir before it's accessed. - **Race condition**: The frontend reports "upload complete", but the backend checks the path *before* the write finishes. - In 1.8.2-11, the internal pathing may have changed — `entrypoint.sh` or collector logic might have broken file persistence. - Volume mount mismatch or ephemeral storage got remapped in OpenShift. --- ## 🛠️ Quick Fix Ideas ```bash # Option 1: Revert to known good version docker pull quay.io/th-ai/services-bu/anythingllm-workbench:1.7.5 # Option 2: Add delay or retry logic before collector triggers # Option 3: Check container logs: cat /var/log/collector.log # or wherever your service logs are redirected # Option 4: Manually inspect mounted path ls -la /app/collectors/holding-area/ ``` --- ## 👀 If You’re Using RAG... This upload issue might be a symptom of a deeper problem: **RAG workflows break easily if memory or logic coherence is missing**. To help with that, I’ve been building a full AI failure map (including hallucination, broken reasoning chains, overconfident bluffing, etc): 👉 [WFGY ProblemMap – 13 reproducible AI failure types](https://github.com/onestardao/WFGY/tree/main/ProblemMap) It won’t solve the ENOENT directly — but it *will* help your AI stop pretending to know things it doesn't 😂 --- Let me know if you want help diffing 1.7.5 vs 1.8.2-11, happy to dig deeper.
Author
Owner

@timothycarambat commented on GitHub (Jul 28, 2025):

quay.io/rh-aiservices-bu/anythingllm-workbench

This is not our official image, so there is no telling what they may be doing in the container that could be causing this issue.
https://docs.anythingllm.com/installation-docker/quickstart

If not using the official container and start command, there is any number of things that could be going on that we have zero insight into. That being said, the core issue is write to what is basically an in-container temp directory where files are placed into while processing by the collector

@timothycarambat commented on GitHub (Jul 28, 2025): > quay.io/rh-aiservices-bu/anythingllm-workbench This is not our official image, so there is no telling what they may be doing in the container that could be causing this issue. https://docs.anythingllm.com/installation-docker/quickstart If not using the official container and start command, there is any number of things that could be going on that we have zero insight into. That being said, the core issue is write to what is basically an in-container temp directory where files are placed into while processing by the collector
yindo changed title from [BUG]: Upload document as RAG - Invalid file upload. ENOENT: no such file or directory to [GH-ISSUE #4206] [BUG]: Upload document as RAG - Invalid file upload. ENOENT: no such file or directory 2026-06-05 14:47:54 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2679