Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5091] [BUG]: Desktop (Windows): ENOENT rename failure when used with Calibre AI Metadata plugin (document path duplicated) #4911

New Issue
Closed
opened 2026-06-05 14:50:49 -04:00 by yindo · 1 comment
yindo commented 2026-06-05 14:50:49 -04:00
Owner
Copy Link
Copy Source

Originally created by @ninerays on GitHub (Feb 28, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5091

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

When using AnythingLLM Desktop on Windows11 together with the Digital Assassins "AI Metadata" plugin for Calibre, document processing fails with an ENOENT error when the backend tries to rename the processed JSON into the workspace folder.

The backend is running and reachable on http://127.0.0.1:3001, and Ollama is running on http://127.0.0.1:11434. A thread is created in the target workspace for each book, but Calibre reports "Failed to download metadata" and AnythingLLM logs an ENOENT during the rename.

The error path includes a duplicated C:\Users\... prefix, which suggests a Windows path handling bug.

Environment

  • AnythingLLM Desktop on Windows 11

  • Backend logs show:

    • AnythingLLM Standalone Backend listening on port 3001
    • AnythingLLM Standalone Document processor listening on port 8888
    • LLM provider: anythingllm_ollama (Ollama on port 11434, model qwen3-vl:4b-instruct)

  • Calibre 9.4 (Windows)

  • Digital Assassins "AI Metadata" plugin configured with:

    • AnythingLLM URL: http://127.0.0.1:3001
    • Valid API key from Developer API
    • Workspace name: Calibre (exists in AnythingLLM)

Are there known steps to reproduce?

Yes, the issue is reproducible with these steps:

  1. Start AnythingLLM Desktop from PowerShell so backend logs are visible:

    & "$env:LOCALAPPDATA\Programs\AnythingLLM\AnythingLLM.exe"

In the PowerShell log, confirm lines like:

AnythingLLM Standalone Backend listening on port 3001

AnythingLLM Standalone Document processor listening on port 8888

Ensure Ollama is running locally and configured as the LLM provider in AnythingLLM:

Ollama API: http://127.0.0.1:11434

Example model: qwen3-vl:4b-instruct

In Calibre (9.4 on Windows), install the Digital Assassins “AI Metadata” plugin bundle and configure the AI Metadata plugin with:

AnythingLLM URL: http://127.0.0.1:3001

API key: from AnythingLLM → Settings → Developer API

Workspace name: Calibre (existing workspace)

In Calibre, filter for a book with an empty Comments field, select a single DRM‑free EPUB, and click the AI Metadata toolbar button (the helper, not “Download metadata” directly).

Observe that:

A new thread is created in the Calibre workspace with the book title.

The backend log shows successful conversion:

text
[collector] info: -- Success Secrets of Disruptors - Antony Abell.epub --
[collector] info: [SUCCESS]: Success Secrets of Disruptors - Antony Abell.epub converted & ready for embedding.
Then an error like:

text
[backend] error: ENOENT: no such file or directory, rename
'C:\Users...\storage\documents\C:\Users...\storage\documents\custom-documents\Success-Secrets-of-Disruptors-Antony-Abell.epub-...json'
->
'C:\Users...\storage\documents\Calibre\Success-Secrets-of-Disruptors-Antony-Abell.epub-...json'
Calibre reports: “Failed to download metadata or cover for the selected book.”

text
undefined
I want one block that contains all of that so I can copy & paste it as a whole block, not sure why you are breaking it up
text
Yes, the issue is reproducible with these steps:

  1. Start AnythingLLM Desktop from PowerShell so backend logs are visible:

    & "$env:LOCALAPPDATA\Programs\AnythingLLM\AnythingLLM.exe"

In the PowerShell log, confirm lines like:

AnythingLLM Standalone Backend listening on port 3001

AnythingLLM Standalone Document processor listening on port 8888

Ensure Ollama is running locally and configured as the LLM provider in AnythingLLM:

Ollama API: http://127.0.0.1:11434

Example model: qwen3-vl:4b-instruct

In Calibre (9.4 on Windows), install the Digital Assassins “AI Metadata” plugin bundle and configure the AI Metadata plugin with:

AnythingLLM URL: http://127.0.0.1:3001

API key: from AnythingLLM → Settings → Developer API

Workspace name: Calibre (existing workspace)

In Calibre, filter for a book with an empty Comments field, select a single DRM‑free EPUB, and click the AI Metadata toolbar button (the helper, not “Download metadata” directly).

Observe that:

A new thread is created in the Calibre workspace with the book title.

The backend log shows successful conversion:

text
[collector] info: -- Success Secrets of Disruptors - Antony Abell.epub --
[collector] info: [TikTokenTokenizer] Input will take too long to encode - estimating
[collector] info: [SUCCESS]: Success Secrets of Disruptors - Antony Abell.epub converted & ready for embedding.
Then an error like:

text
[backend] error: ENOENT: no such file or directory, rename
'C:\Users...\AppData\Roaming\anythingllm-desktop\storage\documents\C:\Users...\AppData\Roaming\anythingllm-desktop\storage\documents\custom-documents\Success-Secrets-of-Disruptors-Antony-Abell.epub-...json'
->
'C:\Users...\AppData\Roaming\anythingllm-desktop\storage\documents\Calibre\Success-Secrets-of-Disruptors-Antony-Abell.epub-...json'
Note the duplicated absolute path prefix in the source path.

Calibre reports: “Failed to download metadata or cover for the selected book.”

text
undefined

Originally created by @ninerays on GitHub (Feb 28, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5091 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? When using AnythingLLM Desktop on Windows11 together with the Digital Assassins "AI Metadata" plugin for Calibre, document processing fails with an ENOENT error when the backend tries to `rename` the processed JSON into the workspace folder. The backend is running and reachable on `http://127.0.0.1:3001`, and Ollama is running on `http://127.0.0.1:11434`. A thread is created in the target workspace for each book, but Calibre reports "Failed to download metadata" and AnythingLLM logs an ENOENT during the rename. The error path includes a duplicated `C:\Users\...` prefix, which suggests a Windows path handling bug. **Environment** - AnythingLLM **Desktop** on Windows 11 - Backend logs show: - `AnythingLLM Standalone Backend listening on port 3001` - `AnythingLLM Standalone Document processor listening on port 8888` - LLM provider: `anythingllm_ollama` (Ollama on port 11434, model `qwen3-vl:4b-instruct`) - Calibre 9.4 (Windows) - Digital Assassins "AI Metadata" plugin configured with: - AnythingLLM URL: `http://127.0.0.1:3001` - Valid API key from Developer API - Workspace name: `Calibre` (exists in AnythingLLM) ### Are there known steps to reproduce? Yes, the issue is reproducible with these steps: 1. Start AnythingLLM Desktop from PowerShell so backend logs are visible: ```powershell & "$env:LOCALAPPDATA\Programs\AnythingLLM\AnythingLLM.exe" In the PowerShell log, confirm lines like: AnythingLLM Standalone Backend listening on port 3001 AnythingLLM Standalone Document processor listening on port 8888 Ensure Ollama is running locally and configured as the LLM provider in AnythingLLM: Ollama API: http://127.0.0.1:11434 Example model: qwen3-vl:4b-instruct In Calibre (9.4 on Windows), install the Digital Assassins “AI Metadata” plugin bundle and configure the AI Metadata plugin with: AnythingLLM URL: http://127.0.0.1:3001 API key: from AnythingLLM → Settings → Developer API Workspace name: Calibre (existing workspace) In Calibre, filter for a book with an empty Comments field, select a single DRM‑free EPUB, and click the AI Metadata toolbar button (the helper, not “Download metadata” directly). Observe that: A new thread is created in the Calibre workspace with the book title. The backend log shows successful conversion: text [collector] info: -- Success Secrets of Disruptors - Antony Abell.epub -- [collector] info: [SUCCESS]: Success Secrets of Disruptors - Antony Abell.epub converted & ready for embedding. Then an error like: text [backend] error: ENOENT: no such file or directory, rename 'C:\Users\...\storage\documents\C:\Users\...\storage\documents\custom-documents\Success-Secrets-of-Disruptors-Antony-Abell.epub-...json' -> 'C:\Users\...\storage\documents\Calibre\Success-Secrets-of-Disruptors-Antony-Abell.epub-...json' Calibre reports: “Failed to download metadata or cover for the selected book.” text undefined I want one block that contains all of that so I can copy & paste it as a whole block, not sure why you are breaking it up text Yes, the issue is reproducible with these steps: 1. Start AnythingLLM Desktop from PowerShell so backend logs are visible: ```powershell & "$env:LOCALAPPDATA\Programs\AnythingLLM\AnythingLLM.exe" In the PowerShell log, confirm lines like: AnythingLLM Standalone Backend listening on port 3001 AnythingLLM Standalone Document processor listening on port 8888 Ensure Ollama is running locally and configured as the LLM provider in AnythingLLM: Ollama API: http://127.0.0.1:11434 Example model: qwen3-vl:4b-instruct In Calibre (9.4 on Windows), install the Digital Assassins “AI Metadata” plugin bundle and configure the AI Metadata plugin with: AnythingLLM URL: http://127.0.0.1:3001 API key: from AnythingLLM → Settings → Developer API Workspace name: Calibre (existing workspace) In Calibre, filter for a book with an empty Comments field, select a single DRM‑free EPUB, and click the AI Metadata toolbar button (the helper, not “Download metadata” directly). Observe that: A new thread is created in the Calibre workspace with the book title. The backend log shows successful conversion: text [collector] info: -- Success Secrets of Disruptors - Antony Abell.epub -- [collector] info: [TikTokenTokenizer] Input will take too long to encode - estimating [collector] info: [SUCCESS]: Success Secrets of Disruptors - Antony Abell.epub converted & ready for embedding. Then an error like: text [backend] error: ENOENT: no such file or directory, rename 'C:\Users\...\AppData\Roaming\anythingllm-desktop\storage\documents\C:\Users\...\AppData\Roaming\anythingllm-desktop\storage\documents\custom-documents\Success-Secrets-of-Disruptors-Antony-Abell.epub-...json' -> 'C:\Users\...\AppData\Roaming\anythingllm-desktop\storage\documents\Calibre\Success-Secrets-of-Disruptors-Antony-Abell.epub-...json' Note the duplicated absolute path prefix in the source path. Calibre reports: “Failed to download metadata or cover for the selected book.” text undefined
yindo added the possible bug label 2026-06-05 14:50:49 -04:00
yindo closed this issue 2026-06-05 14:50:49 -04:00
yindo commented 2026-06-05 14:50:49 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Mar 2, 2026):

This certainly seems like a bug to file with the custom extension creator as it seems like an issue with how they are using the backend API for uploading/embedding files into a workspace

<!-- gh-comment-id:3985207696 --> @timothycarambat commented on GitHub (Mar 2, 2026): This certainly seems like a bug to file with the custom extension creator as it seems like an issue with how they are using the backend API for uploading/embedding files into a workspace
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#4911
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?