SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Omada controller - Mongo version issue #2240

New Issue
Closed
opened 2025-11-20 05:25:57 -05:00 by saavagebueno · 17 comments
saavagebueno commented 2025-11-20 05:25:57 -05:00
Owner
Copy Link

Originally created by @cfilkins on GitHub (Nov 4, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Omada

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.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.0.11/3bf5476b8a4699e2 (running kernel: 6.14.11-4-pve)

📝 Provide a clear and concise description of the issue.

After updating my LXC with the most recent version of the script, Omada fails to start. The script shows "Fail to start mongo DB server."

Looking through the MongoDb logs, it appears that this tries to jump too many versions of MongoDb:
"msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."

🔄 Steps to reproduce the issue.

Run upgrade script, observe Omada fails to start.

mongod --dbpath /opt/tplink/EAPController/data/db --repair

The error appears near the end of the stack trace.

❌ Paste the full error output (if available).

{"t":{"$date":"2025-11-04T16:27:10.152-05:00"},"s":"I", "c":"CONTROL", "id":23285, "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
{"t":{"$date":"2025-11-04T16:27:10.152-05:00"},"s":"I", "c":"CONTROL", "id":5945603, "ctx":"main","msg":"Multi threading initialized"}
{"t":{"$date":"2025-11-04T16:27:10.153-05:00"},"s":"I", "c":"NETWORK", "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set at least one of the related parameters","attr":{"relatedParameters":["tcpFastOpenServer","tcpFastOpenClient","tcpFastOpenQueueSize"]}}
{"t":{"$date":"2025-11-04T16:27:10.154-05:00"},"s":"I", "c":"NETWORK", "id":4915701, "ctx":"main","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":25},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":25},"outgoing":{"minWireVersion":6,"maxWireVersion":25},"isInternalClient":true}}}
{"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"TENANT_M", "id":7091600, "ctx":"main","msg":"Starting TenantMigrationAccessBlockerRegistry"}
{"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"CONTROL", "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":2400,"port":27017,"dbPath":"/opt/tplink/EAPController/data/db","architecture":"64-bit","host":"omada"}}
{"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"CONTROL", "id":23403, "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"8.0.15","gitVersion":"f79b970f08f60c41491003cd55a3dd459a279c39","openSSLVersion":"OpenSSL 3.0.17 1 Jul 2025","modules":[],"allocator":"tcmalloc-google","environment":{"distmod":"debian12","distarch":"x86_64","target_arch":"x86_64"}}}}
{"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"CONTROL", "id":51765, "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"","version":"Kernel 6.14.11-4-pve"}}}
{"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"CONTROL", "id":21951, "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"repair":true,"storage":{"dbPath":"/opt/tplink/EAPController/data/db"}}}}
{"t":{"$date":"2025-11-04T16:27:10.157-05:00"},"s":"I", "c":"STORAGE", "id":22270, "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"/opt/tplink/EAPController/data/db","storageEngine":"wiredTiger"}}
{"t":{"$date":"2025-11-04T16:27:10.157-05:00"},"s":"I", "c":"STORAGE", "id":22297, "ctx":"initandlisten","msg":"Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem","tags":["startupWarnings"]}
{"t":{"$date":"2025-11-04T16:27:10.157-05:00"},"s":"I", "c":"STORAGE", "id":22315, "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=3584M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,remove=true,path=journal,compressor=snappy),builtin_extension_config=(zstd=(compression_level=6)),file_manager=(close_idle_time=600,close_scan_interval=10,close_handle_minimum=2000),statistics_log=(wait=0),json_output=(error,message),verbose=[recovery_progress:1,checkpoint_progress:1,compact_progress:1,backup:0,checkpoint:0,compact:0,evict:0,history_store:0,recovery:0,rts:0,salvage:0,tiered:0,timestamp:0,transaction:0,verify:0,log:0],prefetch=(available=true,default=false),"}}
{"t":{"$date":"2025-11-04T16:27:10.766-05:00"},"s":"W", "c":"STORAGE", "id":22347, "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."}
{"t":{"$date":"2025-11-04T16:27:10.766-05:00"},"s":"W", "c":"STORAGE", "id":22349, "ctx":"initandlisten","msg":"Attempting to salvage WiredTiger metadata"}
{"t":{"$date":"2025-11-04T16:27:10.801-05:00"},"s":"F", "c":"STORAGE", "id":50947, "ctx":"initandlisten","msg":"Failed to salvage WiredTiger metadata","attr":{"details":"-31802: WT_ERROR: non-specific WiredTiger error"}}
{"t":{"$date":"2025-11-04T16:27:10.801-05:00"},"s":"F", "c":"ASSERT", "id":23091, "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":50947,"file":"src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp","line":768}}
{"t":{"$date":"2025-11-04T16:27:10.801-05:00"},"s":"F", "c":"ASSERT", "id":23092, "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"}

