5.15.6.7 - Controller will fail to start on random systems
5.15.6.7 - Controller will fail to start on random systems
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.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I can confirm, after deleting the two mentioned files, the latest Controller 5.15.6.7 has started and seems to be working properly. Thank you.
- Copy Link
- Report Inappropriate Content
Removing this files helped me.
but removed 3 files that looks for me as duplicate in different versions:
bcpkix-jdk18on-1.70.jar
bcprov-jdk18on-1.70.jar
bcutil-jdk18on-1.70.jar
Update:
After I restored the last backup and restarted, the files are back.
If I then delete these files again, I get the following error:
Exception in thread "main" java.lang.IllegalAccessError: class com.tplink.smb.omada.system.api.util.X509CertificateUtils (in unnamed module @0x5542c4ed) cannot access class sun.security.x509.X500Name (in module java.base) because module java.base does not export sun.security.x509 to unnamed module @0x5542c4ed
at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:526)
at com.tplink.smb.omada.system.api.util.X509CertificateUtils.a(SourceFile:499)
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)
Update 2:
The second error can be fixed by disable the radius from site-settings (after restore the backup).
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1474
Replies: 12
Voters 0
No one has voted for it yet.