hassio-addons: Omada crashes

Hi,

the Omada add-on keeps crashing even after a full system restart.

Please see the log file:

-----------------------------------------------------------
 Add-on: Omada
 TP-Link Omada Controller
-----------------------------------------------------------
 Add-on version: 5.9-chromium-amd64-2023-05-26
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.2  (amd64 / generic-x86-64)
 Home Assistant Core: 2023.5.4
 Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
-----------------------------------------------------------
 Provided by: https://github.com/alexbelgium/hassio-addons 
-----------------------------------------------------------
Creating directory
Creating symlink
Updating permissions
[11:54:21] INFO: Execute /config/addons_autoscripts/omada.sh if existing
[11:54:21] INFO: ... no script found
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/Berlin'
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
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: Creating keystore directory (/opt/tplink/EAPController/data/keystore)
INFO: Setting permissions on /opt/tplink/EAPController/data/keystore
INFO: Importing cert from /cert/tls.[key|crt]
INFO: Version check passed; image version (5.9.31) >= the last version ran (0.0.0); writing image version to last ran file...
INFO: userland/kernel check passed
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
05-31-2023 11:54:23.334 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
05-31-2023 11:54:23.338 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
05-31-2023 11:54:23.342 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
05-31-2023 11:54:23.344 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
05-31-2023 11:54:23.347 INFO [main] [] c.t.s.o.c.o.a.b(): success to load configuration omada.properties
05-31-2023 11:54:23.348 INFO [log4j-thread] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
05-31-2023 11:54:23.366 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
Exception in thread "Thread-0" java.lang.ExceptionInInitializerError
	at com.tplink.smb.omada.common.concurrent.thread.a.a(SourceFile:85)
	at com.tplink.smb.omada.common.concurrent.thread.a.c(SourceFile:303)
	at com.tplink.smb.omada.starter.OmadaBootstrap.b(SourceFile:191)
	at com.tplink.smb.omada.starter.OmadaLinuxMain.b(SourceFile:87)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.NullPointerException: Cannot invoke "com.tplink.smb.omada.common.concurrent.thread.CommonExecutorProperties.getCommCoreThreads()" because "com.tplink.smb.omada.common.concurrent.thread.a$b.a" is null
	at com.tplink.smb.omada.common.concurrent.thread.a$b.<clinit>(SourceFile:72)
	... 5 more
05-31-2023 11:54:25.881 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 252
05-31-2023 11:54:25.882 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
05-31-2023 11:54:25.883 INFO [main] [] c.t.s.o.s.s.b(): Mongo DB server started
05-31-2023 11:54:26.312 ERROR [main] [] c.t.s.o.s.a(): Port 8088 is already in use.
05-31-2023 11:54:26.316 ERROR [main] [] c.t.s.o.s.a(): Port 8088 is already in use. Release the port and try again.
05-31-2023 11:54:26.316 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Port 8088 is already in use. Release the port and try again.
05-31-2023 11:54:26.316 ERROR [main] [] c.t.s.o.s.OmadaBootstrap(): Environment is not ok for controller running
05-31-2023 11:54:26.316 ERROR [main] [] c.t.s.o.s.OmadaLinuxMain(): Bootstrap prepare failed, going to exit.
05-31-2023 11:54:26.318 WARN [Thread-0] [] c.t.s.o.c.s.a(): Spring Bean Factory has not been initialed, failed to get bean class com.tplink.smb.omada.common.concurrent.thread.CommonExecutorProperties
05-31-2023 11:54:26.320 WARN [Thread-0] [] c.t.s.o.c.s.a(): Spring Bean Factory has not been initialed, failed to get bean class io.micrometer.core.instrument.MeterRegistry

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 38 (19 by maintainers)

Commits related to this issue

Most upvoted comments

Looks like 8088 is used by Influx DB but this did not change since installation. I’m still trying to figure out, what was changed and when… The only change I can see is the host OS and Omada, both by automated updates, no manual changes of whatever.

Sorry for the late reply, was on holiday.

Version 5.9-chromium-amd64-2023-05-12 was now done as automatic update (latest) and is working fine.

Yes, for me it is working. It starts with the config wizard, but I was able to restore a backup.

Okay my issue had nothing to do with this. Restoring Omada from a backup got it working again. Sorry for that.