Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: 5.15 does not start #509

Open
tr1plus opened this issue Dec 8, 2024 · 16 comments
Open

[Bug]: 5.15 does not start #509

tr1plus opened this issue Dec 8, 2024 · 16 comments
Assignees
@mbentley

Comments

@tr1plus
Copy link

tr1plus commented Dec 8, 2024

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

  1. Copy docker compose file from example
  2. Run docker compose up
  3. Change directories
  4. 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
@mbentley
Copy link
Owner

mbentley commented Dec 8, 2024

I am assuming that instead of 3.13 and 3.14 that you mean 5.13 and 5.14. I can't seem to reproduce this - are you customizing any settings related to RADIUS server config by chance? Anything in particular that you have configured that might be related to what it is complaining about?

@weak-head
Copy link

@mbentley it happens when you start from scratch and you don't migrate from previous version.
The workaround is to deploy 5.14 and then use 'latest' or '5.15' tag.

If you start from scratch and initializing the volumes using '5.15' this happens. To reproduce try to remove the existing docker volumes or use the empty folders with no data inside:

    volumes:
      - ./omada/data:/opt/tplink/EAPController/data
      - ./omada/logs:/opt/tplink/EAPController/logs

@tr1plus
Copy link
Author

tr1plus commented Dec 9, 2024

I am assuming that instead of 3.13 and 3.14 that you mean 5.13 and 5.14. I can't seem to reproduce this - are you customizing any settings related to RADIUS server config by chance? Anything in particular that you have configured that might be related to what it is complaining about?

