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

Omada LXC Helper is EOL, should be updated #456

New Issue
Closed
opened 2026-02-04 19:00:24 +03:00 by OVERLORD · 11 comments
OVERLORD commented 2026-02-04 19:00:24 +03:00
Owner
Copy Link

Originally created by @kogansnet on GitHub (Feb 7, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Omada Controller LXC

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

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

📝 Provide a clear and concise description of the issue.

After installing Omada V5.15.20.X Omada crashes after some time, becaufe of outdated MongoDB V3.6
Purging and installing MongoDB 8.0 bring system running again.

wget https://repo.mongodb.org/apt/debian/dists/bookworm/mongodb-org/8.0/main/binary-amd64/mongodb-org-server_8.0.4_amd64.deb

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

🔄 Steps to reproduce the issue.

Update Omada V5.15.8.X to V5.15.20.X

❌ Paste the full error output (if available).

none

🖼️ Additional context (optional).

No response

Originally created by @kogansnet on GitHub (Feb 7, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Omada Controller LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/omada.sh)" ### 📝 Provide a clear and concise description of the issue. After installing Omada V5.15.20.X Omada crashes after some time, becaufe of outdated MongoDB V3.6 Purging and installing MongoDB 8.0 bring system running again. wget https://repo.mongodb.org/apt/debian/dists/bookworm/mongodb-org/8.0/main/binary-amd64/mongodb-org-server_8.0.4_amd64.deb ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 🔄 Steps to reproduce the issue. Update Omada V5.15.8.X to V5.15.20.X ### ❌ Paste the full error output (if available). none ### 🖼️ Additional context (optional). _No response_
OVERLORD added the investigation label 2026-02-04 19:00:24 +03:00
OVERLORD commented 2026-02-04 19:00:35 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 7, 2025):

Its possible to create an restore / backup?

The changeover would be huge, so I'm considering whether we should build a new LXC. In other words, the current one will be updated so that it no longer works for old MongoDB, but a new installation is necessary.

@MickLesk commented on GitHub (Feb 7, 2025): Its possible to create an restore / backup? The changeover would be huge, so I'm considering whether we should build a new LXC. In other words, the current one will be updated so that it no longer works for old MongoDB, but a new installation is necessary.
OVERLORD commented 2026-02-04 19:00:41 +03:00
Author
Owner
Copy Link

@kogansnet commented on GitHub (Feb 7, 2025):

Its possible to create an restore / backup?

The changeover would be huge, so I'm considering whether we should build a new LXC. In other words, the current one will be updated so that it no longer works for old MongoDB, but a new installation is necessary.

I played around and can confirm:

a) on CPUs with AVX feature, its possible to backup, remove MDB3.6, install MDB8, Omada V5.15.20.X and restore the backup.
b) on CPUs without AVX feature, only MDB4.4 is possible, but controller restore will not work. Only new installation of omada AND "Site import" will work. As workaround.

@kogansnet commented on GitHub (Feb 7, 2025): > Its possible to create an restore / backup? > > The changeover would be huge, so I'm considering whether we should build a new LXC. In other words, the current one will be updated so that it no longer works for old MongoDB, but a new installation is necessary. I played around and can confirm: a) on CPUs with AVX feature, its possible to backup, remove MDB3.6, install MDB8, Omada V5.15.20.X and restore the backup. b) on CPUs without AVX feature, only MDB4.4 is possible, but controller restore will **not** work. Only new installation of omada AND "Site import" will work. As workaround.
OVERLORD commented 2026-02-04 19:00:52 +03:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Feb 7, 2025):

I managed to simply uninstall the old MongoDB that's on my LXC and installed the new MongoDB v7. It prompts me when uninstalling if I would like to backup the configs, and simply using update works to install the new Omada version on the new v7 DB. It prompts whether I'd like to import my config too. Haven't checked if my configs are still the same, but at least there's that.

@dave-yap commented on GitHub (Feb 7, 2025): I managed to simply uninstall the old MongoDB that's on my LXC and installed the new MongoDB v7. It prompts me when uninstalling if I would like to backup the configs, and simply using `update` works to install the new Omada version on the new v7 DB. It prompts whether I'd like to import my config too. Haven't checked if my configs are still the same, but at least there's that.
OVERLORD commented 2026-02-04 19:01:00 +03:00
Author
Owner
Copy Link

