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

Fresh install stable version 5.15.6.7 fails #74

Closed
erkr opened this issue Jan 8, 2025 · 11 comments
Closed

Fresh install stable version 5.15.6.7 fails #74

erkr opened this issue Jan 8, 2025 · 11 comments

Comments

@erkr
Copy link

erkr commented Jan 8, 2025 •
edited
Loading

I installed a fresh controller, with all settings default. It kind of starts, but I can't open the web_ui and have an exception in the log.
It is related to mbentley/docker-omada-controller#509 (comment), but I don't know how to apply the work around mentioned there.

01-08-2025 13:12:11.016 WARN [main] [] c.t.s.o.s.OmadaBootstrap(): Valid 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: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)

Best Eric
@Jeruntu
Copy link
Collaborator

Jeruntu commented Jan 8, 2025

Thanks for reporting. I took a quick look at the workaround. It basically means an environment variable has to be set, and therefore an extra option in the add-on must be added. I'll look into it.

@erkr erkr mentioned this issue Jan 8, 2025
Open
@chiefcomm
Copy link

related to #73 with same WORKAROUND_509 issue

@Jeruntu
Copy link
Collaborator

Jeruntu commented Jan 8, 2025

I released a new version for Stable with the new option: Enable Workaround 509. Please let me know if this works for you.

@erkr
Copy link
Author

erkr commented Jan 8, 2025

I released a new version for Stable with the new option: Enable Workaround 509. Please let me know if this works for you.

Thanks for the fast response! I think it still fails. I see an error, and a little forget the key store exception:


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/data'; setting correct ownership (omada:omada)
WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada)
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.15.6.7); 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
01-08-2025 13:12:07.090 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
01-08-2025 13:12:07.113 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
01-08-2025 13:12:07.271 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
01-08-2025 13:12:07.286 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
01-08-2025 13:12:07.336 INFO [main] [] c.t.s.o.s.g.c(): Current dir omadac type is linux
01-08-2025 13:12:07.403 INFO [main] [] c.t.s.o.c.o.c.b(): success to load configuration omada.properties
01-08-2025 13:12:07.406 INFO [main] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
01-08-2025 13:12:07.407 INFO [main] [] c.t.s.o.s.g.c(): Configuration omadacType is linux
01-08-2025 13:12:07.559 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
01-08-2025 13:12:10.089 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 254
01-08-2025 13:12:10.097 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
01-08-2025 13:12:10.099 INFO [main] [] c.t.s.o.s.s.b(): Mongo DB server started
01-08-2025 13:12:11.016 WARN [main] [] c.t.s.o.s.OmadaBootstrap(): Valid 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: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)
01-08-2025 13:24:44.510 WARN [Thread-0] [] c.t.s.o.c.s.a(): Spring Bean Factory has not been initialed, failed to get bean commThreadPool
01-08-2025 13:24:44.522 INFO [Thread-0] [] c.t.s.o.s.s.b(): Going to stop mongod which pid is 254
01-08-2025 13:24:51.665 INFO [Thread-0] [] c.t.s.o.s.OmadaBootstrap(): success to shutdown mongodb database
01-08-2025 13:24:51.665 INFO [Thread-0] [] c.t.s.o.s.OmadaBootstrap(): Omada Controller exited
01-08-2025 13:24:51.665 INFO [Thread-0] [] c.t.s.o.s.OmadaLinuxMain(): ShutdownHook: service stopped.
[23:52:23] INFO: Create 'logs' directory inside persistent /data volume, if it doesn't exist.
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/Amsterdam'
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/data'; setting correct ownership (omada:omada)
WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada)
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.15.6.7); 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
01-08-2025 23:52:32.319 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
01-08-2025 23:52:32.341 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
01-08-2025 23:52:32.460 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
01-08-2025 23:52:32.477 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
01-08-2025 23:52:32.533 INFO [main] [] c.t.s.o.s.g.c(): Current dir omadac type is linux
01-08-2025 23:52:32.607 INFO [main] [] c.t.s.o.c.o.c.b(): success to load configuration omada.properties
01-08-2025 23:52:32.610 INFO [main] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
01-08-2025 23:52:32.611 INFO [main] [] c.t.s.o.s.g.c(): Configuration omadacType is linux
01-08-2025 23:52:32.800 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
01-08-2025 23:52:35.327 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 257
01-08-2025 23:52:35.335 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
01-08-2025 23:52:35.337 INFO [main] [] c.t.s.o.s.s.b(): Mongo DB server started
01-08-2025 23:52:36.257 WARN [main] [] c.t.s.o.s.OmadaBootstrap(): Valid 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: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)

@Jeruntu
Copy link
Collaborator

Jeruntu commented Jan 8, 2025

You haven't enabled the option yet. The log doesn't show:
INFO: Enable workaround for issue #509

@erkr
Copy link
Author