🖼️ Additional context (optional).

No response

Originally created by @cfilkins on GitHub (Nov 4, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Omada ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.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.0.11/3bf5476b8a4699e2 (running kernel: 6.14.11-4-pve) ### 📝 Provide a clear and concise description of the issue. After updating my LXC with the most recent version of the script, Omada fails to start. The script shows "Fail to start mongo DB server." Looking through the MongoDb logs, it appears that this tries to jump too many versions of MongoDb: "msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade." ### 🔄 Steps to reproduce the issue. Run upgrade script, observe Omada fails to start. mongod --dbpath /opt/tplink/EAPController/data/db --repair The error appears near the end of the stack trace. ### ❌ Paste the full error output (if available). {"t":{"$date":"2025-11-04T16:27:10.152-05:00"},"s":"I", "c":"CONTROL", "id":23285, "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"} {"t":{"$date":"2025-11-04T16:27:10.152-05:00"},"s":"I", "c":"CONTROL", "id":5945603, "ctx":"main","msg":"Multi threading initialized"} {"t":{"$date":"2025-11-04T16:27:10.153-05:00"},"s":"I", "c":"NETWORK", "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set at least one of the related parameters","attr":{"relatedParameters":["tcpFastOpenServer","tcpFastOpenClient","tcpFastOpenQueueSize"]}} {"t":{"$date":"2025-11-04T16:27:10.154-05:00"},"s":"I", "c":"NETWORK", "id":4915701, "ctx":"main","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":25},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":25},"outgoing":{"minWireVersion":6,"maxWireVersion":25},"isInternalClient":true}}} {"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"TENANT_M", "id":7091600, "ctx":"main","msg":"Starting TenantMigrationAccessBlockerRegistry"} {"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"CONTROL", "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":2400,"port":27017,"dbPath":"/opt/tplink/EAPController/data/db","architecture":"64-bit","host":"omada"}} {"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"CONTROL", "id":23403, "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"8.0.15","gitVersion":"f79b970f08f60c41491003cd55a3dd459a279c39","openSSLVersion":"OpenSSL 3.0.17 1 Jul 2025","modules":[],"allocator":"tcmalloc-google","environment":{"distmod":"debian12","distarch":"x86_64","target_arch":"x86_64"}}}} {"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"CONTROL", "id":51765, "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"PRETTY_NAME=\"Debian GNU/Linux 12 (bookworm)\"","version":"Kernel 6.14.11-4-pve"}}} {"t":{"$date":"2025-11-04T16:27:10.155-05:00"},"s":"I", "c":"CONTROL", "id":21951, "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"repair":true,"storage":{"dbPath":"/opt/tplink/EAPController/data/db"}}}} {"t":{"$date":"2025-11-04T16:27:10.157-05:00"},"s":"I", "c":"STORAGE", "id":22270, "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"/opt/tplink/EAPController/data/db","storageEngine":"wiredTiger"}} {"t":{"$date":"2025-11-04T16:27:10.157-05:00"},"s":"I", "c":"STORAGE", "id":22297, "ctx":"initandlisten","msg":"Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem","tags":["startupWarnings"]} {"t":{"$date":"2025-11-04T16:27:10.157-05:00"},"s":"I", "c":"STORAGE", "id":22315, "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=3584M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,remove=true,path=journal,compressor=snappy),builtin_extension_config=(zstd=(compression_level=6)),file_manager=(close_idle_time=600,close_scan_interval=10,close_handle_minimum=2000),statistics_log=(wait=0),json_output=(error,message),verbose=[recovery_progress:1,checkpoint_progress:1,compact_progress:1,backup:0,checkpoint:0,compact:0,evict:0,history_store:0,recovery:0,rts:0,salvage:0,tiered:0,timestamp:0,transaction:0,verify:0,log:0],prefetch=(available=true,default=false),"}} {"t":{"$date":"2025-11-04T16:27:10.766-05:00"},"s":"W", "c":"STORAGE", "id":22347, "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."} {"t":{"$date":"2025-11-04T16:27:10.766-05:00"},"s":"W", "c":"STORAGE", "id":22349, "ctx":"initandlisten","msg":"Attempting to salvage WiredTiger metadata"} {"t":{"$date":"2025-11-04T16:27:10.801-05:00"},"s":"F", "c":"STORAGE", "id":50947, "ctx":"initandlisten","msg":"Failed to salvage WiredTiger metadata","attr":{"details":"-31802: WT_ERROR: non-specific WiredTiger error"}} {"t":{"$date":"2025-11-04T16:27:10.801-05:00"},"s":"F", "c":"ASSERT", "id":23091, "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":50947,"file":"src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp","line":768}} {"t":{"$date":"2025-11-04T16:27:10.801-05:00"},"s":"F", "c":"ASSERT", "id":23092, "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"} ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:25:57 -05:00
saavagebueno commented 2025-11-20 05:25:58 -05:00
Author
Owner
Copy Link

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

Omada doesnt Work with debian13 and CPUs without avx. So you need Debian 12 or you cant use omada

@MickLesk commented on GitHub (Nov 4, 2025): Omada doesnt Work with debian13 and CPUs without avx. So you need Debian 12 or you cant use omada
saavagebueno commented 2025-11-20 05:25:58 -05:00
Author
Owner
Copy Link

@ampersandru commented on GitHub (Nov 5, 2025):

Im on Promox 8/Debian 12 and my CPU supports AVX2. I also get "Failed to start mongoDB" after updating Omada. Is this because you now need MongoDB8 and because I installed this awhile ago, I may still be on MongoDB3.x and the LXC update script does not upgrade it?

https://github.com/mbentley/docker-omada-controller?tab=readme-ov-file#v5-to-v6-upgrade-guide

@ampersandru commented on GitHub (Nov 5, 2025): Im on Promox 8/Debian 12 and my CPU supports AVX2. I also get "Failed to start mongoDB" after updating Omada. Is this because you now need MongoDB8 and because I installed this awhile ago, I may still be on MongoDB3.x and the LXC update script does not upgrade it? https://github.com/mbentley/docker-omada-controller?tab=readme-ov-file#v5-to-v6-upgrade-guide
saavagebueno commented 2025-11-20 05:25:58 -05:00
Author
Owner
Copy Link

@cfilkins commented on GitHub (Nov 5, 2025):

Yup, from what I saw I believe that my CPUs do support AVX2. I found some other docker references about this as well, and they found that you needed to manually upgrade MongoDB incrementally, as it doesn't support jumping directly up to major versions.

@cfilkins commented on GitHub (Nov 5, 2025): Yup, from what I saw I believe that my CPUs do support AVX2. I found some other docker references about this as well, and they found that you needed to manually upgrade MongoDB incrementally, as it doesn't support jumping directly up to major versions.
saavagebueno commented 2025-11-20 05:25:58 -05:00
Author
Owner
Copy Link

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

@community-scripts/contributor time to remove omada? 30 Issues in less months. Every time another issue

@MickLesk commented on GitHub (Nov 5, 2025): @community-scripts/contributor time to remove omada? 30 Issues in less months. Every time another issue
saavagebueno commented 2025-11-20 05:25:58 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Nov 5, 2025):