@kogansnet commented on GitHub (Feb 7, 2025):

I managed to simply uninstall the old MongoDB that's on my LXC and installed the new MongoDB v7. It prompts me when uninstalling if I would like to backup the configs, and simply using update works to install the new Omada version on the new v7 DB. It prompts whether I'd like to import my config too. Haven't checked if my configs are still the same, but at least there's that.

I tried the same, but after restoring the prompting backup config inside LXC, MDB sais: Faild to start MongoDB (or something). I tried it with MDB4.4, 6.0, 7.0 and 8.0. Clear install is working fine.

LXC install is made by the lines down, for CPU w/o AVX:

apt update
apt upgrade -y
apt install curl jsvc libcommons-daemon-java -y

wget https://security.debian.org/debian-security/pool/updates/main/o/openssl/libssl1.1_1.1.1w-0+deb11u2_amd64.deb
dpkg -i libssl1.1_1.1.1w-0+deb11u2_amd64.deb

wget https://repo.mongodb.org/apt/debian/dists/buster/mongodb-org/4.4/main/binary-amd64/mongodb-org-server_4.4.29_amd64.deb
dpkg -i mongodb-org-server_4.4.29_amd64.deb

wget https://download.tplinkcloud.com/firmware/omada_v5.15.20.10_linux_x64_20250122095751_1737709061629.deb
dpkg -i omada_v5.15.20.10_linux_x64_20250122095751_1737709061629.deb

AND for CPU with AVX:

apt update
apt upgrade -y
apt install curl jsvc libcommons-daemon-java -y

wget https://repo.mongodb.org/apt/debian/dists/bookworm/mongodb-org/8.0/main/binary-amd64/mongodb-org-server_8.0.4_amd64.deb
dpkg -i mongodb-org-server_8.0.4_amd64.deb

wget https://download.tplinkcloud.com/firmware/omada_v5.15.20.10_linux_x64_20250122095751_1737709061629.deb
dpkg -i omada_v5.15.20.10_linux_x64_20250122095751_1737709061629.deb

@kogansnet commented on GitHub (Feb 7, 2025): > I managed to simply uninstall the old MongoDB that's on my LXC and installed the new MongoDB v7. It prompts me when uninstalling if I would like to backup the configs, and simply using `update` works to install the new Omada version on the new v7 DB. It prompts whether I'd like to import my config too. Haven't checked if my configs are still the same, but at least there's that. I tried the same, but after restoring the prompting backup config inside LXC, MDB sais: Faild to start MongoDB (or something). I tried it with MDB4.4, 6.0, 7.0 and 8.0. Clear install is working fine. LXC install is made by the lines down, for CPU w/o AVX: apt update apt upgrade -y apt install curl jsvc libcommons-daemon-java -y wget https://security.debian.org/debian-security/pool/updates/main/o/openssl/libssl1.1_1.1.1w-0+deb11u2_amd64.deb dpkg -i libssl1.1_1.1.1w-0+deb11u2_amd64.deb wget https://repo.mongodb.org/apt/debian/dists/buster/mongodb-org/4.4/main/binary-amd64/mongodb-org-server_4.4.29_amd64.deb dpkg -i mongodb-org-server_4.4.29_amd64.deb wget https://download.tplinkcloud.com/firmware/omada_v5.15.20.10_linux_x64_20250122095751_1737709061629.deb dpkg -i omada_v5.15.20.10_linux_x64_20250122095751_1737709061629.deb AND for CPU with AVX: apt update apt upgrade -y apt install curl jsvc libcommons-daemon-java -y wget https://repo.mongodb.org/apt/debian/dists/bookworm/mongodb-org/8.0/main/binary-amd64/mongodb-org-server_8.0.4_amd64.deb dpkg -i mongodb-org-server_8.0.4_amd64.deb wget https://download.tplinkcloud.com/firmware/omada_v5.15.20.10_linux_x64_20250122095751_1737709061629.deb dpkg -i omada_v5.15.20.10_linux_x64_20250122095751_1737709061629.deb
OVERLORD commented 2026-02-04 19:01:08 +03:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Feb 8, 2025):

Hey, I went to check. Official release is only up to v5.15.8.2 while v5.15.20.x is actually a beta release?

