Omada Controller - Update Failed #754

@bvdberg01 commented on GitHub (Mar 21, 2025):

@yodaphone
Can you try to start monodb with: systemctl start mongod
and after that have a look at log with: journalctl -u mongod

@bvdberg01 commented on GitHub (Mar 21, 2025): @yodaphone Can you try to start monodb with: ```systemctl start mongod``` and after that have a look at log with: ```journalctl -u mongod```

saavagebueno commented

@yodaphone commented on GitHub (Mar 21, 2025):

@yodaphone Can you try to start monodb with: systemctl start mongod and after that have a look at log with: journalctl -u mongod

Mar 21 21:03:15 omada systemd[1]: Started mongod.service - MongoDB Database Server.
Mar 21 21:03:15 omada mongod[578]: {"t":{"$date":"2025-03-22T01:03:15.096Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOFORK == 1, overriding \"processManagement.fork\" to false"}

@yodaphone commented on GitHub (Mar 21, 2025): > [@yodaphone](https://github.com/yodaphone) Can you try to start monodb with: `systemctl start mongod` and after that have a look at log with: `journalctl -u mongod` ``` Mar 21 21:03:15 omada systemd[1]: Started mongod.service - MongoDB Database Server. Mar 21 21:03:15 omada mongod[578]: {"t":{"$date":"2025-03-22T01:03:15.096Z"},"s":"I", "c":"CONTROL", "id":7484500, "ctx":"main","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOFORK == 1, overriding \"processManagement.fork\" to false"} ```

saavagebueno commented

@bvdberg01 commented on GitHub (Mar 22, 2025):

@yodaphone Can you try to start monodb with: systemctl start mongod and after that have a look at log with: journalctl -u mongod

Mar 21 21:03:15 omada systemd[1]: Started mongod.service - MongoDB Database Server.
Mar 21 21:03:15 omada mongod[578]: {"t":{"$date":"2025-03-22T01:03:15.096Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOFORK == 1, overriding \"processManagement.fork\" to false"}

Ok can you have look at the logging in /opt/tplink/EAPController/logs

@bvdberg01 commented on GitHub (Mar 22, 2025): > > [@yodaphone](https://github.com/yodaphone) Can you try to start monodb with: `systemctl start mongod` and after that have a look at log with: `journalctl -u mongod` > > ``` > Mar 21 21:03:15 omada systemd[1]: Started mongod.service - MongoDB Database Server. > Mar 21 21:03:15 omada mongod[578]: {"t":{"$date":"2025-03-22T01:03:15.096Z"},"s":"I", "c":"CONTROL", "id":7484500, "ctx":"main","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOFORK == 1, overriding \"processManagement.fork\" to false"} > ``` Ok can you have look at the logging in /opt/tplink/EAPController/logs

saavagebueno commented

@yodaphone commented on GitHub (Mar 22, 2025):

@yodaphone Can you try to start monodb with: systemctl start mongod and after that have a look at log with: journalctl -u mongod
Mar 21 21:03:15 omada systemd[1]: Started mongod.service - MongoDB Database Server.
Mar 21 21:03:15 omada mongod[578]: {"t":{"$date":"2025-03-22T01:03:15.096Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOFORK == 1, overriding \"processManagement.fork\" to false"}
Ok can you have look at the logging in /opt/tplink/EAPController/logs

this is what i see. i tried to repaid mongod --repair with no luck.

{"t":{"$date":"2025-03-21T21:08:31.209-04:00"},"s":"I",  "c":"CONTROL",  "id":20698,   "ctx":"main","msg":"***** SERVER RESTARTED *****"}
{"t":{"$date":"2025-03-21T21:08:31.213-04: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-03-21T21:08:31.213-04:00"},"s":"I",  "c":"NETWORK",  "id":4915701, "ctx":"main","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":21},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":21},"outgoing":{"minWireVersion":6,"maxWireVersion":21},"isInternalClient":true}}}
{"t":{"$date":"2025-03-21T21:08:31.214-04:00"},"s":"I",  "c":"NETWORK",  "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize."}
{"t":{"$date":"2025-03-21T21:08:31.216-04:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationDonorService","namespace":"config.tenantMigrationDonors"}}
{"t":{"$date":"2025-03-21T21:08:31.216-04:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationRecipientService","namespace":"config.tenantMigrationRecipients"}}
{"t":{"$date":"2025-03-21T21:08:31.216-04:00"},"s":"I",  "c":"CONTROL",  "id":5945603, "ctx":"main","msg":"Multi threading initialized"}
{"t":{"$date":"2025-03-21T21:08:31.217-04:00"},"s":"I",  "c":"TENANT_M", "id":7091600, "ctx":"main","msg":"Starting TenantMigrationAccessBlockerRegistry"}
{"t":{"$date":"2025-03-21T21:08:31.217-04:00"},"s":"I",  "c":"CONTROL",  "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1725,"port":27217,"dbPath":"../data/db","architecture":"64-bit","host":"omada"}}
{"t":{"$date":"2025-03-21T21:08:31.217-04:00"},"s":"I",  "c":"CONTROL",  "id":23403,   "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"7.0.17","gitVersion":"f099987179b0e9919aa2fcba25afe48f35e53ae9","openSSLVersion":"OpenSSL 3.0.15 3 Sep 2024","modules":[],"allocator":"tcmalloc","environment":{"distmod":"debian12","distarch":"x86_64","target_arch":"x86_64"}}}}
{"t":{"$date":"2025-03-21T21:08:31.217-04: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.8.12-8-pve"}}}
{"t":{"$date":"2025-03-21T21:08:31.217-04:00"},"s":"I",  "c":"CONTROL",  "id":21951,   "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"net":{"bindIp":"127.0.0.1","port":27217},"processManagement":{"pidFilePath":"../data/mongo.pid"},"storage":{"dbPath":"../data/db"},"systemLog":{"destination":"file","logAppend":true,"path":"../logs/mongod.log"}}}}
{"t":{"$date":"2025-03-21T21:08:31.219-04:00"},"s":"F",  "c":"STORAGE",  "id":50922,   "ctx":"initandlisten","msg":"An incomplete repair has been detected! This is likely because a repair operation unexpectedly failed before completing. MongoDB will not start up again without --repair."}
{"t":{"$date":"2025-03-21T21:08:31.219-04:00"},"s":"F",  "c":"ASSERT",   "id":23091,   "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":50922,"file":"src/mongo/db/storage/storage_engine_init.cpp","line":106}}
{"t":{"$date":"2025-03-21T21:08:31.219-04:00"},"s":"F",  "c":"ASSERT",   "id":23092,   "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"}

I just gave up and used a docker instance and migrated the devices away using the backup file. just too much tinkering around.

THank you

@yodaphone commented on GitHub (Mar 22, 2025): > > > [@yodaphone](https://github.com/yodaphone) Can you try to start monodb with: `systemctl start mongod` and after that have a look at log with: `journalctl -u mongod` > > > > > > ``` > > Mar 21 21:03:15 omada systemd[1]: Started mongod.service - MongoDB Database Server. > > Mar 21 21:03:15 omada mongod[578]: {"t":{"$date":"2025-03-22T01:03:15.096Z"},"s":"I", "c":"CONTROL", "id":7484500, "ctx":"main","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOFORK == 1, overriding \"processManagement.fork\" to false"} > > ``` > > Ok can you have look at the logging in /opt/tplink/EAPController/logs this is what i see. i tried to repaid mongod --repair with no luck. ``` {"t":{"$date":"2025-03-21T21:08:31.209-04:00"},"s":"I", "c":"CONTROL", "id":20698, "ctx":"main","msg":"***** SERVER RESTARTED *****"} {"t":{"$date":"2025-03-21T21:08:31.213-04: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-03-21T21:08:31.213-04:00"},"s":"I", "c":"NETWORK", "id":4915701, "ctx":"main","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":21},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":21},"outgoing":{"minWireVersion":6,"maxWireVersion":21},"isInternalClient":true}}} {"t":{"$date":"2025-03-21T21:08:31.214-04:00"},"s":"I", "c":"NETWORK", "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize."} {"t":{"$date":"2025-03-21T21:08:31.216-04:00"},"s":"I", "c":"REPL", "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationDonorService","namespace":"config.tenantMigrationDonors"}} {"t":{"$date":"2025-03-21T21:08:31.216-04:00"},"s":"I", "c":"REPL", "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationRecipientService","namespace":"config.tenantMigrationRecipients"}} {"t":{"$date":"2025-03-21T21:08:31.216-04:00"},"s":"I", "c":"CONTROL", "id":5945603, "ctx":"main","msg":"Multi threading initialized"} {"t":{"$date":"2025-03-21T21:08:31.217-04:00"},"s":"I", "c":"TENANT_M", "id":7091600, "ctx":"main","msg":"Starting TenantMigrationAccessBlockerRegistry"} {"t":{"$date":"2025-03-21T21:08:31.217-04:00"},"s":"I", "c":"CONTROL", "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1725,"port":27217,"dbPath":"../data/db","architecture":"64-bit","host":"omada"}} {"t":{"$date":"2025-03-21T21:08:31.217-04:00"},"s":"I", "c":"CONTROL", "id":23403, "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"7.0.17","gitVersion":"f099987179b0e9919aa2fcba25afe48f35e53ae9","openSSLVersion":"OpenSSL 3.0.15 3 Sep 2024","modules":[],"allocator":"tcmalloc","environment":{"distmod":"debian12","distarch":"x86_64","target_arch":"x86_64"}}}} {"t":{"$date":"2025-03-21T21:08:31.217-04: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.8.12-8-pve"}}} {"t":{"$date":"2025-03-21T21:08:31.217-04:00"},"s":"I", "c":"CONTROL", "id":21951, "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"net":{"bindIp":"127.0.0.1","port":27217},"processManagement":{"pidFilePath":"../data/mongo.pid"},"storage":{"dbPath":"../data/db"},"systemLog":{"destination":"file","logAppend":true,"path":"../logs/mongod.log"}}}} {"t":{"$date":"2025-03-21T21:08:31.219-04:00"},"s":"F", "c":"STORAGE", "id":50922, "ctx":"initandlisten","msg":"An incomplete repair has been detected! This is likely because a repair operation unexpectedly failed before completing. MongoDB will not start up again without --repair."} {"t":{"$date":"2025-03-21T21:08:31.219-04:00"},"s":"F", "c":"ASSERT", "id":23091, "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":50922,"file":"src/mongo/db/storage/storage_engine_init.cpp","line":106}} {"t":{"$date":"2025-03-21T21:08:31.219-04:00"},"s":"F", "c":"ASSERT", "id":23092, "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"} ``` I just gave up and used a docker instance and migrated the devices away using the backup file. just too much tinkering around. THank you

saavagebueno commented

@profblackjack commented on GitHub (Mar 23, 2025):

@tremor021 @yodaphone I recommend reopening this issue, as it's not fixed even if the original reporter chose a different approach

@profblackjack commented on GitHub (Mar 23, 2025): @tremor021 @yodaphone I recommend reopening this issue, as it's not fixed even if the original reporter chose a different approach

saavagebueno commented

@MickLesk commented on GitHub (Mar 23, 2025):

We remove the Script maybe next week completly. We are fighting with there changes every month

@MickLesk commented on GitHub (Mar 23, 2025): We remove the Script maybe next week completly. We are fighting with there changes every month

saavagebueno commented

@gordhawkins commented on GitHub (Apr 14, 2025):

Are you really just abandoning this project? My controller is now not working. I'm totally down.

@gordhawkins commented on GitHub (Apr 14, 2025): Are you really just abandoning this project? My controller is now not working. I'm totally down.

saavagebueno commented

@tremor021 commented on GitHub (Apr 14, 2025):

There is no point in supporting this app any more. They are changing stuff and breaking installs/updates all the time.

@tremor021 commented on GitHub (Apr 14, 2025): There is no point in supporting this app any more. They are changing stuff and breaking installs/updates all the time.

saavagebueno commented

@gordhawkins commented on GitHub (Apr 14, 2025):

There is no point in supporting this app any more. They are changing stuff and breaking installs/updates all the time.

Please delete the package then. It broke my install.

@gordhawkins commented on GitHub (Apr 14, 2025): > There is no point in supporting this app any more. They are changing stuff and breaking installs/updates all the time. Please delete the package then. It broke my install.

saavagebueno commented

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

i dont see any issues on the script. Working fine for me.

@MickLesk commented on GitHub (Apr 14, 2025): i dont see any issues on the script. Working fine for me.

saavagebueno commented

@tremor021 commented on GitHub (Apr 14, 2025):

There is no point in supporting this app any more. They are changing stuff and breaking installs/updates all the time.

Please delete the package then. It broke my install.

Hence why you have snapshots and backups

@tremor021 commented on GitHub (Apr 14, 2025): > > There is no point in supporting this app any more. They are changing stuff and breaking installs/updates all the time. > > Please delete the package then. It broke my install. Hence why you have snapshots and backups

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

well i updated this and it broke and well, i have no backup of my controller that are reachable. how to solve this i wonder ?

@jonas740 commented on GitHub (Apr 14, 2025): well i updated this and it broke and well, i have no backup of my controller that are reachable. how to solve this i wonder ?

saavagebueno commented

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

Manually download File and try again.

@MickLesk commented on GitHub (Apr 14, 2025): Manually download File and try again.

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

Manually download File and try again.

how do you mean ? i am using the lxc container from https://community-scripts.github.io/ProxmoxVE/scripts?id=omada

and i used the update command

i think i have automatic updates enabled but i can not really see where they are saved

@jonas740 commented on GitHub (Apr 14, 2025): > Manually download File and try again. how do you mean ? i am using the lxc container from https://community-scripts.github.io/ProxmoxVE/scripts?id=omada and i used the update command i think i have automatic updates enabled but i can not really see where they are saved

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

`Hit:1 http://security.debian.org bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm 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 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 ... 29559 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.
Unpacking 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].
⠹ Updating Omada Controllercheck 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`

I really really need this to work beacuse i am leaving for vacation tomorrow and all my servers need to be operating as they should.

@jonas740 commented on GitHub (Apr 14, 2025): `Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm 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 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 ... 29559 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. Unpacking 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]. ⠹ Updating Omada Controllercheck 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` I really really need this to work beacuse i am leaving for vacation tomorrow and all my servers need to be operating as they should.

saavagebueno commented

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

What should not work at all? Omada is a very simple deb package. A bit of analysis should already be coming. The systemctl status etc. Which MongoDB. Omada has announced everything under 7.0. It must be 7.0 MongoDB, but this requires AVX. If your processor doesn't have this, you can't use omada either.

@MickLesk commented on GitHub (Apr 14, 2025): What should not work at all? Omada is a very simple deb package. A bit of analysis should already be coming. The systemctl status etc. Which MongoDB. Omada has announced everything under 7.0. It must be 7.0 MongoDB, but this requires AVX. If your processor doesn't have this, you can't use omada either.

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

What should not work at all? Omada is a very simple deb package. A bit of analysis should already be coming. The systemctl status etc. Which MongoDB. Omada has announced everything under 7.0. It must be 7.0 MongoDB, but this requires AVX. If your processor doesn't have this, you can't use omada either.

As said, i have been using this LXC container for very long with no issues. I just performed an update using the command update in the terminal and now it will not start. Why is this?

And remember that i am not the advanced user.

trying to apt install the omada package says it is already the latest

@jonas740 commented on GitHub (Apr 14, 2025): > What should not work at all? Omada is a very simple deb package. A bit of analysis should already be coming. The systemctl status etc. Which MongoDB. Omada has announced everything under 7.0. It must be 7.0 MongoDB, but this requires AVX. If your processor doesn't have this, you can't use omada either. As said, i have been using this LXC container for very long with no issues. I just performed an update using the command update in the terminal and now it will not start. Why is this? And remember that i am not the advanced user. trying to apt install the omada package says it is already the latest

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

And i am running AMD Ryzen 7 5800H that do support AVX

@jonas740 commented on GitHub (Apr 14, 2025): And i am running AMD Ryzen 7 5800H that do support AVX

saavagebueno commented

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

systemctl status omada
Systemctl status mongodb

@MickLesk commented on GitHub (Apr 14, 2025): systemctl status omada Systemctl status mongodb

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

`root@omada:/# systemctl status omada
● tpeap.service - LSB: Omada Controller
Loaded: loaded (/etc/init.d/tpeap; generated)
Active: active (exited) since Mon 2025-04-14 21:40:17 CEST; 40min ago
Docs: man:systemd-sysv-generator(8)
CPU: 36.512s

Apr 14 21:39:43 omada tpeap[156]: Fail to start mongo DB server
Apr 14 21:39:59 omada tpeap[156]: [38B blob data]
Apr 14 21:39:59 omada tpeap[156]: Fail to start mongo DB server
Apr 14 21:40:13 omada tpeap[156]: [37B blob data]
Apr 14 21:40:13 omada tpeap[156]: Fail to start mongo DB server
Apr 14 21:40:17 omada tpeap[156]: ....
Apr 14 21:40:17 omada tpeap[156]: Exit Omada Controller.
Apr 14 21:40:17 omada tpeap[156]: .
Apr 14 21:40:17 omada tpeap[156]: Start failed.
Apr 14 21:40:17 omada systemd[1]: Started tpeap.service - LSB: Omada Controller.`

root@omada:/# systemctl status mongodb Unit mongodb.service could not be found.

@jonas740 commented on GitHub (Apr 14, 2025): `root@omada:/# systemctl status omada ● tpeap.service - LSB: Omada Controller Loaded: loaded (/etc/init.d/tpeap; generated) Active: active (exited) since Mon 2025-04-14 21:40:17 CEST; 40min ago Docs: man:systemd-sysv-generator(8) CPU: 36.512s Apr 14 21:39:43 omada tpeap[156]: Fail to start mongo DB server Apr 14 21:39:59 omada tpeap[156]: [38B blob data] Apr 14 21:39:59 omada tpeap[156]: Fail to start mongo DB server Apr 14 21:40:13 omada tpeap[156]: [37B blob data] Apr 14 21:40:13 omada tpeap[156]: Fail to start mongo DB server Apr 14 21:40:17 omada tpeap[156]: .... Apr 14 21:40:17 omada tpeap[156]: Exit Omada Controller. Apr 14 21:40:17 omada tpeap[156]: . Apr 14 21:40:17 omada tpeap[156]: Start failed. Apr 14 21:40:17 omada systemd[1]: Started tpeap.service - LSB: Omada Controller.` `root@omada:/# systemctl status mongodb Unit mongodb.service could not be found.`

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

i do think you mean systemctl status mongod

root@omada:/# systemctl status mongod ○ mongod.service - MongoDB Database Server Loaded: loaded (/lib/systemd/system/mongod.service; disabled; preset: enabled) Active: inactive (dead) Docs: https://docs.mongodb.org/manual

@jonas740 commented on GitHub (Apr 14, 2025): i do think you mean systemctl status mongod `root@omada:/# systemctl status mongod ○ mongod.service - MongoDB Database Server Loaded: loaded (/lib/systemd/system/mongod.service; disabled; preset: enabled) Active: inactive (dead) Docs: https://docs.mongodb.org/manual`

saavagebueno commented

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

Your MongoDB is dead. Try an systemctl start or enable mongod If this not Work, reinstall mongodb

@MickLesk commented on GitHub (Apr 14, 2025): Your MongoDB is dead. Try an systemctl start or enable mongod If this not Work, reinstall mongodb

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

`root@omada:/# systemctl status mongod
● mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; disabled; preset: enabled)
Active: active (running) since Mon 2025-04-14 22:33:54 CEST; 9s ago
Docs: https://docs.mongodb.org/manual
Main PID: 5510 (mongod)
Memory: 175.4M
CPU: 414ms
CGroup: /system.slice/mongod.service
└─5510 /usr/bin/mongod --config /etc/mongod.conf

Apr 14 22:33:54 omada systemd[1]: Started mongod.service - MongoDB Database Server.
Apr 14 22:33:54 omada mongod[5510]: {"t":{"$date":"2025-04-14T20:33:54.166Z"},"s":"I", "c":"CONTROL", "id":7484500, "ctx":"main","msg":"Environment >
lines 1-12/12 (END)`

well when rebooting this lxc container it will possibly not start mongodb. it looks like it is disabled ? what command to enable ? and how do i start omada ?

please get back with command to reinstall mongodb aswell

@jonas740 commented on GitHub (Apr 14, 2025): `root@omada:/# systemctl status mongod ● mongod.service - MongoDB Database Server Loaded: loaded (/lib/systemd/system/mongod.service; disabled; preset: enabled) Active: active (running) since Mon 2025-04-14 22:33:54 CEST; 9s ago Docs: https://docs.mongodb.org/manual Main PID: 5510 (mongod) Memory: 175.4M CPU: 414ms CGroup: /system.slice/mongod.service └─5510 /usr/bin/mongod --config /etc/mongod.conf Apr 14 22:33:54 omada systemd[1]: Started mongod.service - MongoDB Database Server. Apr 14 22:33:54 omada mongod[5510]: {"t":{"$date":"2025-04-14T20:33:54.166Z"},"s":"I", "c":"CONTROL", "id":7484500, "ctx":"main","msg":"Environment > lines 1-12/12 (END)` well when rebooting this lxc container it will possibly not start mongodb. it looks like it is disabled ? what command to enable ? and how do i start omada ? please get back with command to reinstall mongodb aswell

saavagebueno commented

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

Dude... Im not an microsoft support 😄 There should be a little bit of cooperation. Otherwise you are simply wrong in the whole Linux area. Have a look at the install script of omada and do the steps manually for mongo, or Google for "mongodb 7.0 install debian" I can't make any remote diagnoses here, I can only give you an indication of what you need to fix.

@MickLesk commented on GitHub (Apr 14, 2025): Dude... Im not an microsoft support :smile: There should be a little bit of cooperation. Otherwise you are simply wrong in the whole Linux area. Have a look at the install script of omada and do the steps manually for mongo, or Google for "mongodb 7.0 install debian" I can't make any remote diagnoses here, I can only give you an indication of what you need to fix.

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

Haha, ye i know but i have not had theese issues with omada lxc container before and am panicing since i am travelling abroad.

The mongodb is active, i ran the update command again but it says mongodb fail to start.

is there any backup configs in this lxc container so i can just set up a new one ? i do not want to loose all my settings but i need to fix this asap

@jonas740 commented on GitHub (Apr 14, 2025): Haha, ye i know but i have not had theese issues with omada lxc container before and am panicing since i am travelling abroad. The mongodb is active, i ran the update command again but it says mongodb fail to start. is there any backup configs in this lxc container so i can just set up a new one ? i do not want to loose all my settings but i need to fix this asap

saavagebueno commented

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

Does an new Install work? MongoDB failed only with wrong cpus

@MickLesk commented on GitHub (Apr 14, 2025): Does an new Install work? MongoDB failed only with wrong cpus

saavagebueno commented

@jonas740 commented on GitHub (Apr 14, 2025):

` ✔️ Updated MongoDB to 7.0
✔️ Azul Zulu Java 21 already installed
✔️ Updated Omada Controller
/dev/fd/63: line 1289: CT_TYPE: unbound variable
root@omada:/# systemctl status omada
● tpeap.service - LSB: Omada Controller
Loaded: loaded (/etc/init.d/tpeap; generated)
Active: active (exited) since Mon 2025-04-14 21:40:17 CEST; 1h 10min ago
Docs: man:systemd-sysv-generator(8)
CPU: 36.512s

Apr 14 21:39:43 omada tpeap[156]: Fail to start mongo DB server
Apr 14 21:39:59 omada tpeap[156]: [38B blob data]
Apr 14 21:39:59 omada tpeap[156]: Fail to start mongo DB server
Apr 14 21:40:13 omada tpeap[156]: [37B blob data]
Apr 14 21:40:13 omada tpeap[156]: Fail to start mongo DB server
Apr 14 21:40:17 omada tpeap[156]: ....
Apr 14 21:40:17 omada tpeap[156]: Exit Omada Controller.
Apr 14 21:40:17 omada tpeap[156]: .
Apr 14 21:40:17 omada tpeap[156]: Start failed.
Apr 14 21:40:17 omada systemd[1]: Started tpeap.service - LSB: Omada Controller.
root@omada:/# systemctl status mongod
● mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; disabled; preset: enabled)
Active: active (running) since Mon 2025-04-14 22:33:54 CEST; 16min ago
Docs: https://docs.mongodb.org/manual
Main PID: 5510 (mongod)
Memory: 174.6M
CPU: 4.896s
CGroup: /system.slice/mongod.service
└─5510 /usr/bin/mongod --config /etc/mongod.conf

Apr 14 22:33:54 omada systemd[1]: Started mongod.service - MongoDB Database Server.
Apr 14 22:33:54 omada mongod[5510]: {"t":{"$date":"2025-04-14T20:33:54.166Z"},"s":"I", "c":"CONTROL", "id":7484500, "ctx":"main","msg":"Environment >
lines 1-12/12 (END)`

this is what i got after reinstalling mongodb and after that i ran the update command again.

In the script it will warn and exit if your cpu does not have AVX btw.

New install works perfect.

But i need my settings

@jonas740 commented on GitHub (Apr 14, 2025): ` ✔️ Updated MongoDB to 7.0 ✔️ Azul Zulu Java 21 already installed ✔️ Updated Omada Controller /dev/fd/63: line 1289: CT_TYPE: unbound variable root@omada:/# systemctl status omada ● tpeap.service - LSB: Omada Controller Loaded: loaded (/etc/init.d/tpeap; generated) Active: active (exited) since Mon 2025-04-14 21:40:17 CEST; 1h 10min ago Docs: man:systemd-sysv-generator(8) CPU: 36.512s Apr 14 21:39:43 omada tpeap[156]: Fail to start mongo DB server Apr 14 21:39:59 omada tpeap[156]: [38B blob data] Apr 14 21:39:59 omada tpeap[156]: Fail to start mongo DB server Apr 14 21:40:13 omada tpeap[156]: [37B blob data] Apr 14 21:40:13 omada tpeap[156]: Fail to start mongo DB server Apr 14 21:40:17 omada tpeap[156]: .... Apr 14 21:40:17 omada tpeap[156]: Exit Omada Controller. Apr 14 21:40:17 omada tpeap[156]: . Apr 14 21:40:17 omada tpeap[156]: Start failed. Apr 14 21:40:17 omada systemd[1]: Started tpeap.service - LSB: Omada Controller. root@omada:/# systemctl status mongod ● mongod.service - MongoDB Database Server Loaded: loaded (/lib/systemd/system/mongod.service; disabled; preset: enabled) Active: active (running) since Mon 2025-04-14 22:33:54 CEST; 16min ago Docs: https://docs.mongodb.org/manual Main PID: 5510 (mongod) Memory: 174.6M CPU: 4.896s CGroup: /system.slice/mongod.service └─5510 /usr/bin/mongod --config /etc/mongod.conf Apr 14 22:33:54 omada systemd[1]: Started mongod.service - MongoDB Database Server. Apr 14 22:33:54 omada mongod[5510]: {"t":{"$date":"2025-04-14T20:33:54.166Z"},"s":"I", "c":"CONTROL", "id":7484500, "ctx":"main","msg":"Environment > lines 1-12/12 (END)` this is what i got after reinstalling mongodb and after that i ran the update command again. In the script it will warn and exit if your cpu does not have AVX btw. New install works perfect. But i need my settings

saavagebueno commented

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

apt-get purge mongodb-org
curl -fsSL "https://www.mongodb.org/static/pgp/server-7.0.asc" | gpg --dearmor >/usr/share/keyrings/mongodb-server-7.0.gpg
  echo "deb [signed-by=/usr/share/keyrings/mongodb-server-7.0.gpg] http://repo.mongodb.org/apt/debian $(grep '^VERSION_CODENAME=' /etc/os-release | cut -d'=' -f2)/mongodb-org/7.0 main" >/etc/apt/sources.list.d/mongodb-org-7.0.list
 apt-get update
 apt-get install -y  mongodb-org

@MickLesk commented on GitHub (Apr 14, 2025): ```bash apt-get purge mongodb-org curl -fsSL "https://www.mongodb.org/static/pgp/server-7.0.asc" | gpg --dearmor >/usr/share/keyrings/mongodb-server-7.0.gpg echo "deb [signed-by=/usr/share/keyrings/mongodb-server-7.0.gpg] http://repo.mongodb.org/apt/debian $(grep '^VERSION_CODENAME=' /etc/os-release | cut -d'=' -f2)/mongodb-org/7.0 main" >/etc/apt/sources.list.d/mongodb-org-7.0.list apt-get update apt-get install -y mongodb-org ```

saavagebueno commented

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

That's all I can do. Otherwise write to omada support and ask them for a solution. End.

@MickLesk commented on GitHub (Apr 14, 2025): That's all I can do. Otherwise write to omada support and ask them for a solution. End.

saavagebueno commented