Yea, every couple of days there is a issue with their app. https://github.com/community-scripts/ProxmoxVE/issues?q=omada
This is just sad... Fix after fix after fix...

@tremor021 commented on GitHub (Nov 5, 2025): Yea, every couple of days there is a issue with their app. https://github.com/community-scripts/ProxmoxVE/issues?q=omada This is just sad... Fix after fix after fix...
saavagebueno commented 2025-11-20 05:25:59 -05:00
Author
Owner
Copy Link

@cfilkins commented on GitHub (Nov 5, 2025):

I was able to install it in a new lxc without issue...and fwiw I haven't had any issues prior to this one. But this one might be that the update script itself doesn't work. And unfortunately you can't migrate from an older version to a newer version.

Someone with a better grasp of mongod can hopefully chime in and help provide some guidance on doing an incremental upgrade.

@cfilkins commented on GitHub (Nov 5, 2025): I was able to install it in a new lxc without issue...and fwiw I haven't had any issues prior to this one. But this one might be that the update script itself doesn't work. And unfortunately you can't migrate from an older version to a newer version. Someone with a better grasp of mongod can hopefully chime in and help provide some guidance on doing an incremental upgrade.
saavagebueno commented 2025-11-20 05:25:59 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Nov 5, 2025):

When it is buggy like that i say remove it. We have way to many scripts anyway.

