Business Community > All Threads > 5.15.6.7 - Controller will fail to start on random systems
< All Threads

5.15.6.7 - Controller will fail to start on random systems

5.15.6.7 - Controller will fail to start on random systems

5.15.6.7 - Controller will fail to start on random systems
5.15.6.7 - Controller will fail to start on random systems
2 weeks ago - last edited 2 weeks ago
Model: Omada Software Controller (Linux)  
Hardware Version:
Firmware Version:

For random systems, the controller for 5.14.6.7 fails to start, there is an error on startup: 


12-09-2024 15:02:57.172 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
12-09-2024 15:02:57.176 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
12-09-2024 15:02:57.201 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
12-09-2024 15:02:57.205 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
12-09-2024 15:02:57.218 INFO [main] [] c.t.s.o.s.g.c(): Current dir omadac type is linux
12-09-2024 15:02:57.234 INFO [main] [] c.t.s.o.c.o.c.b(): success to load configuration omada.properties
12-09-2024 15:02:57.235 INFO [main] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
12-09-2024 15:02:57.235 INFO [main] [] c.t.s.o.s.g.c(): Configuration omadacType is linux
12-09-2024 15:02:57.284 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
12-09-2024 15:02:58.291 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 234
12-09-2024 15:02:58.293 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
12-09-2024 15:02:58.293 INFO [main] [] c.t.s.o.s.s.b(): Mongo DB server started
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:242)
        at com.tplink.smb.omada.starter.OmadaBootstrap.b(SourceFile:935)
        at com.tplink.smb.omada.starter.OmadaBootstrap.a(SourceFile:823)
        at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:371)
        at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:96)
        at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:46)
12-09-2024 15:02:58.509 WARN [main] [] c.t.s.o.s.OmadaBootstrap(): Valid keystore is missing. Generating one ...

 

 

Oddly enough, the machine that it doesn't start on is the same machine I had the problem with the bug in https://community.tp-link.com/en/business/forum/topic/670026 on.

  0      
 
  0      
 
#1
Options
10 Reply
Re:5.15.6.7 - Controller will fail to start on random systems
2 weeks ago

Hi  @mbentley 

 

Could you please list the affected systems and their versions?

  0  
  0  
#2
Options
Re:5.15.6.7 - Controller will fail to start on random systems
2 weeks ago

  @Vincent-TP 



# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

 

 

I'm running this in Docker - it's specifically 5.15.6.7 where this is happening.  Let me know if more information is helpful.  I have many identical systems where they have the exact same kernel and even a system that is a clone of this one that I can reproduce the issue but the clone doesn't have the problem.  There are two other people who have also reported the same issues here: https://github.com/mbentley/docker-omada-controller/issues/509

  0  
  0  
#3
Options
Re:5.15.6.7 - Controller will fail to start on random systems
2 weeks ago

  @Vincent-TP 

 

~$ 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/"

 

 

I'm the one who raised the issue in the docker repo - I was able to upgrade from 5.13 to 5.14 to 5.15, and 5.15 is running now, but I'm unable to create a new controller starting on the 5.15 version.

  0  
  0  
#4
Options
Re:5.15.6.7 - Controller will fail to start on random systems
a week ago

Hi  @Triplus 

 

Thanks for the info.

 

Please tell us what's the jdk versions?

  0  
  0  
#5
Options
Re:5.15.6.7 - Controller will fail to start on random systems
a week ago
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)
  0  
  0  
#6
Options
Re:5.15.6.7 - Controller will fail to start on random systems
a week ago

  @mbentley Exactly same error over here with omada controller in docker..
Unifi Controller works perfect anyway, also with docker.
Please fix.

  0  
  0  
#7
Options
Re:5.15.6.7 - Controller will fail to start on random systems
a week ago

  @mbentley 

 

Hi there,

 

same problem here. Setting up a new contoller does not work.

 

Regards, Eric

  0  
  0  
#8
Options
Re:5.15.6.7 - Controller will fail to start on random systems
Wednesday - last edited Wednesday

  @mbentley 

 

same here on QNAP TS-673A 32G

 

5.14.32.4 work without problem in docker

 

[~] # cat /etc/os-release
NAME="QTS"
VERSION="5.2.2 (20241114)"
ID=qts
PRETTY_NAME="QTS 5.2.2 (20241114)"
VERSION_ID="5.2.2"

  0  
  0  
#9
Options
Re:5.15.6.7 - Controller will fail to start on random systems
12 hours ago

@mbentley Im also using your Docker Image to run my Omada Controller @home. If you just remove the files "bcpkix-jdk15on-1.70.jar" and "bcprov-jdk15on-1.70.jar" its working.
There are some errors at the start, but as workaround its good enough. It looks like the libs are duplicated in 2 diffrent versions (...jdk15on-1.70.jar and jdk18on-1.78.jar).

  0  
  0  
#10
Options
Re:5.15.6.7 - Controller will fail to start on random systems
5 hours ago

  @mbentley 

5.15.8.1 still same problem

 

INFO: Starting Omada Controller as user omada
tail: cannot open '/opt/tplink/EAPController/logs/server.log' for reading: No such file or directory
tail: '/opt/tplink/EAPController/logs/server.log' has appeared;  following new file
12-24-2024 19:18:27.823 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
12-24-2024 19:18:27.829 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
12-24-2024 19:18:27.870 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
12-24-2024 19:18:27.877 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
12-24-2024 19:18:27.901 INFO [main] [] c.t.s.o.s.g.c(): Current dir omadac type is linux
12-24-2024 19:18:27.932 INFO [main] [] c.t.s.o.c.o.c.b(): success to load configuration omada.properties
12-24-2024 19:18:27.933 INFO [main] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
12-24-2024 19:18:27.933 INFO [main] [] c.t.s.o.s.g.c(): Configuration omadacType is linux
12-24-2024 19:18:27.996 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
12-24-2024 19:18:29.506 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 234
12-24-2024 19:18:29.508 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
12-24-2024 19:18:29.509 INFO [main] [] c.t.s.o.s.s.b(): Mongo DB server started
12-24-2024 19:18:29.859 WARN [main] [] c.t.s.o.s.OmadaBootstrap(): Valid keystore is missing. Generating one ...
Exception in thread "main" java.lang.NoSuchFieldError: xmss_SHAKE128_512ph
        at org.bouncycastle.operator.DefaultSignatureAlgorithmIdentifierFinder.<clinit>(Unknown Source)
        at org.bouncycastle.operator.jcajce.JcaContentSignerBuilder.build(Unknown Source)
        at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:243)
        at com.tplink.smb.omada.starter.OmadaBootstrap.b(SourceFile:935)
        at com.tplink.smb.omada.starter.OmadaBootstrap.a(SourceFile:823)
        at com.tplink.smb.omada.starter.OmadaBootstrap.e(SourceFile:371)
        at com.tplink.smb.omada.starter.OmadaLinuxMain.a(SourceFile:96)
        at com.tplink.smb.omada.starter.OmadaLinuxMain.main(SourceFile:46)

  0  
  0  
#11
Options

Information

Helpful: 0

Views: 578

Replies: 10

Related Articles
Controller - Failed to start
517 0
Can't start controller after port change
2294 0
Omada 5.15.6.7 : EAP115-Wall breaks the "firmware" feature
317 0
Controller won't start after reboot
798 0
Failure to start the omada controller after version downgrade
1113 0
Omada Controller in Docker automated daily backups occasionally fail
419 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.