🐛 [Omada] Rebooting the addon makes me lose access to my configuration #1063

ChriKn · 2023-11-05T16:27:37Z

Description

Since a specific update, where I lost my configuration / session / had to redo everything from scratch, it seems to happen again everytime I reboot the plugin.
I now have a backup and recreate an account / link it to the tp-link account, but it still means having to reset everything every so often, which isn't great.

This seems to show up in the logs :
11-05-2023 17:23:17.699 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): No active profile set, falling back to 1 default profile: "default"

Of course, there was a working profile before the reboot.

Reproduction steps

1. reboot the plugin
2. open the plugin
3. see the account has disappeared

Addon Logs

11-05-2023 17:23:17.151 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: start run omada tasks
11-05-2023 17:23:17.151 INFO [main] [] c.t.s.o.s.t.SpringBootStartUpTask(): record: task SpringBootStartupTask start

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v2.6.6)

11-05-2023 17:23:17.697 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): Starting OmadaLinuxMain v5.12.7 using Java 17.0.8.1 on db21ed7f-omada with PID 7 (/opt/tplink/EAPController/lib/local-starter-5.12.7.jar started by omada in /opt/tplink/EAPController/lib)
11-05-2023 17:23:17.699 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): No active profile set, falling back to 1 default profile: "default"
11-05-2023 17:23:26.578 WARN [main] [] o.s.d.c.CustomConversions(): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation.
11-05-2023 17:23:28.325 INFO [main] [] c.t.s.o.m.l.p.e.LicenseEventCenterProperties(): licenseManagerTopic: omada.cloud.license.prd.topics
11-05-2023 17:23:30.792 INFO [main] [] c.t.s.o.m.d.p.t.TransportConfiguration(): upgradeSendReq workGroup core thread num is 1, max thread num is 1
11-05-2023 17:23:31.783 WARN [main] [] o.s.d.c.CustomConversions(): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation.
11-05-2023 17:23:32.289 INFO [main] [] c.t.s.o.m.d.p.t.TransportConfiguration(): manager workGroup core thread  num is 16, max thread num is 16
11-05-2023 17:23:32.632 INFO [main] [] c.t.s.o.m.c.d.m.s.a.AbstractActiveSiteCacheImpl(): Scheduled ActiveSitesCache period flush buf task at fixed rate of 30000 millis.
11-05-2023 17:23:37.429 INFO [main] [] c.t.s.o.m.c.d.m.s.w.s.c.WirelessGroupConfig(): ssidWorkerGroup thread size is 4, queue size is 1500
11-05-2023 17:23:44.035 INFO [main] [] c.t.s.o.m.d.d.m.m.c.DeviceMsgConfig(): setMsgThreadPool thread coreSize is 4, maxSize is 4,queue size is 4500
11-05-2023 17:23:44.456 INFO [main] [] c.t.s.e.s.c.c(): start schedule remove expire device... period = 10
11-05-2023 17:23:44.473 INFO [main] [] c.t.s.e.s.c.c(): update rateLimiterCache, permitsPerSecond = 5.0
11-05-2023 17:23:50.608 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.618 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.619 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.619 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.620 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.620 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.621 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.621 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.622 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.625 INFO [main] [] c.t.s.o.a.d.c.SwaggerConfig(): initOpenAPI.docInfo=DocInfo(title=Omada Open API, description=Omada Open API, version=v0.1, websiteName=Omada Controller, websiteUrl=http://omada.tplink.com)
11-05-2023 17:23:50.684 WARN [main] [] o.s.d.c.CustomConversions(): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation.
11-05-2023 17:23:52.587 WARN [main] [] o.s.d.c.CustomConversions(): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation.
11-05-2023 17:23:53.654 WARN [main] [] c.t.c.r.c.d.MemoryDictionary(): Duplicate type code [-1,207], overwriting Digest-Attributes with WISPr-Redirection-URL
11-05-2023 17:23:53.654 WARN [main] [] c.t.c.r.c.d.MemoryDictionary(): Duplicate type code [-1,207], overwriting WISPr-Redirection-URL with WISPr-Location-ID
11-05-2023 17:23:53.758 INFO [main] [] c.t.c.c.a.c.a.e.c.ActionConfig(): Success to init eap action dispatcher, num = 20, invokes = {EAP_TTLS_ACTION_PROCESS_CLIENT_KEY_FULL=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket@1fd2d192, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket.action3(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_PROCESS_CLIENT_KEY_FULL=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action3(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_PROCESS_ACK=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action4(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), EAP_TTLS_ACTION_INIT=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket@1fd2d192, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket.action0(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), EAP_TTLS_ACTION_PROCESS_TUNNEL_AUTHENTICATION_START=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket@1fd2d192, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket.action4(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), EAP_TTLS_ACTION_PROCESS_TUNNEL_AUTHENTICATION_WAIT_EAPMSCHAPV2_VERIFIED_RESPONSE=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket@1fd2d192, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket.action7(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), EAP_MD5_ACTION_PRECESS_CHALLENGE_VALUE=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapMd5ActionBucket@420da686, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapMd5ActionBucket.action1(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), EAP_TTLS_ACTION_PROCESS_CLIENT_HELLO=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket@1fd2d192, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket.action1(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), EAP_TTLS_ACTION_PROCESS_TUNNEL_AUTHENTICATION_EAP_MD5_CHALLENGE=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket@1fd2d192, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket.action5(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_PROCESS_TUNNEL_AUTHENTICATION_WAIT_MSCHAPV2_RESPONSE=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action7(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), EAP_TTLS_ACTION_SEND_SERVER_HELLO_NEXT_FRAGMENT=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket@1fd2d192, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket.action2(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), EAP_TTLS_ACTION_PROCESS_TUNNEL_AUTHENTICATION_WAIT_EAPMSCHAPV2_RESPONSE=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket@1fd2d192, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapTtlsActionBucket.action6(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_INIT=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action0(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_SEND_SERVER_HELLO_NEXT_FRAGMENT=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action2(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), EAP_MD5_ACTION_INIT=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapMd5ActionBucket@420da686, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.EapMd5ActionBucket.action0(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_PROCESS_TUNNEL_AUTHENTICATION_START=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action5(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_PROCESS_TUNNEL_AUTHENTICATION_MD5_CHALLENGE=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action6(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_PROCESS_TUNNEL_AUTHENTICATION_FINISH=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action9(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_PROCESS_TUNNEL_AUTHENTICATION_WAIT_MSCHAPV2_VERIFIED_RESPONSE=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action8(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq)), PEAP_ACTION_PROCESS_CLIENT_HELLO=ActionBucketMethod(actionBucket=com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket@5d87687e, method=public com.tplink.cdd.radius.common.eap.packet.EapPacket com.tplink.cdd.component.aaa.core.authentication.eap.service.impl.PeapActionBucket.action1(com.tplink.cdd.component.aaa.core.authentication.dto.AuthReq))}
11-05-2023 17:23:53.778 INFO [main] [] c.t.c.c.a.c.a.c.EapAuthConfig(): Success to init eap auth dispatcher, num = 4, invokes = {EAP_TTLS=com.tplink.cdd.component.aaa.core.authentication.service.handler.UserAccessEapTTlsAuthHandler@9ae48b9, PEAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.UserAccessEapPeapAuthHandler@1d7625c, EAP_TLS=com.tplink.cdd.component.aaa.core.authentication.service.handler.UserAccessEapTlsAuthHandler@431cb57, EAP_MD5=com.tplink.cdd.component.aaa.core.authentication.service.handler.UserAccessEapMd5AuthHandler@8666ac0}
11-05-2023 17:23:53.784 INFO [main] [] c.t.c.c.a.c.a.c.AuthConfig(): Success to init radius auth dispatcher, num = 9, invokes = {MAC_EAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.MacEapAuthHandler@111b9fd5, PPSK_UNBOUND_MAC_PAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.PapPpskUnboundMacAuthHandler@65e17e44, USER_ACCESS_PAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.UserAccessPapAuthHandler@3027f381, PORTAL_CHAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.ChapPortalAuthHandler@1336d663, MAC_PAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.MacPapAuthHandler@68be3d40, USER_ACCESS_EAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.UserAccessEapAuthHandler@1a424719, USER_ACCESS_CHAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.UserAccessChapAuthHandler@4710bb78, PORTAL_PAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.PapPortalAuthHandler@70a2b261, PPSK_BOUND_MAC_PAP=com.tplink.cdd.component.aaa.core.authentication.service.handler.PpskBoundMacPapAuthHandler@5c2df5f0}
11-05-2023 17:23:53.811 INFO [main] [] c.t.c.c.a.c.a.a.AccountingConfig(): Success to init radius accounting handler, num = 0, invokes = {}
11-05-2023 17:23:53.835 INFO [main] [] c.t.s.l.c.s.d.CacheLogConsumeHandler(): log mq consume task is start...
11-05-2023 17:23:53.837 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): Started OmadaLinuxMain in 36.582 seconds (JVM running for 39.547)
11-05-2023 17:23:53.865 INFO [main] [] c.t.s.o.m.d.p.b.a(): manager maintenance Handling event: org.springframework.boot.context.event.ApplicationStartedEvent[source=org.springframework.boot.SpringApplication@6d81bb3f]
11-05-2023 17:23:53.929 INFO [main] [] c.t.s.o.s.t.SpringBootStartUpTask(): record: task SpringBootStartupTask finished
11-05-2023 17:23:53.929 INFO [main] [] c.t.s.o.s.t.OmadacInitTask(): record: before OmadacInitTask
11-05-2023 17:23:53.957 INFO [main] [] c.t.s.o.s.t.OmadacInitTask(): record: before init bean
11-05-2023 17:23:53.972 INFO [main] [] c.t.s.o.s.t.OmadacInitTask(): record: after init bean
11-05-2023 17:23:54.071 INFO [main] [] c.t.s.o.s.p.m.d.b(): No startUpInfo exists.
11-05-2023 17:23:54.116 INFO [main] [] c.t.s.o.s.t.OmadacInitTask(): Start init data.
11-05-2023 17:23:54.117 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Start init data.
11-05-2023 17:23:54.165 INFO [main] [] c.t.s.o.i.a.b.d(): name=default_name tenant is not exist.
11-05-2023 17:23:54.168 INFO [main] [] c.t.s.o.i.a.b.d(): name=default_name tenant is not exist.
11-05-2023 17:23:54.462 INFO [main] [] c.t.s.o.i.d.m.o.b.a.a(): Initializing client settings of OmadacId: 8e93088852ec8f42adf32eaafd08fc38
11-05-2023 17:23:54.598 INFO [main] [] c.t.s.o.s.t.OmadacInitTask(): succeed in initializing default omadac OmadacVO(id=8e93088852ec8f42adf32eaafd08fc38, name=Omada Controller_08FC38, pattern=0)
11-05-2023 17:23:54.646 INFO [main] [] c.t.s.o.s.t.OmadacInitTask(): record: before init for hwc
11-05-2023 17:23:54.646 INFO [main] [] c.t.s.o.s.t.OmadacInitTask(): record: after init for hwc
11-05-2023 17:23:54.944 INFO [main] [] c.t.s.o.p.p.r.a.c(): init nioEventLoopGroup
11-05-2023 17:23:55.025 INFO [main] [] c.t.s.o.d.g.c.d.ThreadConfiguration(): device-gateway datatrack workGroup core thread  num is 8, max thread num is 8
11-05-2023 17:23:55.698 INFO [main] [] c.t.s.o.d.g.c.f.b.c(): file download mq consume task is start...
11-05-2023 17:23:55.736 INFO [main] [] c.t.s.o.m.d.p.t.TransportConfiguration(): adopt workGroup core thread num is 8, max thread num is8
11-05-2023 17:23:55.978 INFO [main] [] c.t.s.o.m.d.p.t.TransportConfiguration(): discovery workGroup core thread num is 2, max thread num is 10
11-05-2023 17:23:56.343 INFO [main] [] c.t.s.o.c.c.p.c.o.s.ActiveSiteCacheImpl(): Scheduled ActiveSitesCache period flush buf task at fixed rate of 30000 millis.
11-05-2023 17:23:59.204 WARN [http-nio-8088-exec-1] [] o.s.d.c.CustomConversions(): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation.
11-05-2023 17:23:59.224 WARN [http-nio-8088-exec-1] [] o.s.d.c.CustomConversions(): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation.
11-05-2023 17:23:59.811 INFO [main] [] c.t.s.o.d.g.c.d.ThreadConfiguration(): device-gateway datatrack time task workGroup core thread  num is 8, max thread num is 8
11-05-2023 17:24:00.424 INFO [comm-pool-2] [] c.t.s.o.s.t.OmadacInitTask(): Starting collection maintenance.
11-05-2023 17:24:00.435 INFO [main] [] c.t.s.o.p.b.b.d(): DisconnectRequestServer start
11-05-2023 17:24:00.563 INFO [main] [] c.t.s.o.s.d.a(): record: after OmadacInitTask
11-05-2023 17:24:00.563 INFO [main] [] c.t.s.o.s.t.CloudStartUpTask(): record: CloudStartUpTask start
11-05-2023 17:24:00.564 INFO [main] [] c.t.s.o.s.t.CloudStartUpTask(): record: CloudStartUpTask finished
11-05-2023 17:24:00.564 INFO [main] [] c.t.s.o.s.t.OmadacDiscoveryStartUpTask(): record: OmadacDiscoveryStartUpTask start
11-05-2023 17:24:00.564 INFO [main] [] c.t.s.o.s.t.OmadacDiscoveryStartUpTask(): record: OmadacDiscoveryStartUpTask finished
11-05-2023 17:24:00.672 INFO [main] [] c.t.s.o.d.g.a(): startServers, DISCOVERY host:null.
11-05-2023 17:24:00.674 INFO [main] [] c.t.s.o.d.g.a(): discovery Port is 29810.
11-05-2023 17:24:00.674 INFO [main] [] c.t.s.o.d.g.a(): manage    port v1 is 29811.
11-05-2023 17:24:00.674 INFO [main] [] c.t.s.o.d.g.a(): manage    port v2 is 29814.
11-05-2023 17:24:00.674 INFO [main] [] c.t.s.o.d.g.a(): adopt     port v1 is 29812.
11-05-2023 17:24:00.674 INFO [main] [] c.t.s.o.d.g.a(): upgrade   port is 29813.
11-05-2023 17:24:00.674 INFO [main] [] c.t.s.o.d.g.a(): transfer  port is 29815.
11-05-2023 17:24:00.674 INFO [main] [] c.t.s.o.d.g.a(): rtty port is 29816.
11-05-2023 17:24:00.710 INFO [main] [] c.t.s.e.t.a.t.AbstractServer(): Start NettyUdpServer bind /0.0.0.0:29810, export localhost/127.0.0.1:29810
11-05-2023 17:24:00.718 INFO [main] [] c.t.s.e.t.n.NettyTcpServer(): TCP server /0.0.0.0:29812 global traffic shaping, writeLimit: 536870912, readLimit: 0, checkInterval: 1000, max wait time: 15000
11-05-2023 17:24:00.722 INFO [main] [] c.t.s.e.t.a.t.AbstractServer(): Start NettyTcpServer bind /0.0.0.0:29812, export localhost/127.0.0.1:29812
11-05-2023 17:24:00.723 INFO [main] [] c.t.s.e.t.n.NettyTcpServer(): TCP server /0.0.0.0:29811 global traffic shaping, writeLimit: 536870912, readLimit: 0, checkInterval: 1000, max wait time: 15000
11-05-2023 17:24:00.724 INFO [main] [] c.t.s.e.t.a.t.AbstractServer(): Start NettyTcpServer bind /0.0.0.0:29811, export localhost/127.0.0.1:29811
11-05-2023 17:24:00.725 INFO [main] [] c.t.s.e.t.n.NettyTcpServer(): TCP server /0.0.0.0:29813 global traffic shaping, writeLimit: 536870912, readLimit: 0, checkInterval: 1000, max wait time: 15000
11-05-2023 17:24:00.726 INFO [main] [] c.t.s.e.t.a.t.AbstractServer(): Start NettyTcpServer bind /0.0.0.0:29813, export localhost/127.0.0.1:29813
11-05-2023 17:24:00.728 INFO [main] [] c.t.s.e.t.n.NettyTcpServer(): TCP server /0.0.0.0:29814 global traffic shaping, writeLimit: 536870912, readLimit: 0, checkInterval: 1000, max wait time: 15000
11-05-2023 17:24:00.728 INFO [main] [] c.t.s.e.t.a.t.AbstractServer(): Start NettyTcpServer bind /0.0.0.0:29814, export localhost/127.0.0.1:29814
11-05-2023 17:24:00.729 INFO [main] [] c.t.s.e.t.n.NettyTcpServer(): TCP server /0.0.0.0:29815 global traffic shaping, writeLimit: 536870912, readLimit: 0, checkInterval: 1000, max wait time: 15000
11-05-2023 17:24:00.730 INFO [main] [] c.t.s.e.t.a.t.AbstractServer(): Start NettyTcpServer bind /0.0.0.0:29815, export localhost/127.0.0.1:29815
11-05-2023 17:24:00.733 INFO [main] [] c.t.s.e.t.a.t.AbstractServer(): Start RttyNettyTcpServer bind /0.0.0.0:29816, export localhost/127.0.0.1:29816
11-05-2023 17:24:00.733 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Device connector server started.
11-05-2023 17:24:00.734 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Omada Controller started
11-05-2023 17:24:00.734 INFO [main] [] c.t.s.o.s.t.SuccessExitTask(): Omada Controller started
11-05-2023 17:24:00.734 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: finished run omada tasks
11-05-2023 17:24:06.371 INFO [comm-pool-2] [] c.t.s.o.s.t.OmadacInitTask(): Finished collection maintenance.

Architecture

amd64

OS

HAos

BenJamesAndo · 2023-11-06T22:31:23Z

I'm experiencing the same issue. I'll just rollback to an older version for now.

github-actions · 2023-11-12T12:03:18Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Geraldziu · 2023-11-13T08:39:43Z

The same happened to me :(

Geraldziu · 2023-11-13T10:21:54Z

The discussion is here mbentley/docker-omada-controller#344 and there is a workaround. But this would mean that we should connect to MongoDB inside the addon. Does anyone know how to connect to it?

s-e-t-h · 2023-11-20T20:15:40Z

@Geraldziu what if I reinstall and upload a backup?

BenJamesAndo · 2023-11-20T22:18:31Z

I've switched to using https://github.com/jkunczik/home-assistant-omada Omada HA addon and it works even after rebooting.

s-e-t-h · 2023-11-20T23:31:57Z

I've switched to using https://github.com/jkunczik/home-assistant-omada Omada HA addon and it works even after rebooting.

Thanks!

alexbelgium · 2023-11-21T08:18:21Z

Thanks - if there is a working addon then I'll remove this one from my repo

Geraldziu · 2023-11-21T22:48:06Z

Does anybody have any idea how to connect to the MongoDB of the broken addon? :) I would really hate to reconfigure my whole network

PS. Yes, I know, backup, yes had them, but after the addon ate my storage I deleted the backups from before it was broken. Unfortunately.

alexbelgium · 2023-11-22T07:25:08Z

Hi, I can recheck again to make it remanent by looking how the other add-on is doing it, I just wanted to avoid taking the work from another ; now that paperless is working again which was my latest focus I can look again

Whatsek · 2023-11-22T14:35:53Z

Hi, I can recheck again to make it remanent by looking how the other add-on is doing it, I just wanted to avoid taking the work from another ; now that paperless is working again which was my latest focus I can look again

The other addon is only working for Rasbberrys, cant install it on my intel NUC (CPU not compatible) So switching is not an option for me yet, restored the previous version from backup now.

alexbelgium · 2023-11-22T15:03:29Z

What is the last working version? It will give me a starting point thanks!

#1063

alexbelgium · 2023-11-22T16:00:29Z

Ok, I've pushed a test version that should restore the link with the /data. Please let me know if that works, or the latest version of the addon that worked and I can restore that logic - tested working

Whatsek · 2023-11-22T20:52:45Z

Ok, I've pushed a test version that should restore the link with the /data. Please let me know if that works, or the latest version of the addon that worked and I can restore that logic - tested working

Thank you for your time and awesome repository!

Tested this version just now, I upgraded fom: 5.9-chromium-amd64-2023-05-26 to version: 5.12-2023-11-21-2. But lost the configration. In the logfile the same error: c.t.s.o.s.OmadaLinuxMain(): No active profile set, falling back to 1 default profile: "default"

I cant tell if 5.9-chromium-amd64-2023-05-26 is the last version, but that was the first version that worked for me. I tried newer backups, but maybe I was too impatient. I can provide some information for you, logfiles or something before I restore a backup, happy to help. I can also retry another test version. Thanks!

alexbelgium · 2023-11-22T20:58:00Z

Thanks i'll check where that version stored it's data. I wonder if at one time i didn't store it in /config/addons_config/omada then changed to /data

alexbelgium · 2023-11-22T21:06:30Z

I switch in Oct 2022 from CONFIGSOURCE="/config/addons_config/omada"
To CONFIGSOURCE="/data"

To be sure, do you have a folder named /config/addons_config/omada?

Whatsek · 2023-11-22T21:08:53Z

I switch in Oct 2022 from CONFIGSOURCE="/config/addons_config/omada" To CONFIGSOURCE="/data"

To be sure, do you have a folder named /config/addons_config/omada?

Yes I have, only containiing one file:

/homeassistant/addons_config/omada/config.yaml

alexbelgium · 2023-11-22T21:12:25Z

Then this means that your files are really in /data... I don't understand why your omada instance doesn't pick it up...

alexbelgium · 2023-11-22T22:09:55Z

Hi, just read a comparable issue on the main upstream repo : mbentley/docker-omada-controller#325 (comment)

The recommendation : start the version still working, backup all your settings from the webUI, start clean with the latest version, and reimpory everything! This seems indeed the best way forward in case the mongodb files were messed up by moving forward or backward with versions

chiefcomm · 2023-11-22T23:24:53Z

Hi, just read a comparable issue on the main upstream repo : mbentley/docker-omada-controller#325 (comment)

The recommendation : start the version still working, backup all your settings from the webUI, start clean with the latest version, and reimpory everything! This seems indeed the best way forward in case the mongodb files were messed up by moving forward or backward with versions

Thanks for all the inputs/suggestions, I have just removed the add-on, rebooted OS, installed the add-on with no improvement on reboot the add-on defaults to no config and have to restore from backup. Is there a specific line in the config.yaml that could help?

alexbelgium · 2023-11-23T07:22:01Z

Hi, not sure to understand : according to a check on google it seems there should be a "Backup & Restore" setting in the webui? I don't use omada but this thread is based on the same mbentley image that my addon is using
https://www.reddit.com/r/TPLink_Omada/comments/q8q94r/no_backup_option_on_software_controller/

Geraldziu · 2023-11-23T17:32:23Z

Unfortunately after last update, I still have the same error, and I don't have a backup from before 5.12 when everything was working

11-23-2023 18:29:04.411 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): Starting OmadaLinuxMain v5.12.7 using Java 17.0.8.1 on db21ed7f-omada with PID 7 (/opt/tplink/EAPController/lib/local-starter-5.12.7.jar started by omada in /opt/tplink/EAPController/lib)
11-23-2023 18:29:04.427 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): No active profile set, falling back to 1 default profile: "default"

BenJamesAndo · 2023-11-24T01:25:51Z

Hi, I can recheck again to make it remanent by looking how the other add-on is doing it, I just wanted to avoid taking the work from another ; now that paperless is working again which was my latest focus I can look again

The other addon is only working for Rasbberrys, cant install it on my intel NUC (CPU not compatible) So switching is not an option for me yet, restored the previous version from backup now.

The beta version supports AMD64 CPU's, which is what I'm running mine on. It's my understanding that the stable version will support AMD64 soon. But running a beta version isn't for everyone.

Geraldziu · 2023-11-28T09:25:44Z

I have continued the discussion with Matt Bentley in that [discussion] (mbentley/docker-omada-controller#344 (reply in thread)) and right now it looks like after add-on is restarted it doesn't have access to previous persistent data or the data is not being saved when the container is closed (mine probably crashed)

alexbelgium · 2023-11-30T15:12:07Z

Well my code normally symlinks a folder in /data/db to /opt/tplink/EAPController/data/db to normally allow that ; with a chown omada:omada to allow permissions.

In my latest version, I've moved everything located in /data to /config (accessible using my filebrowser addon at the location /config/addons_config/xxx-omada ; or /addon_configs/xxx-omada) to allow people to access it manually.

I don't understand why it is not correctly seen by omada... I wonder if it doesn't support symlinks anymore while it was supporting it in the past...

alexbelgium · 2023-11-30T20:32:25Z

I wonder if this is because my symlinks were executed in parallel to Omada's code execution, I have forced the sequential execution in DONOTUPDATE_TEST3

Geraldziu · 2023-11-30T20:48:04Z

So i'm on 5.12-2023-11-22-DONOTUPDATE and using Filebrowser addon in addon_configs/db21ed7f_omada/ I see only config.yaml with your commented header and in /config/addons_config I see nothing

Geraldziu · 2023-11-30T21:00:58Z

Leatest update gives this unpleasent error

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: Properties file '*' missing, restoring default file...
cp: cannot stat '/opt/tplink/EAPController2/properties.defaults/*': No such file or directory

viniciusgava · 2023-12-01T06:35:47Z

I was able to recover my Omada controller by restoring it to version 5.12-2023-11-15. It was on automatic update, so I just noticed today when the Omada lost health check failed on my uptime Kuma instance.

Previously I was having the same error @Geraldziu posted above.

Any recent backup restore I tried before 5.12-2023-11-15 has failed to bring my data back.

alexbelgium · 2023-12-01T11:50:55Z

Thanks very much for the feedback ! It's really weird as the initial issue in the thread was on a version prior to 5.12-2023-11-15 which started this whole line of tentative modifications... As you have a strong addon backup in place, could I please ask you to test the version aptly named DONOTUPDATE_TEST3 ?

In theory it will copy your data from its current /data folder (so safe inside your backup file) to a /config folder accessible using the Filebrowser addon (at /config/addons_config/db21ed7f-omada, which itself is a symlink of /addons_configs/db21ed7f-omada), then provide remanence by using data stored in this folder.

It seems to work on my system using DONOTUPDATE_TEST3 (I see the files getting created, there is no error in the logs, I can access them after the addon is stopped) but for some reason the fact that it works on my system does not translate to it working on all systems ;-) if you tell me it works then I would publish it as an official version. Otherwise you would need to restore you 5.12-2023-11-15 backup to go back to your working state. Thanks very much !

Geraldziu · 2023-12-01T13:11:40Z

tried the same today, but still no luck. I don't see anything in the /config/addons_config, but I can see
config.yaml in /addon_configs/db21ed7f_omada/. If it makes any difference I'm running HA on raspberry pi 4 with 2GB ram.

alexbelgium · 2023-12-01T13:56:36Z

just the config.yaml in /addon_configs/db21ed7f_omada/ ??? normally there should be all the folders including the db... thanks for checking I'll see what could have occurred...

alexbelgium · 2023-12-01T18:15:36Z

It's really crazy : when I start the addon I see in /addon_configs/db21ed7f_omada :

and in the db folder

viniciusgava · 2023-12-01T18:39:04Z

@alexbelgium I can try to upgrade directly DONOTUPDATE_TEST3, but I current running 5.12-2023-11-15. Would that be a good test for you?

I ask because I did not have the time to read all the threads to understand the issue, I just restored the backups yesterday until started to work again. I can try to catch up on the thread later.

Let me know if you wanna I to proceed with the test.
I running in a Raspberry Pi 4, 4gb.

Thanks!

alexbelgium · 2023-12-01T19:02:45Z

Hi @viniciusgava if you had the time to upgrade directly to DONOTUPDATE_TEST3 and start the addon normally it would be perfect :-) don't bother reading the rest of the thread it was mostly tries & fixes and hard to say if the issue was in the addon or in the user systems

Thanks!

Geraldziu · 2023-12-02T18:18:56Z

Anything I could test why it's not working on my haos instance? I could understand that the add-on is crushing because there are not enough resources or whatever. But when it's working on one's system and not on my - it's frustrating. I have nothing special installed - standard HAOS with HACS (mushroom, tuya local, Panasonic comfort cloud, lg smart thing cloud), ZigBee2Mqtt, mosquito broker, Google drive backup, esphome, cloudflared.

No Idea what's different the usual. @viniciusgava could you share your setup?
@alexbelgium could you revert to version that's working for @viniciusgava ?

viniciusgava · 2023-12-03T10:54:42Z

Ok. It took me some time to test because this instance ran in a remote location and during the process of the restored backups the supervisor got stuck and I was required to request someone else to restart the raspberry pi.

It did not work upgrade from 5.12-2023-11-15 to DONOTUPDATE_TEST3 or 5.12-2023-11-15 to 5.12-2023-12-01. In both cases, the omada controller opens as a new instance ready to be setup.

Boot logs after migrating to 5.12-2023-12-01:


�[34m System: Home Assistant OS 11.1  (aarch64 / raspberrypi4-64)�[0m
�[34m Home Assistant Core: 2023.11.3�[0m
�[34m Home Assistant Supervisor: 2023.11.6�[0m
�[34m-----------------------------------------------------------�[0m
�[34m Please, share the above information when looking for help�[0m
�[34m or support in, e.g., GitHub, forums�[0m
�[34m-----------------------------------------------------------�[0m
�[32m Provided by: https://github.com/alexbelgium/hassio-addons �[0m
�[34m-----------------------------------------------------------�[0m
/etc/cont-init.d/00-global_var.sh: executing
Timezone set from Etc/UTC to America/Sao_Paulo
/etc/cont-init.d/01-config_yaml.sh: executing
Setting permissions for the config.yaml directory

�[32mLoad environment variables from /config/config.yaml if existing�[0m
�[32mIf accessing the file with filebrowser it should be mapped to /addon_configs/db21ed7f-omada/config.yaml�[0m
�[32m---------------------------------------------------------�[0m
�[32mWiki here on how to use : github.com/alexbelgium/hassio-addons/wiki/Add‐ons-feature-:-add-env-variables�[0m

... no config file, creating one from template. Please customize the file in /config/config.yaml before restarting.
�[32m... no env variables found, exiting�[0m
/etc/cont-init.d/01-custom_script.sh: executing
�[32mExecute /config/omada.sh if existing�[0m
�[32m---------------------------------------------------------�[0m
�[32mIf accessing the file with filebrowser it should be mapped to /config/*-omada/omada.sh�[0m
�[32mWiki here : github.com/alexbelgium/hassio-addons/wiki/Add-ons-feature-:-customisation�[0m
�[32m... no script found, exiting�[0m
/etc/cont-init.d/99-run.sh: executing
Creating directory
Creating symlink
Created symlink for 'LAST_RAN_OMADA_VER.txt'
Created symlink for 'config.yaml'
Created symlink for 'data'
Created symlink for 'db'
Created symlink for 'html'
Created symlink for 'keystore'
Created symlink for 'pdf'
Created symlink for 'portal'
Updating permissions


Recommendation : please backup your database and migrated to this addon https://github.com/jkunczik/home-assistant-omada


 
�[0;32mStarting the upstream container�[0m
 
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 'America/Sao_Paulo'
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
INFO: Importing cert from /cert/tls.[key|crt]
INFO: Version check passed; image version (5.12.7) >= the last version ran (); writing image version to last ran file...
INFO: userland/kernel check passed
INFO: Starting Omada Controller as user omada
12-03-2023 07:13:09.278 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: start the omada controller
12-03-2023 07:13:09.299 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: set property finished
12-03-2023 07:13:09.317 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): record: configure log finished
12-03-2023 07:13:09.337 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap prepare
12-03-2023 07:13:09.339 INFO [log4j-thread] [] c.t.s.o.c.o.a.b(): success to load configuration omada.properties
12-03-2023 07:13:09.343 INFO [log4j-thread] [] c.t.s.o.c.o.OmadacType(): omadacType: Local Controller
12-03-2023 07:13:09.484 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): going to start local mongod.
12-03-2023 07:13:11.069 INFO [main] [] c.t.s.o.s.s.b(): mongodb process id is 381
12-03-2023 07:13:11.075 ERROR [main] [] c.t.s.f.c.FacadeUtils(): facadeMsgEnable is not enable, msg: Mongo DB server started
12-03-2023 07:13:11.077 INFO [main] [] c.t.s.o.s.s.b(): Mongo DB server started
12-03-2023 07:13:13.150 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap record finished
12-03-2023 07:13:13.150 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: bootstrap startup
12-03-2023 07:13:13.591 INFO [main] [] c.t.s.o.s.OmadaBootstrap(): record: start run omada tasks
12-03-2023 07:13:13.594 INFO [main] [] c.t.s.o.s.t.SpringBootStartUpTask(): record: task SpringBootStartupTask start

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v2.6.6)

12-03-2023 07:13:17.246 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): Starting OmadaLinuxMain v5.12.7 using Java 17.0.9 on db21ed7f-omada with PID 8 (/opt/tplink/EAPController/lib/local-starter-5.12.7.jar started by omada in /opt/tplink/EAPController/lib)
12-03-2023 07:13:17.271 INFO [main] [] c.t.s.o.s.OmadaLinuxMain(): No active profile set, falling back to 1 default profile: "default"
12-03-2023 07:14:04.058 WARN [main] [] o.s.d.c.CustomConversions(): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation.
12-03-2023 07:14:12.972 INFO [main] [] c.t.s.o.m.l.p.e.LicenseEventCenterProperties(): licenseManagerTopic: omada.cloud.license.prd.topics
12-03-2023 07:14:24.559 INFO [main] [] c.t.s.o.m.d.p.t.TransportConfiguration(): upgradeSendReq workGroup core thread num is 1, max thread num is 1
12-03-2023 07:14:28.836 WARN [main] [] o.s.d.c.CustomConversions(): Registering converter from class java.time.LocalDateTime to class org.joda.time.LocalDateTime as reading converter although it doesn't convert from a store-supported type! You might want to check your annotation setup at the converter implementation.
12-03-2023 07:14:31.110 INFO [main] [] c.t.s.o.m.d.p.t.TransportConfiguration(): manager workGroup core thread  num is 16, max thread num is 16
12-03-2023 07:14:32.410 INFO [main] [] c.t.s.o.m.c.d.m.s.a.AbstractActiveSiteCacheImpl(): Scheduled ActiveSitesCache period flush buf task at fixed rate of 30000 millis.

How did I fix it?
I backup my data using the Omada controller panel while running an old version of Omada(5.12-2023-11-15) from my home assistant backups.
After that, I updated to 5.12-2023-12-01, and restored the backup. So far it is running normally.

No Idea what's different the usual. @viniciusgava could you share your setup?

@Geraldziu Raspberry Pi 4, 4GB Ram.
Addons: AdGuard Home, Duck DNS, ESPHome, File Editor, Home Assistant Google Drive Backup, MariaDB, Mosquitto broker, Network UPS Tools, Omada, Samba share, Signal Messenger, SMS UPS BETA, Studio Code Server, Terminal & SSH, Uptime Kuma and Wireguard.
HACS: Sonoff LAN, SmartThinQ LGE Sensors, Local Tuya.
Home assistant Code Version: core-2023.11.3
Home Assistant OS: 11.1(supervisor-2023.11.6)

I honestly did not go deep to understand what happened. Whatever was changed, seems to be related to the data storage. Either the addons changed something where the data persisted that may have killed the current data or the Omada controller made a break change?

For now, I will continue monitoring the new version with the Omada backup restored. I also pause auto-update for this plugin for now. I will probably change something on my monitoring since I did notice quickly when stopped to work(famous healthcheck HTTP status 200, right? 😆)

Geraldziu · 2023-12-05T21:00:31Z

@alexbelgium, do you know what the issue could be between 5.12-2023-11-15 and DONOTUPDATE3? we both have the same issue after the update. @viniciusgava, did you check the /addon_configs/db21ed7f_omada by any chance? Are there any files over there after the update to DONOTUPDATE3?

viniciusgava · 2023-12-06T07:25:17Z

@Geraldziu Can you please clarify what and where I can verify this? Just share more details that I will check for you when I have a chance.

Geraldziu · 2023-12-06T10:01:17Z

@viniciusgava this is what I ment :)

#1063 (comment)

Thanks very much for the feedback ! It's really weird as the initial issue in the thread was on a version prior to 5.12-2023-11-15 which started this whole line of tentative modifications... As you have a strong addon backup in place, could I please ask you to test the version aptly named DONOTUPDATE_TEST3 ?

In theory it will copy your data from its current /data folder (so safe inside your backup file) to a /config folder accessible using the Filebrowser addon (at /config/addons_config/db21ed7f-omada, which itself is a symlink of /addons_configs/db21ed7f-omada), then provide remanence by using data stored in this folder.

It seems to work on my system using DONOTUPDATE_TEST3 (I see the files getting created, there is no error in the logs, I can access them after the addon is stopped) but for some reason the fact that it works on my system does not translate to it working on all systems ;-) if you tell me it works then I would publish it as an official version. Otherwise you would need to restore you 5.12-2023-11-15 backup to go back to your working state. Thanks very much !

In theory if you update to DONOTUPDATE_TEST3 there should be some files in this folder /addon_configs/db21ed7f_omada. At least that's what alexbelgium had configured :-)

ChriKn · 2024-01-09T14:40:50Z

Hi, are there any news on this ?
I'm not really sure to understand everything well. Is there even a working beta at the moment ?

Thanks for your dedication ! @alexbelgium

alexbelgium · 2024-01-09T20:26:33Z

Hi, strangely it works on my system but I don't understand why it does not for other people...

Geraldziu · 2024-01-13T18:28:13Z

Unfortunately, it's still not working, and I don't have that much experience with docker/HAOS even to start debugging why it's not working for me and it's working for Alex.
But if there would be someone who would like to work on that with me, I'm more than happy to resolve this issue.

viniciusgava · 2024-01-16T08:05:38Z

Hi @Geraldziu. I am sorry I haven't tested you. I just checked if I still have this backup, but it was rotated already. I was able to download a backup 5.12.2023-11-22-test2.

Here is what it has inside of this backup:

I cannot restore the backup in the same device that the issue happened, since if anything goes wrong I cannot fix it, it's a remote location.

I restored it on my instance, which has almost the same hardware, but instead of 4GB ram is 8GB.
I was able to log in normally with this old backup. Data is still there.

After updating to the latest version as shown in the image below, all data was deleted. It shows up as a new installation.

the content inside after the update:

I don't know how much data you have in your previous backup, but, I just accepted that I lost the data and started over.
I disabled the auto-update, so I updating every month now. I did not get the problem earlier because of the auto-update.

cc: @alexbelgium

Geraldziu · 2024-01-16T09:54:26Z

Thanks for the update. I also accepted the loss and redo the whole network setup (with backup directly from Omada). Could you do one more test? When I start the add-on it starts blank, then when I recover from the backup, from inside Omada, it picks up the data (I have to test if it populates the folder). But when I restart the addon, the data is lost again.

viniciusgava · 2024-01-16T18:01:08Z

To make sure I get it:

Restore the backup that works.
Update to the latest version. It will erase all data as a new installation.
Restore a backup via Omada Panel. It should start to work again.
Reboot the adoon. It will erase all data again?

Is that it?

Geraldziu · 2024-01-16T21:45:47Z

Yes, that's correct

viniciusgava · 2024-01-18T07:33:58Z

Hi @Geraldziu. I did need to redo all the tests. I just did item 4, rebooted the addon, and my data is still there.

My two installations using this addon are small, with 2, and 5 devices in each installation—around 25 clients.

I also changed the config "web interface HTTP" port to 8089 since it conflicts with the InfluxDB port. It should not justify works for me and not for you though.

alexbelgium · 2024-01-18T19:16:30Z

Same here, data is still there... Not sure why there would be different behaviors for different systems but not being able to replicate makes it quite complex to solve...

viniciusgava · 2024-01-18T20:01:36Z

@alexbelgium Could you please send the GitHub diff link between the versions that were working previously and the version that moved the data to a different folder, which did not work for me and the others in this thread?

I gonna try to manually run these commands and see if I can find anything.

@Geraldziu What brand of your micro SD card? Is it fast enough?
I remember when I started to use Home Assistant, I had a micro SD that came with my Raspberry Pi kit, and I frequently had my MariaDB corrupted.
Since I move for a better card it reduces the frequency of corruption.
It might be related.

alexbelgium · 2024-01-18T20:21:57Z

Well it's hard to know exactly when the addon was still running. From what I see, issues started with the update on "Oct 2, 2023"

So here is a diff check between aprevious version (5.9-chromium-amd64-2023-05-26 to be safe) ; and the current one (5.13-2024-01-09). Watch-out there is a major upstream change (from 5.9 to 5.12) and that also HA has changed their way to store data which means that I implemented their new /config system

Here is (for 24h) the diff check of the two scripts : https://www.diffchecker.com/k4LxPw4B/

viniciusgava · 2024-01-19T08:58:15Z

Thanks for sharing @alexbelgium.

Probably this link will get us a similar diff:
https://github.com/alexbelgium/hassio-addons/compare/master..b7686532a3403007bf388c747cb38cd8270af41d
Commit link: b768653

Is this thread might be related to this issue?
https://community.home-assistant.io/t/folder-structure-not-updated-with-latest-release/642039
https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
https://developers.home-assistant.io/docs/add-ons/configuration/#add-on-advanced-options

I see a difference in the config.json for the field map, where config was replaced with addon_config.

I wonder if the old /data folder will be available to be copied to /config/data when you make this change.
The documentation says that when you add addon_config it will create this folder in the home assistant file system and map to /config in the container. Any chance of the MV happening before this volume map happens? Any chance when they map the folder it erases the data?

is It might be related to the docker in the ARM platform(not only Raspberry PI), behaving differently than AMD64?

I don't have any knowledge-building addons, so I just throwing ideas in case ring any bell to you Alex.

So far I have not had the time to restore the backup and ssh into the container to understand what happens.

Thanks

Geraldziu · 2024-01-19T21:45:19Z

@Geraldziu What brand of your micro SD card? Is it fast enough? I remember when I started to use Home Assistant, I had a micro SD that came with my Raspberry Pi kit, and I frequently had my MariaDB corrupted. Since I move for a better card it reduces the frequency of corruption. It might be related.
SD Should be fine :)
https://www.amazon.pl/Samsung-MicroSDXC-256GB-UHS-I-MB-MC256KA/dp/B09DVPX2LN

viniciusgava · 2024-02-23T00:07:07Z

Hi All.

I recently lost my data again. I am not sure what happened. It may be related to the rebooting as mentioned earlier here.

I have two installations for this addon, one that rarely reboots and another that reboots frequently.
It was the second one that I lost the data. Luckily I had one backup available from the last time we talked in this thread, so I recovered the device settings.

Also, the instance that rarely reboots is connected to a UPS device.
I remember that the first time I lost the data in my first instance, I was rebooting it frequently, and sometimes It was manually rebooted since the home assistant supervisor had hanged.

I migrated to the addon below and I hope it solves the issue.
I also added Auto Backup to Omada settings for a second backup in case this addon home assistant backup fails.
It´s been done via FTP using the FTP addons and persisted directly in the homeassistant config folder.

https://github.com/jkunczik/home-assistant-omada

I let you know in a few months if this new setup is working for me.

Thanks!

ChriKn added the bug Something isn't working label Nov 5, 2023

github-actions bot added the stale Element will be closed automatically label Nov 12, 2023

alexbelgium added prevent stale Prevents stale being applied and removed stale Element will be closed automatically labels Nov 12, 2023

alexbelgium added a commit that referenced this issue Nov 21, 2023

Deprecated #1063

bb20623

alexbelgium added a commit that referenced this issue Nov 22, 2023

Recreate previous logic

316abb4

#1063

🐛 [Omada] Rebooting the addon makes me lose access to my configuration #1063

🐛 [Omada] Rebooting the addon makes me lose access to my configuration #1063

Comments

ChriKn commented Nov 5, 2023

Description

Reproduction steps

Addon Logs

Architecture

OS

BenJamesAndo commented Nov 6, 2023

github-actions bot commented Nov 12, 2023

Geraldziu commented Nov 13, 2023

Geraldziu commented Nov 13, 2023

s-e-t-h commented Nov 20, 2023

BenJamesAndo commented Nov 20, 2023

s-e-t-h commented Nov 20, 2023

alexbelgium commented Nov 21, 2023

Geraldziu commented Nov 21, 2023

alexbelgium commented Nov 22, 2023

Whatsek commented Nov 22, 2023

alexbelgium commented Nov 22, 2023

alexbelgium commented Nov 22, 2023 • edited Loading

Whatsek commented Nov 22, 2023

alexbelgium commented Nov 22, 2023

alexbelgium commented Nov 22, 2023

Whatsek commented Nov 22, 2023

alexbelgium commented Nov 22, 2023

alexbelgium commented Nov 22, 2023

chiefcomm commented Nov 22, 2023

alexbelgium commented Nov 23, 2023

Geraldziu commented Nov 23, 2023 • edited Loading

BenJamesAndo commented Nov 24, 2023

Geraldziu commented Nov 28, 2023

alexbelgium commented Nov 30, 2023

alexbelgium commented Nov 30, 2023

Geraldziu commented Nov 30, 2023

Geraldziu commented Nov 30, 2023

viniciusgava commented Dec 1, 2023 • edited Loading

alexbelgium commented Dec 1, 2023 • edited Loading

Geraldziu commented Dec 1, 2023

alexbelgium commented Dec 1, 2023

alexbelgium commented Dec 1, 2023 • edited Loading

viniciusgava commented Dec 1, 2023

alexbelgium commented Dec 1, 2023

Geraldziu commented Dec 2, 2023

viniciusgava commented Dec 3, 2023 • edited Loading

Geraldziu commented Dec 5, 2023

viniciusgava commented Dec 6, 2023

Geraldziu commented Dec 6, 2023

ChriKn commented Jan 9, 2024

alexbelgium commented Jan 9, 2024

Geraldziu commented Jan 13, 2024

viniciusgava commented Jan 16, 2024

Geraldziu commented Jan 16, 2024

viniciusgava commented Jan 16, 2024

Geraldziu commented Jan 16, 2024

viniciusgava commented Jan 18, 2024

alexbelgium commented Jan 18, 2024

viniciusgava commented Jan 18, 2024

alexbelgium commented Jan 18, 2024

viniciusgava commented Jan 19, 2024

Geraldziu commented Jan 19, 2024

viniciusgava commented Feb 23, 2024

alexbelgium commented Nov 22, 2023 •

edited

Loading

Geraldziu commented Nov 23, 2023 •

edited

Loading

viniciusgava commented Dec 1, 2023 •

edited

Loading

alexbelgium commented Dec 1, 2023 •

edited

Loading

alexbelgium commented Dec 1, 2023 •

edited

Loading

viniciusgava commented Dec 3, 2023 •

edited

Loading