@michelroegl-brunner commented on GitHub (Nov 5, 2025): When it is buggy like that i say remove it. We have way to many scripts anyway.
saavagebueno commented 2025-11-20 05:25:59 -05:00
Author
Owner
Copy Link

@ampersandru commented on GitHub (Nov 5, 2025):

backed up config file within omada, spun a new LXC using bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)" , which does install mongoDB 8, restored the config file, readopted omada devices

Everything is up and running again. I tried to update MongoDB manually, but it got stuck at "Migrating MongoDB8 to MongoDB8" - just backing up and restoring was quick and easy.

Not sure if something changed from 5 to 6, but I could not do the regular site migration. But restoring the omada config file restored the site anyways

From my perspective, I have not had any issues at all with the Omada LXC for a couple years now. I haven't read over all the recent bug reports, but Omada did just release Omada 6, which requires a manual mongoDB update even for the docker version, so that will increase a lot of issues coming in because there's no documentation when you attempt to update the Omada LXC - it will attempt to update but fail to run due to mongoDB not updating correctly.

@ampersandru commented on GitHub (Nov 5, 2025): backed up config file within omada, spun a new LXC using `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)"` , which does install mongoDB 8, restored the config file, readopted omada devices Everything is up and running again. I tried to update MongoDB manually, but it got stuck at "Migrating MongoDB8 to MongoDB8" - just backing up and restoring was quick and easy. Not sure if something changed from 5 to 6, but I could not do the regular site migration. But restoring the omada config file restored the site anyways From my perspective, I have not had any issues at all with the Omada LXC for a couple years now. I haven't read over all the recent bug reports, but Omada did just release Omada 6, which requires a [manual mongoDB update even for the docker version](https://github.com/mbentley/docker-omada-controller?tab=readme-ov-file#v5-to-v6-upgrade-guide), so that will increase a lot of issues coming in because there's no documentation when you attempt to update the Omada LXC - it will attempt to update but fail to run due to mongoDB not updating correctly.
saavagebueno commented 2025-11-20 05:25:59 -05:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Nov 5, 2025):

Up to the others if we want to support it further or not.
There are really a lot of issue, but seem to mostly tacke the same things, though I only quickly glanced over them?

Maybe we can add a check to only allow deb12 with avx and refactor to use temurin function now that new tools are merged.
Because it's one of the existing tteck-scripts, I'd say a bit more consideration than any new one, especially as it has nearly 7k installs . Then on further issues remove the app

@CrazyWolf13 commented on GitHub (Nov 5, 2025): Up to the others if we want to support it further or not. There are really a lot of issue, but seem to mostly tacke the same things, though I only quickly glanced over them? Maybe we can add a check to only allow deb12 with avx and refactor to use temurin function now that new tools are merged. Because it's one of the existing tteck-scripts, I'd say a bit more consideration than any new one, especially as it has nearly 7k installs . Then on further issues remove the app
saavagebueno commented 2025-11-20 05:25:59 -05:00
Author
Owner
Copy Link

@Creat commented on GitHub (Nov 6, 2025):

I was about to create my own issue when I found this one, and I think it's related closely enough to be combined.
When logging into my Omada today, I saw it had a new version available so I went to try and upgrade (of course taking a snapshot before). I'm still on Debian 12.9 (according to /etc/debian_version). Trying to run the upgrade script leads to an immediate error:

