starred/ProxmoxVE

Fork 0

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

[GH-ISSUE #9867] Incompatible upgrade of Omada Controller MongoDB #2147

New issue

Closed

opened 2026-02-26 12:51:27 +03:00 by kerem · 11 comments

kerem commented

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

Owner

Originally created by @JXF9527 on GitHub (Dec 11, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9867

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

Omada Controller

📂 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)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9.0.11

📝 Provide a clear and concise description of the issue.

MongoDB does not support cross-version upgrades. If a lower version of MongoDB was previously installed, running this script will cause MongoDB to upgrade (even if I don't want to upgrade it). It is necessary to add verification and confirmation when upgrading MongoDB (prompting about cross-version data incompatibility, or simply not upgrading MongoDB at all).

🔄 Steps to reproduce the issue.

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

❌ Paste the full error output (if available).

Oct 20 11:28:28 omada systemd[1]: Starting tpeap.service - LSB: Omada Controller...
Oct 20 11:28:29 omada tpeap[128]: check omada
Oct 20 11:28:29 omada tpeap[128]: Starting Omada Controller. Please wait.
Oct 20 11:28:35 omada tpeap[128]: ......
Oct 20 11:28:35 omada tpeap[128]: Fail to start mongo DB server

🖼️ Additional context (optional).

No response

Originally created by @JXF9527 on GitHub (Dec 11, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9867 ### ✅ 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? Omada Controller ### 📂 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)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9.0.11 ### 📝 Provide a clear and concise description of the issue. MongoDB does not support cross-version upgrades. If a lower version of MongoDB was previously installed, running this script will cause MongoDB to upgrade (even if I don't want to upgrade it). It is necessary to add verification and confirmation when upgrading MongoDB (prompting about cross-version data incompatibility, or simply not upgrading MongoDB at all). ### 🔄 Steps to reproduce the issue. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/omada.sh)" ### ❌ Paste the full error output (if available). Oct 20 11:28:28 omada systemd[1]: Starting tpeap.service - LSB: Omada Controller... Oct 20 11:28:29 omada tpeap[128]: check omada Oct 20 11:28:29 omada tpeap[128]: Starting Omada Controller. Please wait. Oct 20 11:28:35 omada tpeap[128]: ...... Oct 20 11:28:35 omada tpeap[128]: Fail to start mongo DB server ### 🖼️ Additional context (optional). _No response_

kerem

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

closed this issue
added the
not a script issue
label

kerem commented

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

Author

Owner

@JXF9527 commented on GitHub (Dec 11, 2025):

Perhaps we can handle it like unifi.sh does: do not process MongoDB during upgrades, and only install MongoDB in install.sh.

@JXF9527 commented on GitHub (Dec 11, 2025): Perhaps we can handle it like unifi.sh does: do not process MongoDB during upgrades, and only install MongoDB in install.sh.

kerem commented

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

Author

Owner

@MickLesk commented on GitHub (Dec 11, 2025):

It is the Case?

@MickLesk commented on GitHub (Dec 11, 2025): It is the Case?

kerem commented

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

Author

Owner

@JXF9527 commented on GitHub (Dec 11, 2025):

@MickLesk Yes, if upgrading from 4.4 to 7.0, you must upgrade incrementally: 4.4 -> 5.0 -> 6.0 -> 7.0

@JXF9527 commented on GitHub (Dec 11, 2025): @MickLesk Yes, if upgrading from 4.4 to 7.0, you must upgrade incrementally: 4.4 -> 5.0 -> 6.0 -> 7.0

kerem commented

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

Author

Owner

@MickLesk commented on GitHub (Dec 11, 2025):

Show me the upgrade of mongo in the Script?

@MickLesk commented on GitHub (Dec 11, 2025): Show me the upgrade of mongo in the Script?

kerem commented

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

Author

Owner

@JXF9527 commented on GitHub (Dec 11, 2025):

@MickLesk Perhaps the MongoDB upgrade process can be removed from the upgrade method.

@JXF9527 commented on GitHub (Dec 11, 2025): @MickLesk Perhaps the MongoDB upgrade process can be removed from the upgrade method.

kerem commented

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

Author

Owner

@MickLesk commented on GitHub (Dec 11, 2025):

Then show me the Upgrade of Mongo in the update_script, then we can remove it.

@MickLesk commented on GitHub (Dec 11, 2025): Then show me the Upgrade of Mongo in the update_script, then we can remove it.

kerem commented

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

Author

Owner

@JXF9527 commented on GitHub (Dec 11, 2025):

@MickLesk https://www.mongodb.com/docs/manual/release-notes/7.0-upgrade-standalone/

@JXF9527 commented on GitHub (Dec 11, 2025): @MickLesk https://www.mongodb.com/docs/manual/release-notes/7.0-upgrade-standalone/

kerem commented

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

Author

Owner

@MickLesk commented on GitHub (Dec 11, 2025):

you dont understand? we dont update mongo in our scripts.

@MickLesk commented on GitHub (Dec 11, 2025): you dont understand? we dont update mongo in our scripts.

kerem commented

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

Author

Owner

@JXF9527 commented on GitHub (Dec 11, 2025):

@MickLesk ok, thanks

@JXF9527 commented on GitHub (Dec 11, 2025): @MickLesk ok, thanks

kerem commented

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

Author

Owner

@JXF9527 commented on GitHub (Dec 11, 2025):

This is the logic for upgrading MongoDB in the script:

function update_script() {
……

msg_info "Updating MongoDB"
if lscpu | grep -q 'avx'; then
MONGO_VERSION="8.0"
else
msg_error "No AVX detected (CPU-Flag)! We have discontinued support for this. You are welcome to try it manually with a Debian LXC, but due to the many issues with Omada, we currently only support AVX CPUs."
exit 10
fi

……
}

@JXF9527 commented on GitHub (Dec 11, 2025): This is the logic for upgrading MongoDB in the script: function update_script() { …… msg_info "Updating MongoDB" if lscpu | grep -q 'avx'; then MONGO_VERSION="8.0" else msg_error "No AVX detected (CPU-Flag)! We have discontinued support for this. You are welcome to try it manually with a Debian LXC, but due to the many issues with Omada, we currently only support AVX CPUs." exit 10 fi …… }

kerem commented

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

Author

Owner

@JXF9527 commented on GitHub (Dec 11, 2025):

Oh sorry.. Just realized the upgrade logic has already been removed.

@JXF9527 commented on GitHub (Dec 11, 2025): Oh sorry.. Just realized the upgrade logic has already been removed.

kerem referenced this issue

2026-02-26 13:33:56 +03:00

[PR #2147] [MERGED] Fix: Zerotier-One fixed missing dependency #3568

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#2147

No description provided.

Rows
Columns