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 13 Packages Projects Releases 10 Wiki Activity

Omada update problem #855

New Issue
Closed
opened 2026-02-04 21:55:36 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 21:55:36 +03:00
Owner
Copy Link

Originally created by @jeffreydoorn on GitHub (Apr 25, 2025).

Same problem for me. The weird thing is after restoring the vm from yesterday backups it also won't start. Maybe someone else any solution for this problem?..

Update Link: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)"%22)

/ __ ____ ___ ____ / / _
/ / / / __ __ \/ __ / __ / __ `/
/ // / / / / / / // / // / // /
_// // //_,/_,/_,/

Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 https://repos.azul.com/zulu/deb stable InRelease
Hit:5 http://repo.mongodb.org/apt/debian bookworm/mongodb-org/7.0 InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Skipping mongodb-org, it is not installed and only upgrades are requested.
⠼ Updating MongoDBThe following packages were automatically installed and are no longer required:
libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 libxi6 libxrender1 libxtst6 x11-common zulu8-ca-doc zulu8-ca-jdk zulu8-ca-jdk-headless zulu8-ca-jre zulu8-doc
zulu8-jdk-headless zulu8-jre zulu8-jre-headless
Use 'apt autoremove' to remove them.
⠴ Updating MongoDB0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
✔️ Updated MongoDB to 7.0
✔️ Azul Zulu Java 21 already installed
(Reading database ... 23300 files and directories currently installed.)
Preparing to unpack Omada_SDN_Controller_v5.15.20.18_linux_x64.deb ...
⠦ Updating Omada ControllerA previous controller version has been detected.
⠧ Updating Omada ControllerUnpacking omadac (5.15.20.18) over (5.15.20.18) ...
⠙ Updating Omada ControllerSetting up omadac (5.15.20.18) ...
⠼ Updating Omada ControllerInstall Omada Controller succeeded!

data dir is not empty.
current data is not empty
Omada Controller will start up with system boot. You can also control it by [/usr/bin/tpeap].
check omada
Starting Omada Controller. Please wait.
⠼ Updating Omada Controller.

Fail to start mongo DB server
Fail to start mongo DB server
⠼ Updating Omada Controller.
Fail to start mongo DB server
⠼ Updating Omada Controller.
Fail to start mongo DB server
⠼ Updating Omada Controller.
Fail to start mongo DB server
⠼ Updating Omada Controller.
Exit Omada Controller.
.
Start failed.

✔️ Updated Omada Controller
/dev/fd/63: line 1289: CT_TYPE: unbound variable

Originally posted by @jeffreydoorn in #3321

Originally created by @jeffreydoorn on GitHub (Apr 25, 2025). > Same problem for me. The weird thing is after restoring the vm from yesterday backups it also won't start. Maybe someone else any solution for this problem?.. > > Update Link: bash -c "$(curl -fsSL [https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)"](https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)%22) > ____ __ > / __ \____ ___ ____ _____/ /___ _ > / / / / __ `__ \/ __ `/ __ / __ `/ > / /_/ / / / / / / /_/ / /_/ / /_/ / > \____/_/ /_/ /_/\__,_/\__,_/\__,_/ > > > Hit:1 http://deb.debian.org/debian bookworm InRelease > Hit:2 http://security.debian.org bookworm-security InRelease > Hit:3 http://deb.debian.org/debian bookworm-updates InRelease > Hit:4 https://repos.azul.com/zulu/deb stable InRelease > Hit:5 http://repo.mongodb.org/apt/debian bookworm/mongodb-org/7.0 InRelease > Reading package lists... Done > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Skipping mongodb-org, it is not installed and only upgrades are requested. > ⠼ Updating MongoDBThe following packages were automatically installed and are no longer required: > libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 libxi6 libxrender1 libxtst6 x11-common zulu8-ca-doc zulu8-ca-jdk zulu8-ca-jdk-headless zulu8-ca-jre zulu8-doc > zulu8-jdk-headless zulu8-jre zulu8-jre-headless > Use 'apt autoremove' to remove them. > ⠴ Updating MongoDB0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > ✔️ Updated MongoDB to 7.0 > ✔️ Azul Zulu Java 21 already installed > (Reading database ... 23300 files and directories currently installed.) > Preparing to unpack Omada_SDN_Controller_v5.15.20.18_linux_x64.deb ... > ⠦ Updating Omada ControllerA previous controller version has been detected. > ⠧ Updating Omada ControllerUnpacking omadac (5.15.20.18) over (5.15.20.18) ... > ⠙ Updating Omada ControllerSetting up omadac (5.15.20.18) ... > ⠼ Updating Omada ControllerInstall Omada Controller succeeded! > ========================== > data dir is not empty. > current data is not empty > Omada Controller will start up with system boot. You can also control it by [/usr/bin/tpeap]. > check omada > Starting Omada Controller. Please wait. > ⠼ Updating Omada Controller. > > Fail to start mongo DB server > Fail to start mongo DB server > ⠼ Updating Omada Controller. > Fail to start mongo DB server > ⠼ Updating Omada Controller. > Fail to start mongo DB server > ⠼ Updating Omada Controller. > Fail to start mongo DB server > ⠼ Updating Omada Controller. > Exit Omada Controller. > . > Start failed. > ======================== > ✔️ Updated Omada Controller > /dev/fd/63: line 1289: CT_TYPE: unbound variable > > _Originally posted by @jeffreydoorn in [#3321](https://github.com/community-scripts/ProxmoxVE/issues/3321#issuecomment-2830582509)_
OVERLORD commented 2026-02-04 21:55:52 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 25, 2025):

Report this to omada. Not an Script issue

@MickLesk commented on GitHub (Apr 25, 2025): Report this to omada. Not an Script issue
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
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#855
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?