SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-11 18:52:12 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Update LXC script exits itself #761

New Issue
Open
opened 2025-11-20 04:53:39 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 04:53:39 -05:00
Owner
Copy Link

Originally created by @khthe8th on GitHub (Mar 22, 2025).

✅ Have you read and understood the above guidelines?

yes

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

UpdateLXC

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-lxcs.sh)"

📝 Provide a clear and concise description of the issue.

Run bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-lxcs.sh)" in proxmox shell, it randomly quits after each LXC (sometimes gets through a couple before quitting). Ended up running it and having to skip one LXC at a time in the prompt until all LXCs got updated. Below are a few examples of the last messages when it quit. I have 100-114 as LXCs, but you can see these just quit randomly.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-lxcs.sh)" in proxmox shell, it randomly quits after each LXC (sometimes gets through a couple before quitting).

❌ Paste the full error output (if available).

wget/stable 1.21.3-1+deb12u1 amd64 [upgradable from: 1.21.3-1+b2]
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
root@Homelab:~#

[Info] Updating 101 : sonarr - Boot Disk: 53% full [1.9G/3.9G used, 1.7G free]

Listing... Done
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@Homelab:~#

Processing triggers for dbus (1.14.10-1deb12u1) ...
Processing triggers for mailcap (3.70+nmu1) ...
root@Homelab:#

🖼️ Additional context (optional).

I run this script every week without issue, not sure why today it has started acting weird.

Originally created by @khthe8th on GitHub (Mar 22, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? UpdateLXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-lxcs.sh)" ### 📝 Provide a clear and concise description of the issue. Run bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-lxcs.sh)" in proxmox shell, it randomly quits after each LXC (sometimes gets through a couple before quitting). Ended up running it and having to skip one LXC at a time in the prompt until all LXCs got updated. Below are a few examples of the last messages when it quit. I have 100-114 as LXCs, but you can see these just quit randomly. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-lxcs.sh)" in proxmox shell, it randomly quits after each LXC (sometimes gets through a couple before quitting). ### ❌ Paste the full error output (if available). wget/stable 1.21.3-1+deb12u1 amd64 [upgradable from: 1.21.3-1+b2] E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. root@Homelab:~# [Info] Updating 101 : sonarr - Boot Disk: 53% full [1.9G/3.9G used, 1.7G free] Listing... Done Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@Homelab:~# Processing triggers for dbus (1.14.10-1~deb12u1) ... Processing triggers for mailcap (3.70+nmu1) ... root@Homelab:~# ### 🖼️ Additional context (optional). I run this script every week without issue, not sure why today it has started acting weird.
saavagebueno added the bug label 2025-11-20 04:53:39 -05:00
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#761
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?