@dave-yap commented on GitHub (Feb 8, 2025): Hey, I went to check. Official release is only up to v5.15.8.2 while v5.15.20.x is actually a beta release?
OVERLORD commented 2026-02-04 19:01:14 +03:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Feb 10, 2025):

Its possible to create an restore / backup?

The changeover would be huge, so I'm considering whether we should build a new LXC. In other words, the current one will be updated so that it no longer works for old MongoDB, but a new installation is necessary.

Is it confirmed that we're planning to do a new LXC for Omada instead of editing the current one?

@dave-yap commented on GitHub (Feb 10, 2025): > Its possible to create an restore / backup? > > The changeover would be huge, so I'm considering whether we should build a new LXC. In other words, the current one will be updated so that it no longer works for old MongoDB, but a new installation is necessary. Is it confirmed that we're planning to do a new LXC for Omada instead of editing the current one?
OVERLORD commented 2026-02-04 19:01:18 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 13, 2025):

@dave-yap before we do anything, we need to check if any breaking changes are introduced with the new update, as things differ for AVX and non-AVX CPU's

@MickLesk we can lscpu | grep avx maybe and setup 2 different upgrade paths? that would require script rewrite i guess

@tremor021 commented on GitHub (Feb 13, 2025): @dave-yap before we do anything, we need to check if any breaking changes are introduced with the new update, as things differ for AVX and non-AVX CPU's @MickLesk we can ` lscpu | grep avx` maybe and setup 2 different upgrade paths? that would require script rewrite i guess
OVERLORD commented 2026-02-04 19:01:22 +03:00
Author
Owner
Copy Link

@chiabre commented on GitHub (Feb 21, 2025):

While waiting for the new LXC, I found a temporary workaround that has been working for me so far: increasing the memory allocation for the container without updating MongoDB.

I noticed that Omada crashes were triggered by a MongoDB crash, which in turn seemed to coincide with the container's memory usage reaching 100%. Increasing the available memory has prevented immediate crashes, but the memory usage continues to rise over time.

At this point, this feels more like a workaround than a proper solution, as I’m not sure if memory usage will eventually plateau or if I’m just delaying an inevitable crash by allocating more memory.

@chiabre commented on GitHub (Feb 21, 2025): While waiting for the new LXC, I found a temporary workaround that has been working for me so far: increasing the memory allocation for the container without updating MongoDB. I noticed that Omada crashes were triggered by a MongoDB crash, which in turn seemed to coincide with the container's memory usage reaching 100%. Increasing the available memory has prevented immediate crashes, but the memory usage continues to rise over time. At this point, this feels more like a workaround than a proper solution, as I’m not sure if memory usage will eventually plateau or if I’m just delaying an inevitable crash by allocating more memory.
OVERLORD commented 2026-02-04 19:01:30 +03:00
Author
Owner
Copy Link

@kogansnet commented on GitHub (Feb 28, 2025):

I am very sorry! Thank you for providing new version!
But for since the update, omada lxc script will only install, if the CPU has AVX feature.
Could it be changed the way, unifi script works? It recognizes, if AVX, it installs new MDB, if not, it will install MDB 4.4.
thank you!

@kogansnet commented on GitHub (Feb 28, 2025): I am very sorry! Thank you for providing new version! But for since the update, omada lxc script will only install, if the CPU has AVX feature. Could it be changed the way, unifi script works? It recognizes, if AVX, it installs new MDB, if not, it will install MDB 4.4. thank you!
OVERLORD commented 2026-02-04 19:01:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 28, 2025):

No its removed. We have decided to leave this option out due to the multitude of problems with TP-Link, their update logic and the whole project. The project has only caused problems in the last few months because something so destructive was always being updated.

MongoDB 4.4. is also no longer available on a current Debian 12 without having to go through cumbersome and unmaintainable backports.

@MickLesk commented on GitHub (Feb 28, 2025): No its removed. We have decided to leave this option out due to the multitude of problems with TP-Link, their update logic and the whole project. The project has only caused problems in the last few months because something so destructive was always being updated. MongoDB 4.4. is also no longer available on a current Debian 12 without having to go through cumbersome and unmaintainable backports.
OVERLORD commented 2026-02-04 19:01:46 +03:00
Author
Owner
Copy Link

@kogansnet commented on GitHub (Feb 28, 2025):

Thank you, for the info!

@kogansnet commented on GitHub (Feb 28, 2025): Thank you, for the info!
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
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label investigation
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#456
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?