-
Controller Versionv.5.15.24.19 Describe Your Issue or QuestionHello. I'm new here, so please bear with me... Everything seems to be configured correctly, but the controller restarts automatically after a few/several minutes. I should add that this is a test installation - I'd like to eventually get rid of OC200 and stick with Docker, but I have no idea why it's so unstable in my case 😞 Expected BehaviorStable work without self restarting Steps to Reproduce
How You're Launching the ContainerContainer LogsMongoDB LogsNo response Additional ContextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 12 replies
-
|
That's not the container restarting, that looks like the cloud connection resetting. You would see the container's uptime show this if the container restarted: You can see here that this container's been running for 3 hours so it hasn't been restarting. You would also see the container's entrypoint startup messages in the logs if it restarted. Are you seeing any behavior of the controller where it's failing in some way? If not, it's likely fine but you should probably check to see if the cloud connection is working, if you use that. |
Beta Was this translation helpful? Give feedback.
-
|
Hmmm... it's hard for me to answer your question - however, I remember a situation where my physical OC200 controller behaved similarly strangely (self-restarts) for about 2 weeks with the previous software version (I don't remember exactly, but it was probably 5.15.24.18???) - with the current 5.15.24.21 it's fine now. |
Beta Was this translation helpful? Give feedback.
-
|
I'll keep watching. Thank you for your reply. |
Beta Was this translation helpful? Give feedback.
-
|
Oh and one other thing - don't use the |
Beta Was this translation helpful? Give feedback.
-
|
Hello Matt, I'm reaching out for help. I'd like to migrate my controller to the container you created – my OC200 is acting unpredictably, and I have a spare, unused thin client. I created a build based on your .yaml file, but I don't quite understand the container logs. Could you take a look when you have a moment to see if I compiled it correctly? services:
omada-controller:
container_name: omada-controller
image: mbentley/omada-controller:5.15
restart: always
ulimits:
nofile:
soft: 4096
hard: 8192
stop_grace_period: 60s
networks:
macvlan1:
ipv4_address: 10.77.10.201
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_DISCOVERY=29810
- PORT_MANAGER_V1=29811
- PORT_ADOPT_V1=29812
- PORT_UPGRADE_V1=29813
- PORT_MANAGER_V2=29814
- PORT_TRANSFER_V2=29815
- PORT_RTTY=29816
- PORT_DEVICE_MONITOR=29817
- SHOW_SERVER_LOGS=true
- SHOW_MONGODB_LOGS=false
- SSL_CERT_NAME=tls.crt
- SSL_KEY_NAME=tls.key
- TZ=Europe/Warsaw
volumes:
- /home/miniserwer/omada/data:/opt/tplink/EAPController/data
- /home/miniserwer/omada/logs:/opt/tplink/EAPController/logs
networks:
macvlan1:
external: true |
Beta Was this translation helpful? Give feedback.
-
|
OK so I am not following exactly what you're looking for help on. Are you just wanting verification that your compose is correct or is there something else? |
Beta Was this translation helpful? Give feedback.
-
|
it's just about confirming the correctness |
Beta Was this translation helpful? Give feedback.
-
|
Yes. |
Beta Was this translation helpful? Give feedback.
-
|
👍 |
Beta Was this translation helpful? Give feedback.
-
|
Great job, Matt, everything is working fantastically – you're amazing!!! 💪💪💪 Please tell me one more thing – when migrating the controller from OC200 to Docker, should I add :8043 to the end of the address where I enter the new IP address? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I don’t believe you need to as it will find the discovery ports and ask the controller for what its proper address is. If that fails, it might be due to the controller IP not being set to your macvlan address but it should have set that correctly for macvlan. That’s more of a bridged network issue. |
Beta Was this translation helpful? Give feedback.
-
|
Quick question. |
Beta Was this translation helpful? Give feedback.
-
|
I suppose you could - I'm assuming that is coming from having either a router or switch that is TP-Link. I only have WAPs so I don't have any experience with that but I am assuming it's doing network discovery to see what is on your network. |
Beta Was this translation helpful? Give feedback.
That's not the container restarting, that looks like the cloud connection resetting. You would see the container's uptime show this if the container restarted:
You can see here that this container's been running for 3 hours so it hasn't been restarting. You would also see the container's entrypoint startup messages in the logs if …