⠦ Upgrade MongoDB from v3.6 to 8.0
[ERROR] in line 78: exit code 0: while executing command sort -u

I then tried to just update the underlying debian to the latest 12.x, as it turned out it was also quite a bit behind. This included an apparently significant change in meta-information for the "Azul" repo (java stuff I think?), which looked like this:

E: Repository 'https://repos.azul.com/zulu/deb stable InRelease' changed its 'Origin' value from 'Azul Systems' to 'Azul Systems, Inc.'
E: Repository 'https://repos.azul.com/zulu/deb stable InRelease' changed its 'Label' value from '. stable' to 'Azul Systems, Inc., Ubuntu Repository'
N: Repository 'https://repos.azul.com/zulu/deb stable InRelease' changed its 'Version' value from '' to '1.0'
N: Repository 'https://repos.azul.com/zulu/deb stable InRelease' changed its 'Suite' value from 'stable' to 'azulsystems'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Since the server path doesn't include the debian releaes codename, and since it's now tagged to be a "ubuntu" repository, I assume it may be cause of some of the problems. Because if I now just do a full apt dist-upgrade, I also get a non-working omada controller with similar symptoms to those mentioned above. specifically this is my state after doing that, which explicitly doesn't include the actual omada controller itself and is still on debian 12:

root@omada:~# cat /etc/debian_version
12.12

root@omada:~# systemctl status omada.service
* tpeap.service - LSB: Omada Controller
     Loaded: loaded (/etc/init.d/tpeap; generated)
     Active: active (exited) since Thu 2025-11-06 12:56:46 CET; 2min 58s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 159 ExecStart=/etc/init.d/tpeap start (code=exited, status=0/SUCCESS)
        CPU: 36.299s

Nov 06 12:56:14 omada tpeap[159]: Fail to start mongo DB server
Nov 06 12:56:29 omada tpeap[159]: [38B blob data]
Nov 06 12:56:29 omada tpeap[159]: Fail to start mongo DB server
Nov 06 12:56:45 omada tpeap[159]: [38B blob data]
Nov 06 12:56:45 omada tpeap[159]: Fail to start mongo DB server
Nov 06 12:56:46 omada tpeap[159]: .
Nov 06 12:56:46 omada tpeap[159]: Exit Omada Controller.
Nov 06 12:56:46 omada tpeap[159]: .
Nov 06 12:56:46 omada tpeap[159]: Start failed.
Nov 06 12:56:46 omada systemd[1]: Started tpeap.service - LSB: Omada Controller.
@Creat commented on GitHub (Nov 6, 2025): I was about to create my own issue when I found this one, and I think it's related closely enough to be combined. When logging into my Omada today, I saw it had a new version available so I went to try and upgrade (of course taking a snapshot before). I'm still on Debian 12.9 (according to `/etc/debian_version`). Trying to run the upgrade script leads to an immediate error: ```` ⠦ Upgrade MongoDB from v3.6 to 8.0 [ERROR] in line 78: exit code 0: while executing command sort -u ```` I then tried to just update the underlying debian to the latest 12.x, as it turned out it was also quite a bit behind. This included an apparently significant change in meta-information for the "Azul" repo (java stuff I think?), which looked like this: ```` E: Repository 'https://repos.azul.com/zulu/deb stable InRelease' changed its 'Origin' value from 'Azul Systems' to 'Azul Systems, Inc.' E: Repository 'https://repos.azul.com/zulu/deb stable InRelease' changed its 'Label' value from '. stable' to 'Azul Systems, Inc., Ubuntu Repository' N: Repository 'https://repos.azul.com/zulu/deb stable InRelease' changed its 'Version' value from '' to '1.0' N: Repository 'https://repos.azul.com/zulu/deb stable InRelease' changed its 'Suite' value from 'stable' to 'azulsystems' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. ```` Since the server path doesn't include the debian releaes codename, and since it's now tagged to be a "ubuntu" repository, I assume it may be cause of some of the problems. Because if I now just do a full `apt dist-upgrade`, I also get a non-working omada controller with similar symptoms to those mentioned above. specifically this is my state after doing that, which explicitly doesn't include the actual omada controller itself and is still on debian 12: ```` root@omada:~# cat /etc/debian_version 12.12 root@omada:~# systemctl status omada.service * tpeap.service - LSB: Omada Controller Loaded: loaded (/etc/init.d/tpeap; generated) Active: active (exited) since Thu 2025-11-06 12:56:46 CET; 2min 58s ago Docs: man:systemd-sysv-generator(8) Process: 159 ExecStart=/etc/init.d/tpeap start (code=exited, status=0/SUCCESS) CPU: 36.299s Nov 06 12:56:14 omada tpeap[159]: Fail to start mongo DB server Nov 06 12:56:29 omada tpeap[159]: [38B blob data] Nov 06 12:56:29 omada tpeap[159]: Fail to start mongo DB server Nov 06 12:56:45 omada tpeap[159]: [38B blob data] Nov 06 12:56:45 omada tpeap[159]: Fail to start mongo DB server Nov 06 12:56:46 omada tpeap[159]: . Nov 06 12:56:46 omada tpeap[159]: Exit Omada Controller. Nov 06 12:56:46 omada tpeap[159]: . Nov 06 12:56:46 omada tpeap[159]: Start failed. Nov 06 12:56:46 omada systemd[1]: Started tpeap.service - LSB: Omada Controller. ````
saavagebueno commented 2025-11-20 05:25:59 -05:00
Author
Owner
Copy Link

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

