[Help]: Error starting Springboot on Synology Dead in water #476
-
Controller Version5.14.16.1 Describe Your Issue or QuestionContainer stops with error creating bean message below. How to downgrade the container??? Caused by: 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. Expected BehaviorJust upgraded from some previous version. Steps to ReproduceBoot container on Synology./ How You're Launching the Container
Container Logs
MongoDB LogsNo response Additional ContextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
FYI, I tried running the container in privileged mode, got the same error. |
Beta Was this translation helpful? Give feedback.
Duplicate of #418
There is a software bug in the 5.14 version of the controller and that’s on TP-Link. Use 5.13 for now.
Check the first post there for how to roll back to 5.13.