starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

paperless-gpt update issue -- how to redeploy? #716

New Issue
Closed
opened 2026-02-04 21:03:59 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-04 21:03:59 +03:00
Owner
Copy Link

Originally created by @habitoti on GitHub (Mar 30, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

paperless-gpt

📂 What was the exact command used to execute the script?

update (i.e. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/paperless-gpt.sh)")

📝 Provide a clear and concise description of the issue.

I wanted to update my paperless-gpt LXC, and it started just fine, but then ended in an error. Unfortunately -- as I instantly continued to look for logs or any other clue -- I missed to exactly note down the error text in the console, and now it's seemingly gone. It was sth. around permission issues for the mv-command. As a consequence, the app folder in /opt is now gone, preventing me from simply redoing it (was hoping to just redeploy that way...).
So my questions are:

  • Where would I find logs that explain what happened (or at least show that error again)?
  • Is there any (reasonably simple) way to redeploy within that container, even w/o the app folder existing at this point? Or am I left with killing that LXC and starting from scratch? However, I want then at least to avoid running into that same issue next time I need to update this (or any other) container.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

🔄 Steps to reproduce the issue.

Type "update" in paperless-LXC shell /opt/paperless-gpt folder

❌ Paste the full error output (if available).

Unfortunately gone

🖼️ Additional context (optional).

No response

Originally created by @habitoti on GitHub (Mar 30, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? paperless-gpt ### 📂 What was the exact command used to execute the script? update (i.e. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/paperless-gpt.sh)") ### 📝 Provide a clear and concise description of the issue. I wanted to update my paperless-gpt LXC, and it started just fine, but then ended in an error. Unfortunately -- as I instantly continued to look for logs or any other clue -- I missed to exactly note down the error text in the console, and now it's seemingly gone. It was sth. around permission issues for the mv-command. As a consequence, the app folder in /opt is now gone, preventing me from simply redoing it (was hoping to just redeploy that way...). So my questions are: - Where would I find logs that explain what happened (or at least show that error again)? - Is there any (reasonably simple) way to redeploy within that container, even w/o the app folder existing at this point? Or am I left with killing that LXC and starting from scratch? However, I want then at least to avoid running into that same issue next time I need to update this (or any other) container. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 🔄 Steps to reproduce the issue. Type "update" in paperless-LXC shell /opt/paperless-gpt folder ### ❌ Paste the full error output (if available). Unfortunately gone ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 21:03:59 +03:00
OVERLORD commented 2026-02-04 21:04:20 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Mar 30, 2025):

Have you made a snapshot before updating?

@tremor021 commented on GitHub (Mar 30, 2025): Have you made a snapshot before updating?
OVERLORD commented 2026-02-04 21:04:32 +03:00
Author
Owner
Copy Link

@habitoti commented on GitHub (Mar 30, 2025):

Nope. I am still in the overall setup phase, so I wouldn't even mind to do a full redeploy. However as said I wanted to understand why (especially in this early phase with almost no major data being collected/handled) it already failed to update.

@habitoti commented on GitHub (Mar 30, 2025): Nope. I am still in the overall setup phase, so I wouldn't even mind to do a full redeploy. However as said I wanted to understand why (especially in this early phase with almost no major data being collected/handled) it already failed to update.
OVERLORD commented 2026-02-04 21:04:49 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 30, 2025):

Just Download the latest Release into this folder and follow the Actionscript

@MickLesk commented on GitHub (Mar 30, 2025): Just Download the latest Release into this folder and follow the Actionscript
OVERLORD commented 2026-02-04 21:04:56 +03:00
Author
Owner
Copy Link

@habitoti commented on GitHub (Mar 30, 2025):

So here is the error:

Image

After that, the paperless-gpt folder in /opt is deleted.

@habitoti commented on GitHub (Mar 30, 2025): So here is the error: <img width="945" alt="Image" src="https://github.com/user-attachments/assets/ef31e765-35c4-4525-95ae-f8137d0e01d8" /> After that, the paperless-gpt folder in /opt is deleted.
OVERLORD commented 2026-02-04 21:05:13 +03:00
Author
Owner
Copy Link

@habitoti commented on GitHub (Mar 30, 2025):

Looking at the download script, maybe it should check whether downloading and unpacking of the new version went well before deleting the existing version?

        msg_info "Updating Paperless-GPT to ${RELEASE}"
        temp_file=$(mktemp)
        wget -q "https://github.com/icereed/paperless-gpt/archive/refs/tags/v${RELEASE}.tar.gz" -O $temp_file
        tar zxf $temp_file
        rm -rf /opt/paperless-gpt
        mv paperless-gpt-${RELEASE} /opt/paperless-gpt

The last step fails, so seemingly the previous steps didn't succeed (except the folder deletion 🤨)

@habitoti commented on GitHub (Mar 30, 2025): Looking at the download script, maybe it should check whether downloading and unpacking of the new version went well _before_ deleting the existing version? ``` msg_info "Updating Paperless-GPT to ${RELEASE}" temp_file=$(mktemp) wget -q "https://github.com/icereed/paperless-gpt/archive/refs/tags/v${RELEASE}.tar.gz" -O $temp_file tar zxf $temp_file rm -rf /opt/paperless-gpt mv paperless-gpt-${RELEASE} /opt/paperless-gpt ``` The last step fails, so seemingly the previous steps didn't succeed (except the folder deletion 🤨)
OVERLORD commented 2026-02-04 21:05:16 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 30, 2025):

Read my comment above to fix manually

@MickLesk commented on GitHub (Mar 30, 2025): Read my comment above to fix manually
OVERLORD commented 2026-02-04 21:05:40 +03:00
Author
Owner
Copy Link

@habitoti commented on GitHub (Mar 30, 2025):

Yeah, I just went manually through the script, and it worked. I have no clue why it fails when running automatically. I did exactly each step one by one...

@habitoti commented on GitHub (Mar 30, 2025): Yeah, I just went manually through the script, and it worked. I have no clue why it fails when running automatically. I did exactly each step one by one...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#716
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?