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 11 Packages Projects Releases 10 Wiki Activity

Update LXC script exits itself #683

New Issue
Closed
opened 2026-02-04 20:50:00 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-04 20:50:00 +03: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.
OVERLORD added the bug label 2026-02-04 20:50:00 +03:00
OVERLORD commented 2026-02-04 20:50:08 +03:00
Author
Owner
Copy Link

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

That caused by one of your lxc or your node has an break in apt.

"dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem."

@MickLesk commented on GitHub (Mar 22, 2025): That caused by one of your lxc or your node has an break in apt. "dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem."
OVERLORD commented 2026-02-04 20:50:15 +03:00
Author
Owner
Copy Link

@khthe8th commented on GitHub (Mar 22, 2025):

That caused by one of your lxc or your node has an break in apt.

"dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem."

yes as you can see though that isn't always why it quits, most times it just quits instead of moving to the next one.

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@Homelab:~#

@khthe8th commented on GitHub (Mar 22, 2025): > That caused by one of your lxc or your node has an break in apt. > > "dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem." yes as you can see though that isn't always why it quits, most times it just quits instead of moving to the next one. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@Homelab:~#
OVERLORD commented 2026-02-04 20:50:21 +03:00
Author
Owner
Copy Link

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

But you use the Script correctly? You choose the skip, not the Update

@MickLesk commented on GitHub (Mar 22, 2025): But you use the Script correctly? You choose the skip, not the Update
OVERLORD commented 2026-02-04 20:50:31 +03:00
Author
Owner
Copy Link

@khthe8th commented on GitHub (Mar 23, 2025):

But you use the Script correctly? You choose the skip, not the Update

No. I try to update all and it stops after 1 or 2. So since those are updated I skip the first 1 or 2 then it does the next 1 or 2 and stops.

@khthe8th commented on GitHub (Mar 23, 2025): > But you use the Script correctly? You choose the skip, not the Update No. I try to update all and it stops after 1 or 2. So since those are updated I skip the first 1 or 2 then it does the next 1 or 2 and stops.
OVERLORD commented 2026-02-04 20:50:41 +03:00
Author
Owner
Copy Link

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

Cant reproduce. Can you take a Screenshare/Screenrecord?

@MickLesk commented on GitHub (Mar 23, 2025): Cant reproduce. Can you take a Screenshare/Screenrecord?
OVERLORD commented 2026-02-04 20:50:53 +03:00
Author
Owner
Copy Link

@khthe8th commented on GitHub (Mar 23, 2025):

I've tried it again just now and it was back to working as expected. I am wondering if it is due to earlier I had high CPU usage from running tasks on various LXC. Perhaps this caused the script to crash

@khthe8th commented on GitHub (Mar 23, 2025): I've tried it again just now and it was back to working as expected. I am wondering if it is due to earlier I had high CPU usage from running tasks on various LXC. Perhaps this caused the script to crash
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
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#683
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?