3.6? Thats deprecated since 4 or 5 years. The hell? Tbh, Install the Container new. Nobody can upgrade this. That need 5 or 6 seperate Upgrade steps

@MickLesk commented on GitHub (Nov 6, 2025): 3.6? Thats deprecated since 4 or 5 years. The hell? Tbh, Install the Container new. Nobody can upgrade this. That need 5 or 6 seperate Upgrade steps
saavagebueno commented 2025-11-20 05:25:59 -05:00
Author
Owner
Copy Link

@Creat commented on GitHub (Nov 6, 2025):

Please note I do keep the omada controler container updated at lesat somwhat regularly. So the last udapte was a few months ago at the most, probably some time in summer would be my guess? Basically whenever debian 12.9 was the latest release would be a good bet.

As for mongo, I know omada starts it's own instance directly (not using the system services for some reason) and possibly even has it's own binaries (not sure about that), but certainly doesn't use the system mongo db data files. But to the best of my knowledge, this script (thankfully) handles that well, so I don't have to know. Which frankly is the beauty of these scripts for me in the first place.

Also as a side note: the official script page for the omada controller script seems to specify "debian 13", which according to this thread doesn't even work?

@Creat commented on GitHub (Nov 6, 2025): Please note I do keep the omada controler container updated at lesat somwhat regularly. So the last udapte was a few months ago at the most, probably some time in summer would be my guess? Basically whenever debian 12.9 was the latest release would be a good bet. As for mongo, I know omada starts it's own instance directly (not using the system services for some reason) and possibly even has it's own binaries (not sure about that), but certainly doesn't use the system mongo db data files. But to the best of my knowledge, this script (thankfully) handles that well, so I don't have to know. Which frankly is the beauty of these scripts for me in the first place. Also as a side note: the official script page for the omada controller script seems to specify "debian 13", which according to this thread doesn't even work?
saavagebueno commented 2025-11-20 05:26:00 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Nov 6, 2025):

Honestly, i have no clue how you got so behind with updates, but that doesn't matter any more. Your only course of action is to try to manually upgrade everything or just deploy a new up to date container (which you will hopefully keep updated).
There is no point of dragging this discussion

@tremor021 commented on GitHub (Nov 6, 2025): Honestly, i have no clue how you got so behind with updates, but that doesn't matter any more. Your only course of action is to try to manually upgrade everything or just deploy a new up to date container (which you will hopefully keep updated). There is no point of dragging this discussion
saavagebueno commented 2025-11-20 05:26:00 -05:00
Author
Owner
Copy Link

@cfilkins commented on GitHub (Nov 6, 2025):

I wound up just creating an all new container, and tested backing up my
settings and restoring to the new container. Preliminary tests look ok,
but I still need to complete the migration.

With that, my recommendation to anyone else is to just create a new
container and migrate your controller settings over.

