starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #10700] update-lxcs.sh sometimes fails in the middle and doesn't update all LXCs. #2302

New issue

Closed

opened 2026-02-26 12:51:59 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 12:51:59 +03:00

Owner

Originally created by @mikeage on GitHub (Jan 11, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10700

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

update-lxcs

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/update-lxcs.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.4/5ac30304265fbd8e

📝 Provide a clear and concise description of the issue.

Sometimes, when running update-lxcs.sh, it aborts midway through. The pct exec command to do the upgrade occasionally fails (adding some debug reveals that the pct exec returns a 129); I have only tested with LXCs running Debian or Ubuntu.

🔄 Steps to reproduce the issue.

Run update-lxcs.sh

❌ Paste the full error output (if available).

   __  __          __      __          __   _  ________
  / / / /___  ____/ /___ _/ /____     / /  | |/ / ____/
 / / / / __ \/ __  / __ `/ __/ _ \   / /   |   / /
/ /_/ / /_/ / /_/ / /_/ / /_/  __/  / /___/   / /___
\____/ .___/\__,_/\__,_/\__/\___/  /_____/_/|_\____/
    /_/

[Info] Updating 109 : prometheus - Boot Disk: 21% full [0.8G/4.0G used, 3.2G 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@u59-proxmox:~#

This is a failure. The actual container various; it's not always prometheus. Sometimes it completes successfully:

   __  __          __      __          __   _  ________
  / / / /___  ____/ /___ _/ /____     / /  | |/ / ____/
 / / / / __ \/ __  / __ `/ __/ _ \   / /   |   / /
/ /_/ / /_/ / /_/ / /_/ / /_/  __/  / /___/   / /___
\____/ .___/\__,_/\__,_/\__/\___/  /_____/_/|_\____/
    /_/

The process is complete, and the containers have been successfully updated.


root@u59-proxmox:~#

There is no verbose debug because this script doesn't have that option.

🖼️ Additional context (optional).

No response

Originally created by @mikeage on GitHub (Jan 11, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10700 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? update-lxcs ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/update-lxcs.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.4/5ac30304265fbd8e ### 📝 Provide a clear and concise description of the issue. Sometimes, when running update-lxcs.sh, it aborts midway through. The pct exec command to do the upgrade occasionally fails (adding some debug reveals that the pct exec returns a 129); I have only tested with LXCs running Debian or Ubuntu. ### 🔄 Steps to reproduce the issue. Run update-lxcs.sh ### ❌ Paste the full error output (if available). ``` __ __ __ __ __ _ ________ / / / /___ ____/ /___ _/ /____ / / | |/ / ____/ / / / / __ \/ __ / __ `/ __/ _ \ / / | / / / /_/ / /_/ / /_/ / /_/ / /_/ __/ / /___/ / /___ \____/ .___/\__,_/\__,_/\__/\___/ /_____/_/|_\____/ /_/ [Info] Updating 109 : prometheus - Boot Disk: 21% full [0.8G/4.0G used, 3.2G 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@u59-proxmox:~# ``` This is a failure. The actual container various; it's not always prometheus. Sometimes it completes successfully: ``` __ __ __ __ __ _ ________ / / / /___ ____/ /___ _/ /____ / / | |/ / ____/ / / / / __ \/ __ / __ `/ __/ _ \ / / | / / / /_/ / /_/ / /_/ / /_/ / /_/ __/ / /___/ / /___ \____/ .___/\__,_/\__,_/\__/\___/ /_____/_/|_\____/ /_/ The process is complete, and the containers have been successfully updated. root@u59-proxmox:~# ``` There is no verbose debug because this script doesn't have that option. ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:51:59 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:51:59 +03:00

Author

Owner

@mikeage commented on GitHub (Jan 11, 2026):

Removing the rm -rf /usr/lib/python3.*/EXTERNALLY-MANAGED makes it succeed consistently, as does adding || true before the bash command finishes. I'm not 100% sure why, though, since these files seem to almost never exist, so I don't know why rm sometimes works and sometimes fails (I tried adding a stat too to confirm that they're not there)

@mikeage commented on GitHub (Jan 11, 2026): Removing the `rm -rf /usr/lib/python3.*/EXTERNALLY-MANAGED` makes it succeed consistently, as does adding `|| true` before the bash command finishes. I'm not 100% sure why, though, since these files seem to almost never exist, so I don't know why rm sometimes works and sometimes fails (I tried adding a `stat` too to confirm that they're not there)

kerem referenced this issue

2026-02-26 13:34:19 +03:00

[PR #2302] [MERGED] Fix: Pingvin wrong variable used for version tracking #3678

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2302

No description provided.

Rows
Columns