erkr commented Jan 8, 2025 •
edited
Loading

Oh my bad. I didn't realise it was optional. It now starts much further. Still two exception in the log about opening jar files, but is then it continues:

Failed to scan [file:/opt/tplink/EAPController/lib/bcpkix-jdk15on-1.70.jar] from classloader hierarchy
java.io.IOException: java.lang.reflect.InvocationTargetException
...

Second exception:

Failed to scan [file:/opt/tplink/EAPController/lib/bcprov-jdk15on-1.70.jar] from classloader hierarchy
java.io.IOException: java.lang.reflect.InvocationTargetException
...

And a few times this error:

01-09-2025 00:11:46.385 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Start init data.

The web ui opens now, but is still blank:
image

I'm new to Omada, so not sure what to expect.

The log now continues to log these kind of messages:


01-09-2025 00:30:00.012 INFO [log-timeout-resolve-event-pool-0] [] c.t.s.o.l.d.m.d.e(): ensure index for log collection in 30 ~ 7days
01-09-2025 00:30:00.088 INFO [log-timeout-resolve-event-pool-0] [] c.t.s.o.l.d.m.d.e(): timeout resolve for log in 9 ~ 7 days
01-09-2025 00:30:00.331 WARN [log-dst-info-event-pool-0] [] c.t.s.o.l.d.b.f(): Not mps model of mspIdd8605cd67c145b05ccafb868208e71a5, handle as keep 1 month msp log
01-09-2025 00:30:00.618 WARN [log-dst-info-event-pool-0] [] c.t.s.o.l.d.b.m(): Not mps model of mspIdd8605cd67c145b05ccafb868208e71a5, handle as keep 1 month msp log
01-09-2025 00:30:00.868 WARN [log-dst-info-event-pool-0] [] c.t.s.o.l.d.b.i(): Not mps model of mspIdd8605cd67c145b05ccafb868208e71a5, handle as keep 1 month msp log
01-09-2025 00:32:45.887 INFO [comm-pool-15] [] c.t.s.o.m.d.a.u.f.c(): Target firmware check task run
01-09-2025 00:32:45.891 INFO [comm-pool-15] [] c.t.s.o.m.d.a.u.f.c(): no omadac need handle target firmware upgrade

@erkr
Copy link
Author

erkr commented Jan 8, 2025

Going to bed now, thanks for the great help so far 🤗

@Jeruntu
Copy link
Collaborator

Jeruntu commented Jan 9, 2025

These exceptions come from the two libraries that are deleted by this workaround option. I can't do much about it from my side. Can you try maybe to do a clean fresh installation?

@erkr
Copy link
Author

erkr commented Jan 9, 2025 •
edited
Loading

I will give that a try 👍

Edit: no change. Web ui remains blank. The Add-on is very memory greedy (about 1.5GB, is that normal?):
image
And some website related errors in the log when I try to open the ui:

01-09-2025 20:59:52.879 WARN [https-jsse-nio-8043-exec-5] [] c.t.s.o.i.b.l(): OmadacId=c6c7414ab1a03bb1024331b02cf3a494 find no root users
01-09-2025 20:59:53.431 WARN [https-jsse-nio-8043-exec-7] [] c.t.s.o.m.l.p.c.f(): failed to find site:SiteId(defaultInternetSite) in db, omadacId:OmadacId(c6c7414ab1a03bb1024331b02cf3a494).
01-09-2025 20:59:53.439 WARN [https-jsse-nio-8043-exec-7] [] c.t.s.o.m.l.p.c.f(): failed to find site:SiteId(defaultInternetSite) in db, omadacId:OmadacId(c6c7414ab1a03bb1024331b02cf3a494).
01-09-2025 20:59:53.490 INFO [https-jsse-nio-8043-exec-10] [] c.t.s.o.m.c.d.m.d.u(): site not exists. omadacId: OmadacId(c6c7414ab1a03bb1024331b02cf3a494), siteId: SiteId(defaultInternetSite).
01-09-2025 21:02:34.459 INFO [comm-pool-14] [] c.t.s.o.m.d.a.u.f.c(): Target firmware check task run
01-09-2025 21:02:34.463 INFO [comm-pool-14] [] c.t.s.o.m.d.a.u.f.c(): no omadac need handle target firmware upgrade

Is it possible to install an older version, and upgrade later?

@Jeruntu
Copy link
Collaborator

Jeruntu commented Jan 10, 2025

Unfortunately I can't help you further. This is a known issue and has to be fixed in the Omada controller. It is very memory greedy indeed, that's "normal".

@erkr
Copy link
Author

erkr commented Jan 10, 2025 •
edited
Loading

Still some exceptions while starting, but I have it working. The Web_UI remains empty if there are no Omada devices on the network. I apparently started in the wrong order ;-(
Thanks for the support :-)

@erkr erkr closed this as completed Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@erkr @Jeruntu @chiefcomm