Here is a link to the log output: https://github.com/user-attachments/files/15512450/out2.txt

05-31-2024 10:44:47.289 ERROR [main] [] o.s.b.SpringApplication(): Application run failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.tplink.smb.omada.identityaccess.domain.model.openapi.c.q': Unsatisfied dependency expressed through field 'e'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.tplink.smb.omada.identityaccess.port.common.a.a': Unsatisfied dependency expressed through field 'c'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.tplink.smb.omada.identityaccess.port.common.e.a': Unsatisfied dependency expressed through field 'b'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.tplink.smb.omada.identityaccess.b.p': Unsatisfied dependency expressed through field 'm'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.tplink.smb.omada.identityaccess.domain.model.user.A': Unsatisfied dependency expressed through field 'c'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'com.tplink.smb.omada.identityaccess.port.mongo.adaptor.persistence.tenant.a': Bean with name 'com.tplink.smb.omada.identityaccess.port.mongo.adaptor.persistence.tenant.a' has been injected into other beans [com.tplink.smb.omada.identityaccess.domain.model.d.q] in its raw version as part of a circular reference, but has eventually been wrapped. This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesForType' with the 'allowEagerInit' flag turned off, for example.

  @Hank21 - sorry, I did not get a notification of your reply.  No, I am not running the controller as root, I've created a non-root user to run it as.

  @Hank21 - someone else reporting that the 5.14.26.1 release also will randomly have the same problem: https://github.com/mbentley/docker-omada-controller/issues/441#issue-2400650196

I am affected by this bug as well. I hope it does not occur on productive release of 5.14.

  @mbentley I am having the same issue. Hopefully @Hank21 can help

  @Konni I have the same issue. Have not been able to get 5.14 to start, had to downgrade to 5.13.

  @mbentley I am having same issue as well w/ the latest 5.14 release. I rolled back to 5.13 successfully. 

Watchtower just upgraded my omada controller to 5.14.26.1 and it runs into the same issue. I have reverted back to 5.13.30.8 which is working fine.