Omada LXC Helper is EOL, should be updated

[kogansnet]

✅ 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

[MickLesk]

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.

[kogansnet]

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.

[dave-yap]

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.

[kogansnet]

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

[dave-yap]

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]

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?

[tremor021]

@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

[chiabre]

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.

[kogansnet]

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!

[MickLesk]

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.

[kogansnet]

Thank you, for the info!