[Help]: Upgrade to V6 - MongoDB V8

[randomguy1991]

Controller Version

V6

Describe Your Issue or Question

Currently we are required to upgrade the MongoDB to V8, however some CPU is not eligible for AVX thus unable to upgrade. Is there a way to have a MongoDB V4 version released to ensure those who can't upgrade to V8 can still run the latest version of Omada.

Expected Behavior

Error message:

INFO: running hardware prerequesite checks to ensure your system supports MongoDB 8...ERROR: your system does not support AVX which is a requirement for MongoDB starting with 5.x; you will not be able to upgrade

Steps to Reproduce

Ran the following:

docker run -it --rm
-v omada-data:/opt/tplink/EAPController/data
mbentley/omada-controller:mongodb-upgrade-3.6-to-8

How You're Launching the Container

-

Container Logs

-

MongoDB Logs

-

Additional Context

No response

[mbentley]

Well, I wasn't sure if someone would run into the AVX or armv8.2-a support requirement so quickly but now that we're here, I do have addressing what to do for those scenarios that block the MongoDB upgrade in #443 in the work list.

That being said, there are a few difficult things about supporting an image that has MongoDB 4.x. That version only supports as recent as Ubuntu 20.04 which is end of life and receives no more updates, which is why the MongoDB upgrade is required in the first place. The solution that I was going to propose for people who can't upgrade but still want to run the latest versions is to switch to an external MongoDB. I need to revamp those instructions there as they're quite out of date and I still need to ensure that an external MongoDB works on 6.x as well.

[mbentley]

Just FYI, I did just update the README for the external MongoDB to have some slightly more detailed instructions and I did verify that v6 does work with external MongoDB.

[dawibe]

I have the same issue on Synology DS720+

INFO: running hardware prerequesite checks to ensure your system supports MongoDB 8... ERROR: your system does not support AVX which is a requirement for MongoDB starting with 5.x; you will not be able to upgrade MongoDB

[pustekuchen91]

Same here. Have an Synology from 2016.

I'm running portainer with docker compose. it should be no big problem to run MongoDB 4.x in the same stack? Something i should pay attention to?

[mbentley]

Well if you've been running the 5.x images, it's actually MongoDB 3.x that's inside otherwise you would need to migrate to 4.x to use that. You could follow these instructions to run MongoDB externally: https://github.com/mbentley/docker-omada-controller/blob/master/external_mongodb/README.md#migration-from-all-in-one

[pustekuchen91]

Omada 6 is running on my NAS (with portainer) without AVX Support now.

This is my final docker compose, but before some steps had to be done!

services:
  mongodb:
    image: mongo:4
    container_name: omada-mongodb
    user: "508:508"     
    volumes:
      - /volume1/docker/omada/data/db:/data/db
    restart: always
    command: ["mongod",
              "--dbpath","/data/db",
              "--bind_ip_all",
              "--port","27017"]
    healthcheck:
      test: ["CMD", "mongo", "--host", "localhost", "--port", "27017", "--eval", "db.adminCommand('ping')"]
      interval: 20s
      timeout: 15s
      retries: 5
    ports: 
      - 27017:27017
      
  omada-controller:
    container_name: omada-controller
    image: mbentley/omada-controller:6
    restart: unless-stopped
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    environment:
      - PUID=508
      - PGID=508
      - MANAGE_HTTP_PORT=8088
      - MANAGE_HTTPS_PORT=8043
      - PORTAL_HTTP_PORT=8088
      - PORTAL_HTTPS_PORT=8843
      - PORT_APP_DISCOVERY=27001
      - PORT_ADOPT_V1=29812
      - PORT_UPGRADE_V1=29813
      - PORT_MANAGER_V1=29811
      - PORT_MANAGER_V2=29814
      - PORT_DISCOVERY=29810
      - PORT_TRANSFER_V2=29815
      - PORT_RTTY=29816
      - SHOW_SERVER_LOGS=true
      - SHOW_MONGODB_LOGS=false
      - SSL_CERT_NAME=tls.crt
      - SSL_KEY_NAME=tls.key
      - TZ=Europe/Berlin
      - MONGO_EXTERNAL=true
      - EAP_MONGOD_URI=mongodb://mongodb:27017/omada
    volumes:
      - /volume1/docker/omada/data:/opt/tplink/EAPController/data
      - /volume1/docker/omada/logs:/opt/tplink/EAPController/logs
    depends_on:
      mongodb:
        condition: service_healthy
    ports:
      - 8043:8043
      - 8088:8088
      - 8843:8843
      - 19810:19810/udp
      - 27001:27001/udp
      - 29810:29810/udp 
      - 29811-29817:29811-29817

1. Backup
   1.1 if you need to restore the backup, keep in mind that the files need the correct owner of the data folder. if you need to -> sudo chown -R 508:508 data
2. Upgrade MongoDB
   2.1 Hint: You need to restart the mongodb container multiple times, so disable the omada service for that first.
   2.2 Hint: the old database is located in the data/db folder.
   2.3 start the mongodb service with image: mongo:4.0
   2.4 connect to shell of the container and execute mongo --host 127.0.0.1 --port 27017
   2.5 in mongo shell execute db.adminCommand({ setFeatureCompatibilityVersion: "4.0" })
   2.6 now increase the image to 4.2 and restart the container, connecto to the mongo shell and execute db.adminCommand({ setFeatureCompatibilityVersion: "4.2" })
   2.7 and finally use the ìmage: mongo:4 and execute db.adminCommand({ setFeatureCompatibilityVersion: "4.4" }) in the mongo shell
3. Reenable the omada service and be happy :)

[IDZ-GH]

Thanks for the impressive work. The DS1520+ is working.

[veN1337]

Did anyone try a MongoDB docker image without the AVX requirement or tried to compile without AVX from source?

[mbentley]

I've only seen that done for like version 5.x and not really carried further but I didn't look at it that hard myself.

[dawibe]

Is there a list available which CPUs support that AVX? I have just systems running with Celeron J4125 (including the Synology DS 720+) but I need to upgrade the Omada Software which is a requirement to use the new Firmware for my Switch. I am currently a bit lost with that topic and just wonder if it makes sense to buy a new device just for the Omada Controller but for that I need to know which device is supporting that. That's a bit frustrating.

[mbentley]

If you're looking at another Intel based CPU, search for the SKU specifications page for the processor such as: https://www.intel.com/content/www/us/en/products/sku/231803/intel-processor-n100-6m-cache-up-to-3-40-ghz/specifications.html It will list the instruction sets supported which it will call out AVX.

You can search AMD's info at https://www.amd.com/en/products/specifications/processors.html

[mbentley]

You could run an external MongoDB as well on your system without AVX if you want to go that route.

[GoodOmens83]

Is there a list available which CPUs support that AVX? I have just systems running with Celeron J4125 (including the Synology DS 720+) but I need to upgrade the Omada Software which is a requirement to use the new Firmware for my Switch. I am currently a bit lost with that topic and just wonder if it makes sense to buy a new device just for the Omada Controller but for that I need to know which device is supporting that. That's a bit frustrating.

The Celeron J4125 does not support AVX. Alternative would be to upgrade to the DS723+/DS725+ or offload/migrate the docker/controller onto a different device, like a rasberry pi. I think the PI 5 is the only PI that supports MongoDB5+ per @mbentley response below.

[mbentley]

...and then for arm based devices, you need something that is at least armv8.2-a. Pretty sure that limits you to a rpi5.

[mikepell007]

@mbentley Just did the upgrade to 6 and Mongo 8. Followed the excellent docs and all went smoothly. Great job by you and all the testers!