Yes, I meant 5.xx (sorry I'm a bit sick so less concentrated ;))

As this is also happening on a fresh start (see comment from weak-head) - I think this has nothing to do with any specific configurations.

@mbentley it happens when you start from scratch and you don't migrate from previous version. The workaround is to deploy 5.14 and then use 'latest' or '5.15' tag.

If you start from scratch and initializing the volumes using '5.15' this happens. To reproduce try to remove the existing docker volumes or use the empty folders with no data inside:

    volumes:
      - ./omada/data:/opt/tplink/EAPController/data
      - ./omada/logs:/opt/tplink/EAPController/logs

Thanks for this analysis - I think migrating from 5.13 straight to 5.15 also breaks this. (but maybe I did something wrong with the back up my data dir)

Would you recommended upgrading from 5.13 to 5.14 to 5.15, or should I wait for a fix for now?

@mbentley
Copy link
Owner

mbentley commented Dec 9, 2024

OK, that's odd then because I can create new controllers and have no issues with startup. That's the one test that I always do before pushing changes on new versions. Could you both provide some info for me:

  • Output of docker info
  • Output of cat /etc/os-release
  • What filesystem type is your persistent data stored on?

I'm trying to think of anything else that would cause the controller to not start but just out of curiosity, could you try to use the 5.15-openj9 tag and see if you have the same behavior?

@tr1plus
Copy link
Author

tr1plus commented Dec 9, 2024 •
edited
Loading

This also happens when upgrading from 5.13 to 5.15, same behavior, I'll try upgrading from 5.13 to 5.14 to 5.15 now.

  • Output of docker info
Client: Docker Engine - Community
 Version:    27.3.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.17.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.7
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 22
  Running: 21
  Paused: 0
  Stopped: 1
 Images: 23
 Server Version: 27.3.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 88bf19b2105c8b17560993bee28a01ddc2f97182
 runc version: v1.2.2-0-g7cb3632
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.10.0-33-amd64
 Operating System: Debian GNU/Linux 11 (bullseye)
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 3.828GiB
 Name: docker
 ID: QYRD:6DY5:QKBG:DZPP:3TSO:75DE:2BRK:N5UE:J7YD:KHXV:FAKZ:JTQI
 Docker Root Dir: /mnt/docker/docker-root
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
  • Output of cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
  • What filesystem type is your persistent data stored on?

This is a VM on proxmox, but using a "local" disk, I beleive formatted as ext4

I'm trying to think of anything else that would cause the controller to not start but just out of curiosity, could you try to use the 5.15-openj9 tag and see if you have the same behavior?

Attaching to omada-controller
omada-controller  | INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508)
omada-controller  | INFO: Group (omada) doesn't exist; creating
omada-controller  | INFO: User (omada) doesn't exist; creating
omada-controller  | INFO: Time zone set to 'Europe/Brussels'
omada-controller  | INFO: Value of 'manage.http.port' already set to 8088 in omada.properties
omada-controller  | INFO: Value of 'manage.https.port' already set to 8043 in omada.properties
omada-controller  | INFO: Value of 'portal.http.port' already set to 8088 in omada.properties
omada-controller  | INFO: Value of 'portal.https.port' already set to 8843 in omada.properties
omada-controller  | INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties
omada-controller  | INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties
omada-controller  | INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties
omada-controller  | INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties
omada-controller  | INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties
omada-controller  | INFO: Value of 'port.discovery' already set to 29810 in omada.properties
omada-controller  | INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties
omada-controller  | INFO: Value of 'port.rtty' already set to 29816 in omada.properties
omada-controller  | INFO: Value of 'mongo.external' already set to false in omada.properties
omada-controller  | INFO: Value of 'eap.mongod.uri' already set to mongodb://127.0.0.1:27217/omada in omada.properties
omada-controller  | WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada)
omada-controller  | INFO: Version check passed; image version (5.15.6.7) >= the last version ran (5.15.6.7); writing image version to last ran file...
omada-controller  | INFO: userland/kernel check passed
omada-controller  | INFO: output of 'java -version':
omada-controller  | openjdk version "17.0.13" 2024-10-15
omada-controller  | IBM Semeru Runtime Open Edition 17.0.13.11 (build 17.0.13+11)
omada-controller  | Eclipse OpenJ9 VM 17.0.13.11 (build openj9-0.48.0, JRE 17 Linux amd64-64-Bit Compressed References 20241015_886 (JIT enabled, AOT enabled)
omada-controller  | OpenJ9   - 1d5831436e
omada-controller  | OMR      - d10a4d553
omada-controller  | JCL      - d17dd58f8d7 based on jdk-17.0.13+11)
omada-controller  |
omada-controller  |
omada-controller  | ##############################################################################
omada-controller  | ##############################################################################
omada-controller  | WARNGING: autobackup directory not found! Please configure automatic backups!
omada-controller  |   For instructions, see https://github.com/mbentley/docker-omada-controller#controller-backups
omada-controller  | ##############################################################################
omada-controller  | ##############################################################################
omada-controller  |
omada-controller  | INFO: Starting Omada Controller as user omada
omada-controller  | 12-09-2024 13:32:22.756 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
omada-controller  | 12-09-2024 13:32:22.764 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
omada-controller  | 12-09-2024 13:32:22.843 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
omada-controller  | 12-09-2024 13:32:22.850 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
omada-controller  | 12-09-2024 13:32:22.866 INFO [main] [] c.t.s.o.s.g.c(): Current dir omadac type is linux
omada-controller  | 12-09-2024 13:32:22.886 INFO [main] [] c.t.s.o.c.o.c.b(): success to load configuration omada.properties
omada-controller  | 12-09-2024 13:32:22.887 INFO [main] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
omada-controller  | 12-09-2024 13:32:22.887 INFO [main] [] c.t.s.o.s.g.c(): Configuration omadacType is linux
omada-controller  | 12-09-2024 13:32:22.949 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
omada-controller  | 12-09-2024 13:32:25.967 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 237
omada-controller  | 12-09-2024 13:32:25.969 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
omada-controller  | 12-09-2024 13:32:25.970 INFO [main] [] c.t.s.o.s.s.b(): Mongo DB server started
omada-controller  | 12-09-2024 13:32:26.679 WARN [main] [] c.t.s.o.s.a.u.X509CertificateUtils(): Valid radius server keystore is missing. Generating one ...
omada-controller  | Exception in thread "main" java.lang.NoSuchFieldError: org/bouncycastle/asn1/pkcs/PKCSObjectIdentifiers.id_alg_zlibCompress
omada-controller  |     at org.bouncycastle.asn1.cms.CMSObjectIdentifiers.<clinit>(Unknown Source)
omada-controller  |     at org.bouncycastle.operator.DefaultSignatureNameFinder.<clinit>(Unknown Source)
omada-controller  |     at org.bouncycastle.operator.jcajce.OperatorHelper.<clinit>(Unknown Source)
omada-controller  |     at org.bouncycastle.operator.jcajce.JcaContentSignerBuilder.<init>(Unknown Source)
omada-controller  |     at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:493)
omada-controller  |     at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:609)
omada-controller  |     at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:381)
omada-controller  |     at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:96)
omada-controller  |     at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:46)

@tr1plus
Copy link
Author

tr1plus commented Dec 9, 2024

Going from 5.13 -> 5.14 -> 5.15 seems to work.

Starting a new controller on 5.13 works.
Starting a new controller on 5.14 works.
Starting a new controller on 5.15 does not work.

@weak-head
Copy link

If it would be helpful, I have a little bit different error, though it's still related to X509CertificateUtils:

