You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cri-resmgr[196816]: W: [ grpc ] [core]grpc: addrConn.createTransport failed to connect to {/var/run/cri-resmgr/cri-resmgr-agent.sock /var/run/cri-resmgr/cri-resmgr-agent.sock 0 }. Err: connection error: desc = "transport: Error while dialing dial unix /var/run/cri-resmgr/cri-resmgr-agent.sock: connect: no such file or directory". Reconnecting...
Yeah, there is really no that agent socket and I have never saw it ever. I think cri-resmgr has not created it.
And cri-resmgr doesn't work. When I start it with topolgy-aware plocy, the pod won't bind to numa node.
How to resolve this?
The text was updated successfully, but these errors were encountered:
My cri-resmgr version is
cri-resmgr version information:
I always get journal log related with cri-resmgr:
Yeah, there is really no that agent socket and I have never saw it ever. I think cri-resmgr has not created it.
And cri-resmgr doesn't work. When I start it with topolgy-aware plocy, the pod won't bind to numa node.
How to resolve this?
The text was updated successfully, but these errors were encountered: