Controller Version
5.15
Describe the Bug
This was my first time using this software. When starting with tag latest/5.15 the logs stop at the following:
##############################################################################
##############################################################################
WARNGING: autobackup directory not found! Please configure automatic backups!
For instructions, see https://github.com/mbentley/docker-omada-controller#controller-backups
##############################################################################
##############################################################################
INFO: Starting Omada Controller as user omada
12-08-2024 21:43:47.526 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
12-08-2024 21:43:47.533 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
12-08-2024 21:43:47.562 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
12-08-2024 21:43:47.570 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
12-08-2024 21:43:47.590 INFO [main] [] c.t.s.o.s.g.c(): Current dir omadac type is linux
12-08-2024 21:43:47.612 INFO [main] [] c.t.s.o.c.o.c.b(): success to load configuration omada.properties
12-08-2024 21:43:47.613 INFO [main] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
12-08-2024 21:43:47.613 INFO [main] [] c.t.s.o.s.g.c(): Configuration omadacType is linux
12-08-2024 21:43:47.696 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
12-08-2024 21:43:51.206 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 228
12-08-2024 21:43:51.207 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
12-08-2024 21:43:51.208 INFO [main] [] c.t.s.o.s.s.b(): Mongo DB server started
12-08-2024 21:43:51.970 WARN [main] [] c.t.s.o.s.a.u.X509CertificateUtils(): Valid radius server keystore is missing. Generating one ...
Exception in thread "main" java.lang.NoSuchFieldError: id_alg_zlibCompress
at org.bouncycastle.asn1.cms.CMSObjectIdentifiers.<clinit>(Unknown Source)
at org.bouncycastle.operator.DefaultSignatureNameFinder.<clinit>(Unknown Source)
at org.bouncycastle.operator.jcajce.OperatorHelper.<clinit>(Unknown Source)
at org.bouncycastle.operator.jcajce.JcaContentSignerBuilder.<init>(Unknown Source)
at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:493)
at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:609)
at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:381)
at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:96)
at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:46)
I started up everything using version/tag 3.13 (as I saw a lot of issues with 3.14 I wanted to go to a stable version) and everything is working there. Once I had adopted my switch & EAP, I tried to re start the container with latest tag and I got the same error as above.
Currently rolling back to 3.13 (as I had backed up the data dir)
Expected Behavior
5.15 should start without issue, same as with the 3.13 I used
Steps to Reproduce
- Copy docker compose file from example
- Run docker compose up
- Change directories
- Observer this fails
How You're Launching the Container
docker compose up
version: "3.1"
services:
omada-controller:
container_name: omada-controller
image: mbentley/omada-controller:5.13 #or 5.15, or latest
restart: unless-stopped
ulimits:
nofile:
soft: 4096
hard: 8192
stop_grace_period: 60s
network_mode: host
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/Brussels
volumes:
- ${dir}/data:/opt/tplink/EAPController/data
- ${dir}/logs:/opt/tplink/EAPController/logs
Container Logs
INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508)
INFO: Group (omada) doesn't exist; creating
INFO: User (omada) doesn't exist; creating
INFO: Time zone set to 'Europe/Brussels'
INFO: Value of 'manage.http.port' already set to 8088 in omada.properties
INFO: Value of 'manage.https.port' already set to 8043 in omada.properties
INFO: Value of 'portal.http.port' already set to 8088 in omada.properties
INFO: Value of 'portal.https.port' already set to 8843 in omada.properties
INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties
INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties
INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties
INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties
INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties
INFO: Value of 'port.discovery' already set to 29810 in omada.properties
INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties
INFO: Value of 'port.rtty' already set to 29816 in omada.properties
INFO: Value of 'mongo.external' already set to false in omada.properties
INFO: Value of 'eap.mongod.uri' already set to mongodb://127.0.0.1:27217/omada in omada.properties
WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada)
INFO: Version check passed; image version (5.15.6.7) >= the last version ran (5.13.30.8); writing image version to last ran file...
INFO: userland/kernel check passed
INFO: output of 'java -version':
openjdk version "17.0.13" 2024-10-15
OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu120.04)
OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu120.04, mixed mode, sharing)
##############################################################################
##############################################################################
WARNGING: autobackup directory not found! Please configure automatic backups!
For instructions, see https://github.com/mbentley/docker-omada-controller#controller-backups
##############################################################################
##############################################################################
INFO: Starting Omada Controller as user omada
12-08-2024 21:43:47.526 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
12-08-2024 21:43:47.533 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
12-08-2024 21:43:47.562 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
12-08-2024 21:43:47.570 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
12-08-2024 21:43:47.590 INFO [main] [] c.t.s.o.s.g.c(): Current dir omadac type is linux
12-08-2024 21:43:47.612 INFO [main] [] c.t.s.o.c.o.c.b(): success to load configuration omada.properties
12-08-2024 21:43:47.613 INFO [main] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
12-08-2024 21:43:47.613 INFO [main] [] c.t.s.o.s.g.c(): Configuration omadacType is linux
12-08-2024 21:43:47.696 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
12-08-2024 21:43:51.206 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 228
12-08-2024 21:43:51.207 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
12-08-2024 21:43:51.208 INFO [main] [] c.t.s.o.s.s.b(): Mongo DB server started
12-08-2024 21:43:51.970 WARN [main] [] c.t.s.o.s.a.u.X509CertificateUtils(): Valid radius server keystore is missing. Generating one ...
Exception in thread "main" java.lang.NoSuchFieldError: id_alg_zlibCompress
at org.bouncycastle.asn1.cms.CMSObjectIdentifiers.<clinit>(Unknown Source)
at org.bouncycastle.operator.DefaultSignatureNameFinder.<clinit>(Unknown Source)
at org.bouncycastle.operator.jcajce.OperatorHelper.<clinit>(Unknown Source)
at org.bouncycastle.operator.jcajce.JcaContentSignerBuilder.<init>(Unknown Source)
at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:493)
at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:609)
at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:381)
at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:96)
at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:46)
MongoDB Logs
No response
Additional Context
No response
Controller Version
5.15
Describe the Bug
This was my first time using this software. When starting with tag latest/5.15 the logs stop at the following:
I started up everything using version/tag 3.13 (as I saw a lot of issues with 3.14 I wanted to go to a stable version) and everything is working there. Once I had adopted my switch & EAP, I tried to re start the container with latest tag and I got the same error as above.
Currently rolling back to 3.13 (as I had backed up the data dir)
Expected Behavior
5.15 should start without issue, same as with the 3.13 I used
Steps to Reproduce
How You're Launching the Container
Container Logs
MongoDB Logs
No response
Additional Context
No response