[Help]: OC200 > Docker Controller, No Devices

[BillyBobMills]

Controller Version

v5.12.7

Describe Your Issue or Question

Hi, I'm looking for a bit of clarification if possible please?

I have been running an OC200 for a little over a year and I am looking to migrate to a Docker Software Instance.

I'm running a small Proxmox install with a Ubuntu 20.04 VM + Portainer with various containers already running on this VM.

Having set up the new controller container using the below docker compose via a stack in Portainer I can log into the new controller, skip the initial setup, just creating the account, getting to the main dashboard all ok.

What I am stuck on is:
Is the new controller supposed to be able to see the existing devices even though they are already adopted by the OC200?
It cannot see anything which I think is wrong.

I have now done a successful site backup and restore to the new container controller and the devices are listed but 'Disconnected' status.

I do not want to try the next step Migrating the Devices if the new controller cannot see them already.

Other Info:

The VM and the hardware devices are all on the same VLAN.

The Ubuntu 20.04 VM can ping the devices.

Originally the OC200 was on 5.7.4 and a backup could not be restored into a 5.7.6, 5.8 or 5.12 new container controller.
I have updated the OC200 to 5.12.9 and a site backup via migration has successfully been restored into the new container controller. The devices all show but with a 'Disconnected' status.

Expected Behavior

NA

Steps to Reproduce

NA

How You're Launching the Container

version: "3.1"

services:
  omada-controller:
    container_name: omada-controller
    image: mbentley/omada-controller:latest
    restart: unless-stopped
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    network_mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - 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=Etc/UTC
    volumes:
      - /home/user/config/omada/data:/opt/tplink/EAPController/data
      - /home/user/config/omada/logs:/opt/tplink/EAPController/logs

Container Logs

NA

MongoDB Logs

No response

Additional Context

No response

[mbentley]

Are you shutting down the OC200 before you restore your config to the software controller in a container? I imagine what is going on is that the existing controller is still owning those devices so the restore still shows them as disconnected. You should be fine to power off your OC200 and it shouldn't lose any configuration. It may have to re-adopt the devices but that's not a big deal (or shouldn't be).

[BillyBobMills]

I have not tried shutting down the OC200 yet. Searching there is some conflicting info that suggests that more than one controller should be able to live on the same network.

Ill try it next though thanks.

I've just created a new Ubuntu VM with a new a new docker + Portainer install just to remove any other container conflicting issue.

Same on the new VM. Not trying any restore it shows as 'No devices found'.

[mbentley]

Live on the same network - yes. Control the same devices? No.

[BillyBobMills]

After turning off the OC200 and starting the Container the devices all started to auto connect and be adopted by the new container. (I had not clicked migrate devices so didn't expect them to automatically be connected to the new container controller)

The Issue with this is it seems to have not restored any Client Usernames. (I had done a site migration)

So I have reset everything back to the OC200 and stared again with a new container and OC200 controller migration.

As originally I can not get any container backup to restore to the software controller.

Checking the logs I have this error.

Is this container related?

11-28-2023 13:57:55.992 ERROR [restore-work-group-0] [] c.t.s.o.b.c.r.c(): omadacId=OmadacId(XXX) restore failed with Exception
java.lang.reflect.InaccessibleObjectException: Unable to make field private static final long java.util.LinkedHashMap.serialVersionUID accessible: module java.base does not "opens java.util" to unnamed module @5c130274
at java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354) ~[?:?]
at java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297) ~[?:?]
at java.lang.reflect.Field.checkCanSetAccessible(Field.java:178) ~[?:?]
at java.lang.reflect.Field.setAccessible(Field.java:172) ~[?:?]
at com.tplink.smb.omada.backup.api.f.c.a(SourceFile:27) ~[backup-api-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.api.f.b.a(SourceFile:54) ~[backup-api-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.core.unit.a.a.a(SourceFile:31) ~[backup-core-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.core.restore.c.a(SourceFile:606) ~[backup-core-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.core.restore.c.a(SourceFile:538) ~[backup-core-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.core.restore.c.a(SourceFile:181) ~[backup-core-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.core.restore.j.a(SourceFile:124) ~[backup-core-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.core.restore.j.a(SourceFile:65) ~[backup-core-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.core.a.a.a(SourceFile:100) ~[backup-core-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.a.b.a.a.f.b(SourceFile:230) ~[maintenance-port-web-5.12.7.jar:5.12.7]
at com.tplink.smb.component.lock.api.AbstractReadWriteLockService.doWithTryLockWrite(AbstractReadWriteLockService.java:107) ~[solution-components-lock-api-1.1.4.jar:1.1.4]
at com.tplink.smb.omada.lock.a.a.b(SourceFile:77) ~[omada-lock-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.lock.a.a.b(SourceFile:92) ~[omada-lock-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.a.b.a.a.f.a(SourceFile:227) ~[maintenance-port-web-5.12.7.jar:5.12.7]
at com.tplink.smb.omada.backup.a.b.a.a.f.a(SourceFile:161) ~[maintenance-port-web-5.12.7.jar:5.12.7]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) [?:?]
11-28-2023 13:57:55.995 INFO [restore-work-group-0] [] c.t.s.o.b.c.r.b.a(): omadacId=XXX restore failed

[mbentley]

No, looks like that's something with the controller software.

[BillyBobMills]

Thanks ill try on the tplink community

[BillyBobMills]

Shutting down the original controller made the devices connect in the new controller