On Thu, Nov 6, 2025, 7:47 AM Slaviša Arežina @.***>
wrote:

tremor021 left a comment (community-scripts/ProxmoxVE#8864)
https://github.com/community-scripts/ProxmoxVE/issues/8864#issuecomment-3497106923

Honestly, i have no clue how you got so behind with updates, but that
doesn't matter any more. Your only course of action is to try to manually
upgrade everything or just deploy a new up to date container (which you
will hopefully keep updated).
There is no point of dragging this discussion

—
Reply to this email directly, view it on GitHub
https://github.com/community-scripts/ProxmoxVE/issues/8864#issuecomment-3497106923,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWVUHFVVNGMAH7QHDYQXDL33M7MVAVCNFSM6AAAAACLET75ZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOJXGEYDMOJSGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

@cfilkins commented on GitHub (Nov 6, 2025): I wound up just creating an all new container, and tested backing up my settings and restoring to the new container. Preliminary tests look ok, but I still need to complete the migration. With that, my recommendation to anyone else is to just create a new container and migrate your controller settings over. On Thu, Nov 6, 2025, 7:47 AM Slaviša Arežina ***@***.***> wrote: > *tremor021* left a comment (community-scripts/ProxmoxVE#8864) > <https://github.com/community-scripts/ProxmoxVE/issues/8864#issuecomment-3497106923> > > Honestly, i have no clue how you got so behind with updates, but that > doesn't matter any more. Your only course of action is to try to manually > upgrade everything or just deploy a new up to date container (which you > will hopefully keep updated). > There is no point of dragging this discussion > > — > Reply to this email directly, view it on GitHub > <https://github.com/community-scripts/ProxmoxVE/issues/8864#issuecomment-3497106923>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAWVUHFVVNGMAH7QHDYQXDL33M7MVAVCNFSM6AAAAACLET75ZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOJXGEYDMOJSGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
saavagebueno commented 2025-11-20 05:26:00 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Nov 6, 2025):

Yes because trying to patch this old install up can lead to so many issues, its just not worth it.

@tremor021 commented on GitHub (Nov 6, 2025): Yes because trying to patch this old install up can lead to so many issues, its just not worth it.
saavagebueno commented 2025-11-20 05:26:00 -05:00
Author
Owner
Copy Link

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

backed up config file within omada, spun a new LXC using bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)" , which does install mongoDB 8, restored the config file, readopted omada devices

Thank you for a stress free morning upgrading method to V6. this is the best way to do it for now

@tismofied commented on GitHub (Nov 10, 2025): > backed up config file within omada, spun a new LXC using `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)"` , which does install mongoDB 8, restored the config file, readopted omada devices > Thank you for a stress free morning upgrading method to V6. this is the best way to do it for now
saavagebueno commented 2025-11-20 05:26:00 -05:00
Author
Owner
Copy Link

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

I've recently gone through this process as well, as my LXC container also had MongoDB 3.6.

I used the MongoDB upgrade instructions from TP-Link. I had to upgrade version-by-version.

Upgrade from v3.6 to v4.4

Upgrade from v4.4 to v7

I don't know what these commands are for and what happens if you don't run them, but the upgrade instructions suggest they should be run after every upgrade, db.adminCommand( { setFeatureCompatibilityVersion: "4.4" } ), db.adminCommand( { setFeatureCompatibilityVersion: "7.0", confirm: true } ), etc.

I then upgraded to v8.

@adi1 commented on GitHub (Nov 12, 2025): I've recently gone through this process as well, as my LXC container also had MongoDB 3.6. I used the MongoDB upgrade instructions from TP-Link. I had to upgrade version-by-version. [Upgrade from v3.6 to v4.4](https://support.omadanetworks.com/en/document/24468/) [Upgrade from v4.4 to v7](https://support.omadanetworks.com/en/document/13252/) I don't know what these commands are for and what happens if you don't run them, but the upgrade instructions suggest they should be run after every upgrade, `db.adminCommand( { setFeatureCompatibilityVersion: "4.4" } )`, `db.adminCommand( { setFeatureCompatibilityVersion: "7.0", confirm: true } )`, etc. I then upgraded to v8.
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#2240
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?