SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

paperless-ngx: Update from 2.19.5 -> 2.19.6 crashed #2340

New Issue
Closed
opened 2025-11-20 05:27:40 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 05:27:40 -05:00
Owner
Copy Link

Originally created by @rapton on GitHub (Nov 16, 2025).

✅ Have you read and understood the above guidelines?

yes

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

paperless-ngx

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

8.4.11

📝 Provide a clear and concise description of the issue.

I want to update withe "update" in the console form 2.19.5 to 2.19.6 but it crashed while "Backup up user data anchor configuration". While this process the cpu load is on 95% with 4 CPU, Ram is on 3% with 4GB.

✔️ Update available: paperless 2.19.5 → 2.19.6
✔️ Stopped all Paperless-ngx Services
⠹ Backing up user data and configuration/usr/bin/update: line 1: 972 Killed bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/paperless-ngx.sh)"
⠸ Backing up user data and configuration

🔄 Steps to reproduce the issue.

Update in the console

❌ Paste the full error output (if available).

/usr/bin/update: line 1: 972 Killed bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/paperless-ngx.sh)"

🖼️ Additional context (optional).

No response

Originally created by @rapton on GitHub (Nov 16, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? paperless-ngx ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 8.4.11 ### 📝 Provide a clear and concise description of the issue. I want to update withe "update" in the console form 2.19.5 to 2.19.6 but it crashed while "Backup up user data anchor configuration". While this process the cpu load is on 95% with 4 CPU, Ram is on 3% with 4GB. ✔️ Update available: paperless 2.19.5 → 2.19.6 ✔️ Stopped all Paperless-ngx Services ⠹ Backing up user data and configuration/usr/bin/update: line 1: 972 Killed bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/paperless-ngx.sh)" ⠸ Backing up user data and configuration ### 🔄 Steps to reproduce the issue. Update in the console ### ❌ Paste the full error output (if available). /usr/bin/update: line 1: 972 Killed bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/paperless-ngx.sh)" ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:27:40 -05:00
saavagebueno commented 2025-11-20 05:27:40 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 16, 2025):

You have Killed the Update? It saved all configs and Files before removing Files. So you broke the process yourself? Why? Just because CPU ? It Takes time. Its an rebuild of UV sync, Node and Copy/pasting Files

@MickLesk commented on GitHub (Nov 16, 2025): You have Killed the Update? It saved all configs and Files before removing Files. So you broke the process yourself? Why? Just because CPU ? It Takes time. Its an rebuild of UV sync, Node and Copy/pasting Files
saavagebueno commented 2025-11-20 05:27:40 -05:00
Author
Owner
Copy Link

@rapton commented on GitHub (Nov 16, 2025):

No, I don't broke the process. The system do that after 10 minutes (ca.)

I repeat it several times... One time it runned 20 minutes with no end on 90% percent. Why you close the issue? I don't understand it.

@rapton commented on GitHub (Nov 16, 2025): No, I don't broke the process. The system do that after 10 minutes (ca.) I repeat it several times... One time it runned 20 minutes with no end on 90% percent. Why you close the issue? I don't understand it.
saavagebueno commented 2025-11-20 05:27:41 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 16, 2025):

If you have an big amount Files, it takes time. My 50G in an NVME need ~7min

@MickLesk commented on GitHub (Nov 16, 2025): If you have an big amount Files, it takes time. My 50G in an NVME need ~7min
saavagebueno commented 2025-11-20 05:27:41 -05:00
Author
Owner
Copy Link

@rapton commented on GitHub (Nov 16, 2025):

I have 8G.

@rapton commented on GitHub (Nov 16, 2025): I have 8G.
saavagebueno commented 2025-11-20 05:27:41 -05:00
Author
Owner
Copy Link

@rapton commented on GitHub (Nov 16, 2025):

I don't understand why, but after X recovery from backups, x restarts and x time "update" now it works and it need 1 minute to make the backup. Thanks.

@rapton commented on GitHub (Nov 16, 2025): I don't understand why, but after X recovery from backups, x restarts and x time "update" now it works and it need 1 minute to make the backup. Thanks.
saavagebueno commented 2025-11-20 05:27:41 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 16, 2025):

Maybe something Block your HDD/ssd at Same time? Updates, other Containers or something. Hard to say

@MickLesk commented on GitHub (Nov 16, 2025): Maybe something Block your HDD/ssd at Same time? Updates, other Containers or something. Hard to say
saavagebueno commented 2025-11-20 05:27:41 -05:00
Author
Owner
Copy Link

@rapton commented on GitHub (Nov 16, 2025):

I don't think so. Hope next update is easier ;)

@rapton commented on GitHub (Nov 16, 2025): I don't think so. Hope next update is easier ;)
saavagebueno commented 2025-11-20 05:27:41 -05:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Nov 17, 2025):

It no longer works for me either.

    ____                        __                                     
   / __ \____ _____  ___  _____/ /__  __________      ____  ____ __  __
  / /_/ / __ `/ __ \/ _ \/ ___/ / _ \/ ___/ ___/_____/ __ \/ __ `/ |/_/
 / ____/ /_/ / /_/ /  __/ /  / /  __(__  |__  )_____/ / / / /_/ />  <  
/_/    \__,_/ .___/\___/_/  /_/\___/____/____/     /_/ /_/\__, /_/|_|  
           /_/                                           /____/        

  ✔️   Update available: paperless 2.19.5 → 2.19.6
  ✔️   Stopped all Paperless-ngx Services
  ✔️   Backup completed to /opt/paperless_backup_16327
  ✔️   Python 3.13 installed
  ✔️   Setup uv 0.9.9
⠏ Fetching GitHub release: paperless (2.19.6)rm: cannot remove '/opt/paperless/consume': Device or resource busy
⠸ Fetching GitHub release: paperless (2.19.6)
[ERROR] in line 1856: exit code 0: while executing command rm -rf "${target:?}/"*

⠸ Fetching GitHub release: paperless (2.19.6)
@pafade89 commented on GitHub (Nov 17, 2025): It no longer works for me either. ``` ____ __ / __ \____ _____ ___ _____/ /__ __________ ____ ____ __ __ / /_/ / __ `/ __ \/ _ \/ ___/ / _ \/ ___/ ___/_____/ __ \/ __ `/ |/_/ / ____/ /_/ / /_/ / __/ / / / __(__ |__ )_____/ / / / /_/ /> < /_/ \__,_/ .___/\___/_/ /_/\___/____/____/ /_/ /_/\__, /_/|_| /_/ /____/ ✔️ Update available: paperless 2.19.5 → 2.19.6 ✔️ Stopped all Paperless-ngx Services ✔️ Backup completed to /opt/paperless_backup_16327 ✔️ Python 3.13 installed ✔️ Setup uv 0.9.9 ⠏ Fetching GitHub release: paperless (2.19.6)rm: cannot remove '/opt/paperless/consume': Device or resource busy ⠸ Fetching GitHub release: paperless (2.19.6) [ERROR] in line 1856: exit code 0: while executing command rm -rf "${target:?}/"* ⠸ Fetching GitHub release: paperless (2.19.6) ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2340
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?