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.
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
Client exception in call to com.sitewhere.grpc.service #962
Comments
Can you provide details regarding the Kubernetes cluster where you are running SiteWhere? In particular:
|
|
Thanks, that configuration should work well. I was just making sure that the services were not starved for CPU or other resources. It looks like the root of the issue is failed interactions with the device management microservice when getting device and/or listing assignments. Are there exceptions in the logs for that microservice. Also, is there any particular use case that triggers these issues? |
Thanks for your reply.The current bug will appear after entering the tenant after each new login. This is the error log. |
The root of this error seems to be the following lines:
It seems like in this case, the database had an error, which caused the device management APIs to fail. If you look in the |
error 1、Client exception in call to com.sitewhere.grpc.service.DeviceManagement/ListDeviceSummaries.CLOSE
error 2、Client exception in call to com.sitewhere.grpc.service.AssetManagement/GetAssetById.CLOSE
The text was updated successfully, but these errors were encountered: