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

Omada Controller update fail #2287

New Issue
Closed
opened 2025-11-20 05:26:50 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:26:50 -05:00
Owner
Copy Link

Originally created by @Nicowars on GitHub (Nov 9, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Omada Controller

📂 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?

9.0.11

📝 Provide a clear and concise description of the issue.

While updating the Omada Controller LXC using the update command in the console, the script hung during the MongoDB update (which the text reported as updating from 8.0 to 8.0) and would not proceed. After rebooting the LXC, Omada kept working, but now the script fails with the following error: [ERROR] in line 78: exit code 0: while executing command sort -u.

🔄 Steps to reproduce the issue.

Updating the Omada Controller LXC with the built-in Update command from VE Scripts is failing. A new LXC creation with the script executes flawlessly, but attempting to update that new LXC generates the same error.

❌ Paste the full error output (if available).

0

🖼️ Additional context (optional).

No response

Originally created by @Nicowars on GitHub (Nov 9, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Omada Controller ### 📂 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? 9.0.11 ### 📝 Provide a clear and concise description of the issue. While updating the Omada Controller LXC using the update command in the console, the script hung during the MongoDB update (which the text reported as updating from 8.0 to 8.0) and would not proceed. After rebooting the LXC, Omada kept working, but now the script fails with the following error: [ERROR] in line 78: exit code 0: while executing command sort -u. ### 🔄 Steps to reproduce the issue. Updating the Omada Controller LXC with the built-in Update command from VE Scripts is failing. A new LXC creation with the script executes flawlessly, but attempting to update that new LXC generates the same error. ### ❌ Paste the full error output (if available). 0 ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:26:50 -05:00
saavagebueno commented 2025-11-20 05:26:51 -05:00
Author
Owner
Copy Link

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

no logs? no Screenshots? No Error Output? Should i play LOTTO?

@MickLesk commented on GitHub (Nov 10, 2025): no logs? no Screenshots? No Error Output? Should i play LOTTO?
saavagebueno commented 2025-11-20 05:26:51 -05:00
Author
Owner
Copy Link

@shaggee commented on GitHub (Nov 10, 2025):

Same here:

Image
@shaggee commented on GitHub (Nov 10, 2025): Same here: <img width="600" height="174" alt="Image" src="https://github.com/user-attachments/assets/e7b7ddb3-99b4-4562-b903-a33c49e54d86" />
saavagebueno commented 2025-11-20 05:26:51 -05:00
Author
Owner
Copy Link

@delzear commented on GitHub (Nov 12, 2025):

Running dpkg --configure -a solved my issue

@delzear commented on GitHub (Nov 12, 2025): Running `dpkg --configure -a` solved my issue
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#2287
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?