omada_controller  | INFO: Starting Omada Controller as user omada
omada_controller  | tail: cannot open '/opt/tplink/EAPController/logs/server.log' for reading: No such file or directory
omada_controller  | tail: '/opt/tplink/EAPController/logs/server.log' has appeared;  following new file
omada_controller  | 12-09-2024 08:51:10.614 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
omada_controller  | 12-09-2024 08:51:10.616 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
omada_controller  | 12-09-2024 08:51:10.630 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
omada_controller  | 12-09-2024 08:51:10.633 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
omada_controller  | 12-09-2024 08:51:10.644 INFO [main] [] c.t.s.o.s.g.c(): Current dir omadac type is linux
omada_controller  | 12-09-2024 08:51:10.657 INFO [main] [] c.t.s.o.c.o.c.b(): success to load configuration omada.properties
omada_controller  | 12-09-2024 08:51:10.658 INFO [main] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
omada_controller  | 12-09-2024 08:51:10.658 INFO [main] [] c.t.s.o.s.g.c(): Configuration omadacType is linux
omada_controller  | 12-09-2024 08:51:10.684 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
omada_controller  | Exception in thread "main" java.lang.NoSuchFieldError: xmss_SHAKE128_512ph
omada_controller  |       at org.bouncycastle.operator.DefaultSignatureAlgorithmIdentifierFinder.<clinit>(Unknown Source)
omada_controller  |       at org.bouncycastle.operator.jcajce.JcaContentSignerBuilder.build(Unknown Source)
omada_controller  |       at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:243)
omada_controller  |       at com.tplink.smb.omada.starter.OmadaBootstrap.b(SourceFile:935)
omada_controller  |       at com.tplink.smb.omada.starter.OmadaBootstrap.a(SourceFile:823)
omada_controller  |       at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:371)
omada_controller  |       at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:96)
omada_controller  |       at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:46)
omada_controller  | 12-09-2024 08:51:15.193 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 241

@weak-head
Copy link

@tr1plus Your container logs looks similar to the logs from an existing closed 5.14 bug: #418 (comment)

@tr1plus
Copy link
Author

tr1plus commented Dec 9, 2024

@tr1plus Your container logs looks similar to the logs from an existing closed 5.14 bug: #418 (comment)

I had looked into that one, but the exception itself is different (it happens at the same certificate generation tho).

Exception in thread "main" java.lang.IllegalAccessError: class com.tplink.smb.omada.system.api.util.X509CertificateUtils (in unnamed module @0x313ac989) cannot access class sun.security.x509.X500Name (in module java.base) because module java.base does not export sun.security.x509 to unnamed module @0x313ac989

vs

Exception in thread "main" java.lang.NoSuchFieldError: org/bouncycastle/asn1/pkcs/PKCSObjectIdentifiers.id_alg_zlibCompress

@mbentley
Copy link
Owner

mbentley commented Dec 9, 2024 •
edited
Loading

While I'll continue to see if there is anything I can do to replicate the issue, I would suggest starting a thread on the TP-Link community forums: https://community.tp-link.com/en/business/forum/582 to raise awareness to TP-Link.

I created a thread since I can now reproduce it.

I'm running the exact same version of Debian w/the same kernel, and same version of Docker, using the compose file provided and I am not seeing the issue which makes me think it is something going on in the controller software.

*edit: I decided to try to run the controller across a wide variety of systems I have and just like the random issues people were seeing with that one 5.14 version (as described here), one of the 5 machines I am testing on fails to run the controller and I get the error. Strangely enough, it is the same machine that I could reproduce the issue with the original 5.14 on.

@tr1plus
Copy link
Author

tr1plus commented Dec 9, 2024

Thanks!
In the meantime I will upgrade my existing install to 5.15 by going trough the versions one by one.

@mbentley
Copy link
Owner

If you all can please post on the forum post at https://community.tp-link.com/en/business/forum/topic/721750?page=1, that would be helpful!

@mbentley mbentley pinned this issue Dec 12, 2024
@mjsteckel mjsteckel mentioned this issue Dec 27, 2024
Closed
@mbentley
Copy link
Owner

mbentley commented Dec 27, 2024 •
edited
Loading

A workaround was posted:

Delete the files bcpkix-jdk15on-1.70.jar and bcprov-jdk15on-1.70.jar from the controller and the controller will start. I may update the entrypoint with a workaround that will be triggered by env var or something to delete them for the user as that's kind of tricky.

*edit: I just added an environment variable WORKAROUND_509 that when set to true will delete those files from the container, if present. I also added a note to the known issues.

@erkr
Copy link

erkr commented Jan 8, 2025 •
edited
Loading

Please help. I tried to setup this controller fresh in home assistant today and also get this keystore exception
Question: Where to apply the mentioned WORKAROUND_509 for this Home assistant add-on?

Thanks Eric

@erkr erkr mentioned this issue Jan 8, 2025
Closed
@mbentley
Copy link
Owner

mbentley commented Jan 8, 2025

Please help. I tried to setup this controller fresh in home assistant today and also get this keystore exception Question: Where to apply the mentioned WORKAROUND_509 for this Home assistant add-on?

Thanks Eric

I'm not immediately familiar with how it works with home assistant to deploy the container but what you're looking for is the ability to add or modify the default environment variables for the container. You need to add an environment variable with the name/key WORKAROUND_509 and a value of true for it to work. Not sure if home assistant exposes the ability to manually specify an env var but I would expect it should somehow.

@erkr
Copy link

erkr commented Jan 8, 2025 •
edited
Loading

Thx, a Developer of the add-on just responded and will look into it. jkunczik/home-assistant-omada#74 (comment)
Best Eric

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mbentley mbentley

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mbentley @weak-head @erkr @tr1plus